A fix is available
APAR status
Closed as new function.
Error description
If a job is submitted to an STC workstation that has a mismatch between the job name and member name, all subsequent STC submissions may hang.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All TWS for z/OS users 8.5.1, 8.6, 9.1, * * 9.2 and IWS for z/OS users 9.3. * * FUNCTION=MAJOR * **************************************************************** * PROBLEM DESCRIPTION: When a started job is submitted * * and the job card has a job name * * different from the operation job * * name in the current plan: * * - Controller does not check the * * mismatch * * - Submit task starts the job * * with command /S operation_name * * As a consequence the started job * * remains forever in S status in * * the plan and no other started job * * is processed. * * This problem has been fixed by: * * - applying the JOBCHECK parameter * * to started job too * * - checking for a possible mismatch * * at tracker level, just before * * to submit the started job, * * preventing the submission in case * * of mismatch and setting the started * * job in failed status. * * - A new OPCOPTS keyword is provided * * for SUBMIT task usage: STCDELAY. * * It indicates the amount of seconds * * to be waited before to put the * * started job in error if the confirm * * of completed submission is not * * received from JES2 system. * **************************************************************** * RECOMMENDATION: * **************************************************************** When a started job is submitted and the job card has a job name different from the operation job name in the current plan: - Controller does not check the mismatch - Submit task starts the job with command /S operation_name As a consequence the started job remains forever in S status and no other started job is processed.
Problem conclusion
Temporary fix
Comments
Following documentation must be updated: +--------------------------------------------------------------+ |TITLE: IBM Tivoli Workload Scheduler for z/OS | | Customization and Tuning | | Version 8.5.1 SC32-1265-05 | | Version 8.6 SC32-1265-06 | | Version 9.1 SC32-1265-08 | | Version 9.2 SC32-1265-09 | | Version 9.3 | |--------------------------------------------------------------| |CHAPTER :1. Defining initialization statements | |SECTION : JTOPTS - Paramaters | |--------------------------------------------------------------| | In the JOBCHECK parameter explanation add the | | following sentence before the Note: | | | | With Apar PI57149 JOBCHECK is applied also to started task | | JCL (associated to a workstation of type STC). | | The only difference is that, when a JOB card is not found, | | the related action is not applied and job is submitted. | | This because started task workstations can have jobs | | submitted without a job card, according to the specific | | customer environment. | | Note that on tracker side the job name is always checked | | by SUBMIT task side whenever a JOB card is found in the JCL | | of a started task workstation. If SUBMIT task detects a | | job name mismatch a failed submission event is sent back to | | Controller. | +--------------------------------------------------------------+ |--------------------------------------------------------------| |CHAPTER :1. Defining initialization statements | |SECTION : OPCOPTS | |--------------------------------------------------------------| | Add the new keyword STCDELAY as follows: | | | | add in the FORMAT section: | | | | >--+-----------------------------------+------> | | | | | | | +-- 0 ------+ | | | | | | | | | +--- STCDELAY ( --+- integer -+--)--+ | | | | | | Add the in the Parameter section: | | | | STCDELAY (delay /0) | | - | | When a job running on workstation of type started task | | is submitted, the scheduler wait for the JES exit | | confirmation before to consider the submission completed. | | Until this confirmation is received, no other job running | | on a workstation of type started task can be submitted. | | This keyword specifies the time interval, expressed in | | seconds, that is waited for JES confirmation, before to | | consider the submission of the started task failed. | | If value 0 is specified (the default), no check on delay | | is done. | | This keyword can be useful to detect immediately if there | | are problems in started task submission, like for example | | the incorrect or missing installation of JES2 EXIT 51. | | Consider also that, whenever the system has spool problems | | the jobs can hang for a long time beforethey are really | | submitted and this case the Started task delay would be | | reached and jobs would be put in error status even if | | they really run after the spool problem has been solved. | | This keyword applies only to JES2 configurations. | | | +--------------------------------------------------------------+ +--------------------------------------------------------------+ |TITLE: IBM Tivoli Workload Scheduler for z/OS | | Messages and Codes | | Version 8.5.1 SC32-1267-05 | | Version 8.6 SC23-9114-04 | | Version 9.1 SC23-9114-06 | | Version 9.2 SC23-9114-07 | | Version 9.3 | |--------------------------------------------------------------| |CHAPTER : 30. EQQSUnn messages 8.5.1 | |CHAPTER : 34. EQQSUnn messages 8.6 | |CHAPTER :223. EQQSUnn messages 9.1 | |CHAPTER :238. EQQSUnn messages 9.2 | |CHAPTER :250. EQQSUnn messages 9.3 | |--------------------------------------------------------------| | Add the following new messages: | | | | EQQSU08E THE SUBMITTOR TASK DETECTED THAT THE STC &STCID | | EXCEEDED MAX DELAY TIME WAITING FOR JES EXIT POST. | | STC IS PUT IN FAILED STATUS. | | | | Explanation: This message is issued on Tracker MLOG | | when the submission of the started task identified by the | | &STCID name, waited for too much time the JES2 exit | | confirmation: the wait time exceeded the max delay time | | specified in the STCDELAY parameter. | | | | System action: The started task submission process is | | stopped and an event about the failed submission is | | sent back to controller. The STC data set used to store the | | procedure/jcl to be submitted is emptied so that | | otrher STC can be processed. | | | | User response: Check if there is some configuration | | error like missing activation of EXIT51 jes exit. | | | +--------------------------------------------------------------+
APAR Information
APAR number
PI57149
Reported component name
TIV WRKLD SCHD
Reported component ID
5697WSZ01
Reported release
930
Status
CLOSED UR1
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-02-12
Closed date
2016-07-04
Last modified date
2016-09-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI38529 UI38530 UI38531 UI38532 UI38533 UI38534 UI38535 UI38536
UI38537 UI38538
Modules/Macros
EQQSUMPR EQQSUQPR EQQSUSTC EQQSU0 EQQWASUB EQQWASUJ EQQZEV2X EQQZEV2Y EQQZMAIN EQQZOPTX
SC32126505 | SC32126506 | SC32126508 | SC32126509 | SC32126705 |
SC23911404 | SC23911406 | SC23911407 | SC32126505 | SC32126506 |
SC32126508 |
Fix information
Fixed component name
TIV WRKLD SCHD
Fixed component ID
5697WSZ01
Applicable component levels
R510 PSY UI38529
UP16/08/04 P F608
R512 PSY UI38534
UP16/08/04 P F608
R600 PSY UI38530
UP16/08/19 P F608
R602 PSY UI38535
UP16/08/19 P F608
R910 PSY UI38531
UP16/08/04 P F608
R912 PSY UI38536
UP16/08/04 P F608
R920 PSY UI38532
UP16/08/04 P F608
R922 PSY UI38537
UP16/08/04 P F608
R930 PSY UI38533
UP16/08/04 P F608
R932 PSY UI38538
UP16/08/04 P F608
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":"930","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":"930","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 September 2016