APAR status
Closed as documentation error.
Error description
1. In Managing the Workload, chapter 17, section "Re-executing steps", after the sentence in bullet item: "The dispostion type is NEW." Add: Since JES does not allow you execute a restart from a step that has a referback in VOL parameter to a step that has not been executed, TWS z/OS cannot allow this type of restart either. For example, if an earlier step in a job which is NOT executed on restart contains: 221 //XXXXJCL EXEC PGM=IEBCOPY 222 //SYSUDUMP DD SYSOUT=* 223 //SYSPRINT DD SYSOUT=* 224 //SYSUT1 DD DISP=SHR,DSN=XXXX.YYY(0) 225 //SYSUT2 DD DSN=XXXX.ZZZ(+1), // UNIT=TAPE,DISP=(,CATLG), // DCB=GDG,LABEL=(10,SL,EXPDT=99000), // VOL=(,RETAIN,REF=*.AAAAAAA.OUT) . and the later step where restart is desired to occur contains: 233 //XXXCOPY EXEC PGM=IEBGENER 234 //SYSUT1 DD DISP=SHR,DSN=&&VDRINV 235 //SYSUT2 DD DISP=(,CATLG),DSN=XXXX.AAA(+1), // UNIT=TAPE,DCB=GDG,LABEL=(11,SL,EXPDT=99000), // VOL=REF=*.XXXXJCL.SYSUT2 236 //SYSPRINT DD SYSOUT=* . The restart attempt will fail with message: IEF372I JJJJJJJJ XXXCOPY SYSUT2 - VOLUME FIELD CONTAINS REFERENCE TO A DD NOT PREVIOUSLY RESOLVED (2) The Customization and Tuning manual does not contain any consideration related to the use of DASD Mirroring in the "Disaster Recovery planning" Chapter. (3) In the TWS for z/OS Customization and tuning manual the description of SYSDEST and FAILDEST parameters for DSTOPTS Data Store initialization statement should contain a reference to a required cross check about JES2 DESTDEF parameter settings. (4) The messages EQQFAR2E and EQQFJKME need to be clarified when are issued after a S001 abend of the JES.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: (1) All TWS for zOS users of Restart and * * Cleanup feature. * * FUNCTION=R&C * * (2) All TWS for zOS users running Mirroring * * solutions for Disaster Recovery. * * FUNCTION=MCP * * (3) Users of the Data Store function. * * FUNCTION=DS. * * (4) All TWS for zOS users of Restart and * * Cleanup feature. * * FUNCTION=R&C * **************************************************************** * PROBLEM DESCRIPTION: (1) TWS for zOS Restart and Cleanup * * can fail with message IEF372I in * * case referback is used. * * (2) Even with Mirroring it is needed * * to start with CURRPLAN(NEW) * * after Disaster Recovery. * * (3) Missing information in SYSDEST and * * FAILDEST descriptions. * * (4) The messages EQQFAR2E and EQQFJKME * * need to be clarified when are * * issued after a S001 abend of the * * JES. * **************************************************************** * RECOMMENDATION: APPLY THE PTF FIXING THIS APAR * **************************************************************** (1) Since JES does not allow to execute a restart from a step which has a referback in VOL parameter to a step that has not been executed, TWS z/OS cannot allow this type of restart either in Restart and Cleanup feature. For example, if a job is restarted from a step which contains // VOL=(,RETAIN,REF=*.AAAAAAA.OUT) that is a referback to a previous step which has not been executed, the restart attempt will fail with message: IEF372I JJJJJJJJ XXXXXXX ZZZZZZ - VOLUME FIELD CONTAINS REFERENCE TO A DD NOT PREVIOUSLY RESOLVED (2) When mirroring is used, the Dual JT logging can be avoided. But even if the DASD Mirroring is in place, it is still necessary to use CURRPLAN(NEW) on restart after Disaster Recovery, due to LSR buffering of the CP1/CP2 which might make not complete the content of the CP1/CP2 and of its mirrored copy. (3) The description of SYSDEST and FAILDEST parameters for DSTOPTS initialization statement should contain a reference to a required cross check about JES2 DESTDEF parameter. (4) The messages EQQFAR2E and EQQFJKME need to be clarified when are issued after a S001 abend of the JES.
Problem conclusion
(1) The Managing the Workload Manual should document the TWS for zOS behavior when a referback is used in the VOL statement. (2) The Customization and Tuning manual, in the Disaster Recovery section, should mention the behavior in presence of DASD Mirroring. (3) The Customization and tuning manual need to clarify in the description of SYSDEST and FAILDEST parameters for DSTOPTS, the reference to a cross check about JES2 DESTDEF parameter. (4) The messages EQQFAR2E and EQQFJKME need to be clarified when are issued after a S001 abend of the JES. - - - THE FOLLOWING TWS FOR Z/OS PUBLICATION WILL BE UPDATED: - - - (1) +-------------------------------------------------------------+ |TITLE: Tivoli Workload Scheduler for z/OS | | Managing the Workload SC32-1263-04 | |-------------------------------------------------------------| |Chapter 20. Restart and cleanup | |Section Re-executing steps | | | |After the sentence in bullet list: "The dispostion type is | |NEW." add the following explanation: | | "JES does not allow the execution of a restart from a | | step that has a referback (REF=) in VOL parameter, to | | a previous step that has not been executed, TWS z/OS | | does not allow this type of restart either." | +-------------------------------------------------------------+ - - - +-------------------------------------------------------------+ |TITLE: Tivoli Workload Scheduler for z/OS | | Managing the Workload SC32-1263-05 | | SC32-1263-06 | |-------------------------------------------------------------| |Chapter 17. Restart and cleanup | |Section Re-executing steps | | | |After the sentence in bullet list: "The dispostion type is | |NEW." add the following explanation: | | "JES does not allow the execution of a restart from a | | step that has a referback (REF=) in VOL parameter, to | | a previous step that has not been executed, TWS z/OS | | does not allow this type of restart either." | +-------------------------------------------------------------+ - - - +-------------------------------------------------------------+ |TITLE: Tivoli Workload Scheduler for z/OS | | Managing the Workload SC32-1263-08 | |-------------------------------------------------------------| |Chapter 19. Restart and cleanup | |Section Re-executing steps | | | |After the sentence in bullet list: "The dispostion type is | |NEW." add the following explanation: | | "JES does not allow the execution of a restart from a | | step that has a referback (REF=) in VOL parameter, to | | a previous step that has not been executed, TWS z/OS | | does not allow this type of restart either." | +-------------------------------------------------------------+ - - - (2) +-------------------------------------------------------------+ |TITLE: Tivoli Workload Scheduler for z/OS | | Customization and Tuning SC32-1265-08 | | SC32-1265-06 | | Installation and Customization SC32-1265-04 | | SC32-1265-05 | |-------------------------------------------------------------| |Chapter 12. Disaster Recovery Planning | |Add a new Section after "Recovery to point-of-failure" | | | |"DASD Mirroring Considerations | | If products like PPRC, or other OEM products, are used for | | DASD mirroring of TWS for z/OS data sets, consider that: | | - It is advisable to allocate to DASD the EQQMLOG for the | | TWSz tasks, so that the datasets can be mirrored and | | checked, in case a recovery on the mirrored system is | | needed. | | - The use of mirroring would make dual logging unnecessary | | as far as the JT files will be mirrored. | | - The NCP/NCX will be mirrored as well, as long as the | | mirroring is not done during the run of a CP EXTEND or | | REPLAN (which would make the NCP/NCX not usable) | | That case, the most recent complete copy of the NCP backup| | must be used. The messages sequence EQQN121I, EQQN115I | | without the following EQQN116I is the indication of a not | | yet completed NCP (which makes mirrored copy unusable). | | - Note that, it is still necessary to set CURRPLAN(NEW) | | when starting the controller after the Disaster Recovery, | | even if DASD Mirrorring is in place in the environment, | | as due to LSR buffering the CP1/CP2 files cannot not be | | completely mirrored, the last changes might be still in | | storage, at the time the disaster occurs. For this reason | | also double check that the complete NCP copy (either from | | mirroring or most recent backup) is used on restart. | +-------------------------------------------------------------+ - - - (3) +-------------------------------------------------------------+ | | |TITLE: TWS for z/OS Installation and Customization SC32126404| | SC32126405| | Customization and Tuning SC32126406| | SC32126408| | | | | |CHAPTER: 1 TOPIC: DSTOPTS initialization statement | | SYSDEST parameter description | | | |Add the following text at the end of SYSDEST parameter | |description. | | | |If JES2 DESTDEF statement specifies NODENAME=REQUIRED, then | |the destination specified in the SYSDEST parameter must be | |defined to JES2. You can dynamically define it to JES using | |the following command: | | $ADD DESTID(xxxxxxxx),DEST=xxxxxxxx | |where xxxxxxxx is the destination specified in the DSTDEST | |parameter. | |If JES2 DESTDEF specifies NODENAME=OPTIONAL then the | |destination specified on SYSDEST does not need to be | |specified. | +-------------------------------------------------------------+ |TITLE: TWS for z/OS Installation and Customization SC32126404| | SC32126405| | Customization and Tuning SC32126406| | | | | |CHAPTER: 1 TOPIC: DSTOPTS initialization statement | | FAILDEST parameter description | | | |Add the following text at the end of FAILDEST parameter | |description. | | | |If JES2 DESTDEF statement specifies NODENAME=REQUIRED, then | |the destination specified in the FAILDEST parameter must be | |defined to JES2. You can dynamically define it to JES using | |the following command: | | $ADD DESTID(xxxxxxxx),DEST=xxxxxxxx | |where xxxxxxxx is the destination specified in the DSTDEST | |parameter. | |If JES2 DESTDEF specifies NODENAME=OPTIONAL then the | |destination specified on FAILDEST does not need to be | |specified | +-------------------------------------------------------------+ (4) +-------------------------------------------------------------+ |TITLE: Tivoli Workload Scheduler for z/OS | | Messages and Codes | | Version 8.5 SC32-1267-04| | Version 8.5.1 SC32-1267-05| |-------------------------------------------------------------| |Chapter EQQFxxx messages | |The following sentence must be added in the SYSTEM ACTION | |section for the message EQQFAR2E: | |If involved task is WRITER and RETURN value is 00001000, | |see message EQQFJKME. | | | |The following sentence must be added at the beginning of | |USER RESPONSE section for the message EQQFJKME: | |If this message is preceeded by EQQFAR2E with REASON 00001000| |a S001 abend has been recovered from and no other action is | |needed- however it will not be possible to restart the job | |mentioned in the EQQFAR2E message. | +-------------------------------------------------------------+ |TITLE: Tivoli Workload Automation | | Messages and Codes | | Version 8.6 SC23-9114-03| | Version 9.1 SC23-9114-06| |-------------------------------------------------------------| |Chapter EQQFxxx messages | |The following sentence must be added in the SYSTEM ACTION | |section for the message EQQFAR2E: | |If involved task is WRITER and RETURN value is 00001000, | |see message EQQFJKME. | | | |The following sentence must be added at the beginning of | |USER RESPONSE section for the message EQQFJKME: | |If this message is preceeded by EQQFAR2E with REASON 00001000| |a S001 abend has been recovered from and no other action is | |needed- however it will not be possible to restart the job | |mentioned in the EQQFAR2E message. | |-------------------------------------------------------------|
Temporary fix
Comments
APAR Information
APAR number
PM90316
Reported component name
TIV WRKLD SCHD
Reported component ID
5697WSZ01
Reported release
600
Status
CLOSED DOC
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2013-06-03
Closed date
2013-08-21
Last modified date
2016-04-22
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
| SC32126304 | SC32126305 | SC32126306 | SC32126504 | SC32126505 |
| SC32126506 | SC32126404 | SC32126405 | SC32126406 | SC23911406 |
| SC32126705 | SC23911403 | SC32126704 |
Fix information
Applicable component levels
[{"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":"600","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":"600","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
22 April 2016