APAR status
Closed as documentation error.
Error description
Documentation updates for Tivoli Workload Scheduler for z/OS . 1. The text of messages EQQE146W, EQQE144E, EQQE145W about output collector processing is misleading. In these messages change "might be lost" to "will be lost if any additional zcentric jobs are run before the problem is corrected". . 2. In the TWSz 9.2 Messages and Codes manual, messages EQQZ022W, EQQZ023W, EQQZ025E all refer to "EQQSSCMD" instead of "EQQSSCML" (which is the specific value for the 9.2 release) or "EQQSSCMx" (if this is intended to be a generic value that is different for each release). . 3. The TWSz manuals do not explain that in the JCL for TRACKER and CONTROLLER started tasks, the DSN= of the EQQPARM DD card must not include the parmlib MEMBERNAME. Instead, the main parmlib member for TRACKER and CONTROLLER is specified in the PARM= keyword of the EXEC PGM=EQQMAJOR statement. For example > > //T91C EXEC PGM=EQQMAJOR,REGION=0M,PARM='CONP',TIME=1440 > If no membername is specified on the EXEC card, the default membername STDPARMS is used, and if this member does not exist, message EQQZ010E is issued: > > EQQZ010E MEMBER STDPARMS CANNOT BE FOUND IN PARAMETER > LIBRARY > and the task immediately terminates. . The PLANNING AND INSTALLATION manual, STEP 11 - DEFINING THE INITIALIZATION STATEMENTS, should document where the EQQPARM membername is specified... in the PARM= of the EXEC statement for TRACKERs and CONTROLLERs, and in the EQQPARM DD for all other started tasks and EQQBATCH jobs. It would also be helpful to have a comment to this effect in the sample procs in SEQQSAMP. . Further, the documentation of the OPCOPTS initialization statement in the CUSTOMIZATION AND TUNING manual should state A) Name of the PARMLIB member containing the OPCOPTS statement must be in the PARM= field of the EXEC card of the CONTROLLER and TRACKER PROCS B) If no PARM= is specified on the EXEC card, then a default membername of STDPARMS is used. 4. The documentation of the EVENT TRIGGERED TRACKING function in the TWSz MANAGING THE WORKLOAD manual, chapter 21-RUNNING EVENT DRIVEN WORKLOAD AUTOMATION, topic - AUTOMATICALLY ADDING AN OCCURRENCE TO THE CURRENT PLAN, should explicitly state that only type "A" Applications are supported. A type "G" (GROUP) application cannot be specified in an ETT definition, and a single ETT TRIGGER can add only ONE APPLICATION (up to 255 operations) into the Current Plan. (5) IBM Tivoli Workload Scheduler for z/OS Planning and Installation Version 9 Release 1 SC32-1264-08 On page 142 Chapter: Step 22. Activating support for the Java utilities There is reference in step 3 to "Make sure you applied FMID JWSZ603" FMID JWSZ603 is the E2E enablement FMID for TWS V8R6. It must be JWSZ913, instead.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: (1) All TWS for zOS 8.6.0, 9.1.0 and 9.2.0 * * users using output collector * * FUNCTION=OUC * * (2) All TWS for zOS 9.2.0 users * * FUNCTION=MAJOR * * (3) All TWS for zOS users * * FUNCTION=SAMP * * (4) All TWS for zOS 9.2.0 users * * FUNCTION=ETT * * (5) All TWS for zOS 9.1.0 users * * FUNCTION=DS-TRIG * * (6) All TWS for zOS users * * FUNCTION=E2E * **************************************************************** * PROBLEM DESCRIPTION: (1) The text of messages EQQE146W, * * EQQE144E, EQQE145W is misleading * * (2) Messages EQQZ022W, EQQZ023W, * * EQQZ025E for TWSz 9.2 * * all refer to "EQQSSCMD" instead * * of "EQQSSCML" * * (3) Message EQQZ010E is issued if PARM * * field on EXEC statement in TWSz * * started tasks is not specified. * * (4) A type "G" (group) Application * * cannot be specified in an ETT * * definition. * * (5) Wrong FMID referenced in TWSz * * Planning and Installation manual. * * (6) NOP command works on completed * * non-centralized E2E operations. * **************************************************************** * RECOMMENDATION: na * **************************************************************** (1) The text of messages EQQE146W, EQQE144E, EQQE145W is misleading (2) Messages EQQZ022W, EQQZ023W, EQQZ025E for TWSz 9.2 all refer to "EQQSSCMD" instead of "EQQSSCML" (3) PLANNING AND INSTALLATION manual, should document that the EQQPARM member name must be specified in the PARM= of the EXEC statement for TRACKERs and CONTROLLERs, and in the EQQPARM DD for all other started tasks and EQQBATCH jobs. Further, the documentation of the OPCOPTS initialization statement in the CUSTOMIZATION AND TUNING manual should state that if no PARM= is specified on the EXEC card, then a default membername of STDPARMS is used. (4) The TWSz MANAGING THE WORKLOAD manual, topic Automatically adding an occurrence to the current plan, should explicitly state that only type "A" Applicaiotns are supported. A type "G" (GROUP) application cannot be specified in an ETT definition. (5) In "Activating support for the Java utilities" a reference to the wrong FMID is reported (FMID JWSZ603) in TWSz 9.10 Planning and Installation manual. It should be FMID JWSZ913 instead. (6) The WSz MANAGING THE WORKLOAD manual, topic End-to-end scheduling with fault tolerance capabilities, should explain how the nop command works on completed non-centralized operations.
Problem conclusion
THE FOLLOWING TWS FOR Z/OS PUBLICATION WILL BE UPDATED: - - - (1) +-------------------------------------------------------------+ |TITLE: Tivoli Workload Automation | | Messages and Codes | | Version 8.6 SC23-9114-03| | Version 9.1 SC23-9114-06| | Version 9.2 SC23-9114-07| |-------------------------------------------------------------| |CHAPTER : EQQEnnn messages | | | |The System action of the messages EQQE146W, EQQE144E and | |EQQE145W has to be changed in this way: | | | |System action: The event manager continues | |processing but any events sent to the output collector | |from now on will be lost if any additional | |zcentric jobs are run before the problem is corrected. | |-------------------------------------------------------------| (2) +-------------------------------------------------------------+ |TITLE: Tivoli Workload Automation | | Messages and Codes | | Version 9.2 SC23-9114-07| |-------------------------------------------------------------| |CHAPTER : EQQZnnn messages | |The messages EQQZ022W, EQQZ023W, EQQZ025E wronly | |refer to the module EQQSSCMD. This name has | |to be changed with EQQSSCML. | |-------------------------------------------------------------| (3) +-------------------------------------------------------------+ |TITLE: Tivoli Workload Scheduler for z/OS | | Customization and Tuning SC32-1265-04 | | SC32-1265-05 | | SC32-1265-07 | | SC32-1265-08 | | SC32-1265-09 | |-------------------------------------------------------------| |Chapter 1. Defining Initialization Statements | |Section: OPCOPTS statement | | | |CHANGE FROM: | |"OPCOPTS is defined in the member of the EQQPARM library as | | specified by the PARM parameter on the JCL EXEC statement." | | | |TO: | |"OPCOPTS is defined in the member of the EQQPARM library as | | specified by the PARM parameter on the JCL EXEC card of | | Controller and Tracker start up PROCs. | | If no PARM= is specified on the EXEC card, then a default | | membername of STDPARMS is used. | +-------------------------------------------------------------+ - - - +-------------------------------------------------------------+ |TITLE: Tivoli Workload Scheduler for z/OS | | Installation and Customization SC32-1264-04 | | SC32-1264-05 | | SC32-1264-07 | | Planning and Installation SC32-1264-08 | | SC32-1264-09 | |-------------------------------------------------------------| |Chapter 11. | |Paragraph: "Step 11. Defining the initialization statements" | | | |CHANGE FROM: | |"The parameter library is specified by the EQQPARM DD | | statement in the Tivoli Workload Scheduler for z/OS | | started-task procedure." | | | | TO: | |"The parameter library is specified in the PARM= field of the| | EXEC statement for TRACKERs and CONTROLLERs started-task | | procedure and in the EQQPARM DD for all the other started | | tasks and EQQBATCH jobs. | | If the PARM= parameter is not specified, the default member | | name value STDPARMS is used, and if it does not exist, the | | message EQQZ010E is issued." | +-------------------------------------------------------------+ (4) +-------------------------------------------------------------+ |TITLE: Tivoli Workload Scheduler for z/OS | | Managing the Workload SC32-1263-08 | | SC32-1263-09 | |-------------------------------------------------------------| |Chapter 23. Running event-driven workload automation | |Section: Automatically adding an occurrence to the current | | plan | | | |Add the following new bullet at the end of the "Attention" | |paragraph: | |"- Only type 'A' Applications are supported. A type 'G' | | (GROUP) application cannot be specified in an ETT | | definition. If done, it fails with message EQQE011E" | +-------------------------------------------------------------+ +-------------------------------------------------------------+ |TITLE: Tivoli Workload Scheduler for z/OS | | Managing the Workload SC32-1263-04 | | SC32-1263-05 | | SC32-1263-07 | |-------------------------------------------------------------| |Part 1. Running event-driven workload automation | |Section: Automatically adding an occurrence to the current | | plan | | | |Add at the end the following "Attention" paragraph: | |"- Only type 'A' Applications are supported. A type 'G' | | (GROUP) application cannot be specified in an ETT | | definition. If done, it fails with message EQQE011E" | +-------------------------------------------------------------+ (5) +-------------------------------------------------------------+ |TITLE: Tivoli Workload Scheduler for z/OS | | Planning and Installation SC32-1264-08 | | | |-------------------------------------------------------------| |Chapter 4. Installing | |Paragraph: "Step 22. Activating support for the Java | | utilities" | | | |CHANGE BULLET 3 FROM: | |"3. Make sure you applied FMID JWSZ603" | | | | TO: | |"3. Make sure you applied FMID JWSZ913" | +-------------------------------------------------------------+ (6) +-------------------------------------------------------------+ |TITLE: Tivoli Workload Scheduler for z/OS | | Managing the Workload SC32-1263-04 | | SC32-1263-05 | | SC32-1263-07 | | SC32-1263-08 | | SC32-1263-09 | |-------------------------------------------------------------| |Chapter 13: Selecting Work for Automatic Submission | |Section: For end-to-end scheduling with fault tolerance | | capabilities | |Add at the end the following consideration: | | | |When the nop command is issued for non-centralized operations| |it is translated into a cancel pending action and the | |operations will be set directly to complete status when the | |conditions for them to run occur. | |If the nop command is issued against a completed | |non-centralized operation, it will not determine a cancel | |pending action and the operation will effectively run when | |the conditions occur, independently on nop status. | +-------------------------------------------------------------+
Temporary fix
Comments
APAR Information
APAR number
PI19400
Reported component name
TIV WRKLD SCHD
Reported component ID
5697WSZ01
Reported release
603
Status
CLOSED DOC
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-06-05
Closed date
2014-09-04
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:
| SC32126507 |
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":"603","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":"603","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
22 April 2016