A fix is available
APAR status
Closed as program error.
Error description
JCC processing of a job which had gotten an S878 abend and thus the JES joblog was not closed (S001 abend) caused the tracker to loop. Messages received were: EQQZ106W 010 % OF QUEUE JCCQ IN USE EQQZ106W 020 % OF QUEUE JCCQ IN USE . . EQQZ106W 099 % OF QUEUE JCCQ IN USE followed by: EQQZ120E XCF FUNCTION MSGO FAILED WITH EQQZ120I RETURN CODE=08 AND REASON CODE 00000008 . The tracker consumed a large amount of CPU during the loop.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All TWS for z/OS users and all IWS for * * z/OS 9.3 users, who are using the * * Job Completion Checker function. * * FUNCTION=JCC * **************************************************************** * PROBLEM DESCRIPTION: Loop of JCC task can occur when * * a processed job ends with a storage * * abend affecting also the initiator * * ability to execute clean up. * * In the customer scenario the job * * to be processed by JCC task * * ends with an OUT OF STORAGE condition, * * such as an abend ABEND0F9. * * In this case both job and initiator * * end without the possibility to do * * any clean up. * * As a result of this type of failure, * * JES is unable to write to spool the * * instorage buffers for OPEN SYSOUT * * data sets such as JOBLOG, and the * * sysout datasets are left on spool in * * a damaged (unreadable) condition. * * The damaged data sets cause the JCC * * loop. * **************************************************************** * RECOMMENDATION: APPLY THE PTF FIXING THIS APAR * **************************************************************** Damaged data sets, like the ones left on spool when a job abends OUT OF STORAGE condition, can cause a JCC loop.
Problem conclusion
The JCC task has been changed to prevent a loop condition: if the same data set is continuosly re-read the job processing is stopped, the new message EQQW902W is issued, and JCC continue to process the next job in the queue. Following documentation must be updated: +--------------------------------------------------------------+ |TITLE: Workload Automation | | Messages and Codes | | Version 8.5.1 SC32-1267-05 | | Version 8.6.0 SC23-9114-04 | | Version 9.1.0 SC23-9114-06 | | Version 9.2.0 SC23-9114-07 | |--------------------------------------------------------------| |CHAPTER :37. EQQWnnn messages (if 8.5.1) | |CHAPTER :40. EQQWnnn messages (if 8.6.0) | |CHAPTER :228. EQQWnnn messages (if 9.1.0) | |CHAPTER :242 EQQWnnn messages (if 9.2.0) | |--------------------------------------------------------------| | Add the following new messages: | | | | EQQW902W JCC IS LOOPING ON DATA SET &DSNAME | | FOR JOB &JOBNAME - &JOBNUM. | | PROCESSING ON THIS DATA SET IS SKIPPED. | | | | Explanation: This message is issued on Controller or | | tracker MLOG when the JCC task detects a loop while reading | | a data set from the spool: if always the same data set is | | returned it stops the loop and skip the specific job | | processing. The specific job is identified by job name | | &JOBNAME and Job id &JOBNUM. The involved data set is | | identified by the data set name &DSNAME. | | | | User response: none. | | | | System Action: Job is skipped, JCC processing continue. | | | +--------------------------------------------------------------+ +--------------------------------------------------------------+ |TITLE: IBM Workload Automation | | Messages and Codes | | Version 9.3 | |--------------------------------------------------------------| |CHAPTER :254. EQQWnnn messages | |--------------------------------------------------------------| | Add the following new messages: | | | | EQQW902W JCC IS LOOPING ON DATA SET &DSNAME | | FOR JOB &JOBNAME - &JOBNUM. | | PROCESSING ON THIS DATA SET IS SKIPPED. | | | | Explanation: This message is issued on Controller or | | tracker MLOG when the JCC task detects a loop while reading | | a data set from the spool: if always the same data set is | | returned it stops the loop and skip the specific job | | processing. The specific job is identified by job name | | &JOBNAME and Job id &JOBNUM. The involved data set is | | identified by the data set name &DSNAME. | | | | User response: none. | | | | System Action: Job is skipped, JCC processing continue. | | | +--------------------------------------------------------------+ 510Y 600Y 910Y 920Y 930Y EQQJCDSN EQQJCJOB EQQJCNXT EQQW90
Temporary fix
Comments
APAR Information
APAR number
PI48332
Reported component name
TIV WRKLD SCHD
Reported component ID
5697WSZ01
Reported release
920
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-09-08
Closed date
2015-12-30
Last modified date
2016-03-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI34135 UI34136 UI34137 UI34138 UI34139
Modules/Macros
EQQJCDSN EQQJCJOB EQQJCNXT EQQW90
| SC32126705 | SC23911404 | SC23911406 | SC23911407 |
Fix information
Fixed component name
TIV WRKLD SCHD
Fixed component ID
5697WSZ01
Applicable component levels
R510 PSY UI34135
UP16/02/27 P F602
R600 PSY UI34136
UP16/02/27 P F602
R910 PSY UI34137
UP16/02/27 P F602
R920 PSY UI34138
UP16/02/27 P F602
R930 PSY UI34139
UP16/02/27 P F602
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSRULV","label":"IBM Workload Scheduler for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"920","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"920","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 March 2016