I think it is cased by a related bug which converts all numbers in job properties to positive values. As a result the -1 "Low" priority number is converted to 1 and this leads to "High" job priority. The fix is already available and will be provided in 3.4.18. This version should be come available in a week or two when the new web-based scheduler management system is generally released. : I'm trying to set the priority of a job to "Low", : without success. The help files says to set the : PRIORITY in JDL files to -1 for Low Priority. : I've tried: set 1316 PRIORITY=1 : set 1365 PRIORITY=0 : set 1414 PRIORITY=-1 : This sets these three jobs to High, Medium, and High, respectively. : I get the same behavior when using JAL's JobModify. : Am I doing something wrong?
|