APAR status
Closed as program error.
Error description
SCHEDULE MDM93NEW#PRITEST PRIORITY 0 : MDM93NEW#DATE PRIORITY 50 END From DWC 1. Administration>Submit pre-defined Job Streams submit pritest 2. Monitor workload>check job "date" and select Actions>Hold 3. Monitor workload>check job "date" and select Actions>Release 4. Check job "date" priority, turns to default 10, instead of the original defined 50. If I repleace step 2 with followig, the same result as step 4. Monitor workload>check job "date" and select Actions>Priority, and change its priority to HOLD. The issue can be reproduced on 9.3 FP3 and 9.4 FP1 -------TEST RESULT USING CONMAN------- 1. ********For DWC 9.3 FP3 (MDM 9.3 FP3)********* ******CONMAN 9.3 FP3***** 1). Define a stream with one job: SCHEDULE MDM93NEW#PRITEST PRIORITY 0 : MDM93NEW#DATE PRIORITY 50 END 2). Submit it into the current plan. conman "sbs pritest" 3). Change the job to hold: conman "ap pritest.date;0" 4). Release the job: conman "rj pritest.date" 5). Check job priority is still 0. UNEXPECTED -----> Expected result: job priority returns to the original 50 6). Release the job by specifying priority keyword: conman "rj pritest.date;priority" 7). Check the job priority is still 0. UNEXPECTED -----> Expected result: job priority returns to the original 50 8). Change the job to hold again: conman "ap pritest.date;0" 9). Release the job by pecifying priority keyword: conman "rj pritest.date;priority" 10). Check the job priority returns to 50. EXPECTED! 11). Release the job without the keyword: conman "rj pritest.date" 12). Check the job priority is still 50. EXPECTED! Short result: ******CONMAN 9.3 FP3****** Result: On step 5), result is 0 UNEXPECTED On step 7), resul is 0 UNEXPECTED On step 10), result is 50. EXPECTED! On step 12), result is 50. EXPECTED! Hence it related to which command is issued first. If conman "rj <stream>.<job>" issued first, the priority will not return. If conman "rj <stream>.<job>" issued first, the priority will return. ******DWC 9.3 FP3****** Repeat the same steps using DWC. Result: On step 5), result 50 EXPECTED! ---> NOT the same as client's test. On step 7), no such option in DWC > More Actions > release 2. **********For DWC 9.4 FP1 (MDM 9.4 FP1)********* ******CONMAN 9.4 FP1****** Result: On step 5), result is 0 UNEXPECTED On step 7), resul is 0 UNEXPECTED On step 10), result is 50. EXPECTED! On step 12), result is 50. EXPECTED! ******DWC 9.4 FP1******** Result: On step 5), result is 50. EXPECTED! On step 7), no such option in DWC > More Actions > release
Local fix
N/A
Problem summary
THE JOB PREDEFINED PRIORITY WILL NOT RETURN TO THE ORIGINAL VALUE AFTER BEING HOLD AND RELEASED VIA DWC ERROR DESCRIPTION: SCHEDULE MDM93NEW#PRITEST PRIORITY 0 : MDM93NEW#DATE PRIORITY 50 END From DWC 1. Administration>Submit pre-defined Job Streams submit pritest 2. Monitor workload>check job "date" and select Actions>Hold 3. Monitor workload>check job "date" and select Actions>Release 4. Check job "date" priority, turns to default 10, instead of the original defined 50. If I repleace step 2 with followig, the same result as step 4. Monitor workload>check job "date" and select Actions>Priority, and change its priority to HOLD. The issue can be reproduced on 9.3 FP3 and 9.4 FP1 -------TEST RESULT USING CONMAN------- 1. ********For DWC 9.3 FP3 (MDM 9.3 FP3)********* ******CONMAN 9.3 FP3***** 1). Define a stream with one job: SCHEDULE MDM93NEW#PRITEST PRIORITY 0 : MDM93NEW#DATE PRIORITY 50 END 2). Submit it into the current plan. conman "sbs pritest" 3). Change the job to hold: conman "ap pritest.date;0" 4). Release the job: conman "rj pritest.date" 5). Check job priority is still 0. UNEXPECTED -----> Expected result: job priority returns to the original 50 6). Release the job by specifying priority keyword: conman "rj pritest.date;priority" 7). Check the job priority is still 0. UNEXPECTED -----> Expected result: job priority returns to the original 50 8). Change the job to hold again: conman "ap pritest.date;0" 9). Release the job by pecifying priority keyword: conman "rj pritest.date;priority" 10). Check the job priority returns to 50. EXPECTED! 11). Release the job without the keyword: conman "rj pritest.date" 12). Check the job priority is still 50. EXPECTED! Short result: ******CONMAN 9.3 FP3****** Result: On step 5), result is 0 UNEXPECTED On step 7), resul is 0 UNEXPECTED On step 10), result is 50. EXPECTED! On step 12), result is 50. EXPECTED! Hence it related to which command is issued first. If conman "rj <stream>.<job>" issued first, the priority will not return. If conman "rj <stream>.<job>" issued first, the priority will return. ******DWC 9.3 FP3****** Repeat the same steps using DWC. Result: On step 5), result 50 EXPECTED! ---> NOT the same as client's test. On step 7), no such option in DWC > More Actions > release 2. **********For DWC 9.4 FP1 (MDM 9.4 FP1)********* ******CONMAN 9.4 FP1****** Result: On step 5), result is 0 UNEXPECTED On step 7), resul is 0 UNEXPECTED On step 10), result is 50. EXPECTED! On step 12), result is 50. EXPECTED! ******DWC 9.4 FP1******** Result: On step 5), result is 50. EXPECTED! On step 7), no such option in DWC > More Actions > release
Problem conclusion
This apar will be fixed 9.3.0-TIV-TDWC-FP0004 and 9.4.0-TIV-TDWC-FP0004
Temporary fix
Comments
APAR Information
APAR number
IJ02348
Reported component name
TIV WKLD SCHDL
Reported component ID
5698WKB93
Reported release
9L3
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-12-03
Closed date
2018-02-28
Last modified date
2018-02-28
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
TIV WKLD SCHDL
Fixed component ID
5698WKB93
Applicable component levels
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSGSPN","label":"IBM Workload Scheduler"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9L3","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
28 February 2018