APAR status
Closed as documentation error.
Error description
1) Add EQQW431E and EQQX068E errors in Messages_and_Codes manual EQQW431E DYNAMIC OPTION INCORRECT OR NOT DEFINED Explanation: Data entry error; see Data entry errors on page 877. User response: You specified an incorrect value. Specify Y (yes) or N (no). . EQQX068E REMOTE ENGINE INFO NOT AVAILABLE Explanation: Remote engine information is not available. System action: The request is rejected. User response: Specify a valid value 2) to change NOTE introduced with DOC APAR PI70574 on EQQYCOM. This is the text: ------- If EQQYCOM abends, processing is immediately interrupted and the control is passed to the system, therefore no return code is provided. ------- (3) The HTS and HTC subtasks should be added to the list of subtasks that can be started/stopped in Appendix D of the Managing the Workload manual (section "Modifying the scheduler". HTC (HTTP Client) and HTS (HTTP Server) should be added after GEN (General service subtas). . 4) In Messages_and_Codes manual (Chapter 216. Messages and codes overview in paragraph: "Message format""Message format") where EQQ message is mensioned and after -------------- I Information message. Processing continues and, in almost all cases, no action by the user is required. -------------- you have to add the following Note ----------------- Note Informational messages issued by IBM Workload Scheduler are not documented in this guide because they are complete in themselves and require no further information or explanation. This also applies to informational messages giving the usage of the product's commands. If you require more information than is given on the screen, see User's Guide and Reference. ----------------- . 5) IBM Workload Scheduler for z/OS: Planning and Installation and Table 25. IBM Workload Scheduler for z/OS VSAM data sets (page 101) shows for EQQNSTDS and EQQSTDS ------------- EQQPCS01 EQQNSTDS KSDS UNIQUE NSPND . EQQPCS01 EQQSTDS KSDS UNIQUE NSPND -------- Change both NSPND in SPANNED. . 6) Change manual IBM Workload Scheduler for z/OS: Managing the Workload Chapter 15. How work is selected for automatic submission paragraph : Identifying the order of submission to add AFTER the following point 3. : ---- 3. Operation priority (other than 9). --- this text ---- Each operation gets the priority assigned to the owing application as defined in the AD database. When in a dependency chain an operation with priority X has predecessors with a priority Y lower than X, then those predecessors will automatically get higher priority X as soon as they come in the Current plan. This is to avoid any delay in the submission of the operations defined as urgent in their dependency chain. The priority promotion of the predecessors is done at operation level and not at application level, because it could be that only some operations in a certain application have the urgent operation as a successor while the other don't have. ---- .
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: (1) All IWS and TWS for z/OS users running * * with dialog * * FUNCTION=DIALOG * * (2) All IWS and TWS for z/OS users running * * with TERM PIF * * FUNCTION=PIF * * (3) All IWS and TWS for z/OS users * * FUNCTION=MAJOR * * (4) All IWS and TWS for z/OS users * * FUNCTION=MESSAGES * * (5) All IWS and TWS for z/OS users * * FUNCTION=VSAM * * (6) All IWS and TWS for z/OS users * * FUNCTION=MAJOR * **************************************************************** * PROBLEM DESCRIPTION: (1) A new message errors EQQW431E, * * EQQX067E and EQQCL7QE are added * * (2) A clarification is needed when * * EQQYCOM ends in abend * * (3) Added two new subtasks that can be * * started/stopped. * * (4) Added a note where EQQ message is * * mensioned * * (5) Changed the attributes of VSAM * * for DD EQQCP1DS and EQQCP2DS * * (6) Clarification is needed for * * automatic submission * **************************************************************** * RECOMMENDATION: * **************************************************************** (1) In Messages and Codes manual, added 3 new message errors. (2) A clarification is needed when EQQYCOM ends in abend (3) Two new subtasks added in list of the subtasks that can be started/stopped (4) Added a note where EQQ message is mensioned (5) Changed the attributes of VSAM for DD EQQCP1DS and EQQCP2DS. The attributes is modified from NSPND (NO SPANNED) to SPANNED (6) Clarification is needed for automatic submission
Problem conclusion
(1) +-------------------------------------------------------------+ |TITLE: Messagges and Codes IWS for z/OS manual | | IWS 9.3.0 | | SC23-9114-07 | | SC23-9114-06 | | SC23-9114-04 | |-------------------------------------------------------------| |Chapter 255. EQQWnnn messages | |Section EQQW000 - EQQW902 | | | |ADD following EQQW430E message | | EQQW431E DYNAMIC OPTION INCORRECT OR NOT DEFINED | | Explanation: Data entry error; see Data entry errors | | on page 877. | | User response: You specified an incorrect value. | | Specify Y (yes) or N (no). | +-------------------------------------------------------------+ |Chapter 257. EQQXnnn messages | |Section EQQX000 - EQQX724 | | | |ADD following EQQX067E message | | EQQX068E REMOTE ENGINE INFO NOT AVAILABLE | | Explanation: Remote engine information is not available. | | System action: The request is rejected. | | User response: Specify a valid value | +-------------------------------------------------------------+ |Chapter 224. EQQCLnnn Messages | |Section EQQX000 - EQQX724 | | | |ADD following EQQCL7QE message | | EQQCL7QE Applications in GROUP(&XGRP) are mutually dependent| |Explanation: The application group contains applications | | mutually dependent. Say A10 and A20 are operations in | | application A, A10 predecessor to A20, and B10 is an | | operations in B. If A10 is a predecessor to B10 and B10 a | | predecessor to A20, A and B are mutually dependent. | | The mutual dependency could also be via other applications | | in the group. OCL cannot handle such dependencies | |System action: The request to add group is rejected. | |User response: Break up one of the applications given by | | the messages EQQCL7RI into two to get the predecessor | | operation (A10) in the chain in one application and the | | successor operation (A20) in another application. | +-------------------------------------------------------------+ (2) +-------------------------------------------------------------+ |TITLE: Driving IWS for z/OS manual | | IWS 9.3.0 | | SC32-1266-07 | | SC32-1266-08 | | SC32-1266-09 | |-------------------------------------------------------------| |Chapter 1. The program interface PIF | |Section TERM request | | | |CHANGE FROM | |If EQQYCOM abends, code execution is immediately interrupted | |and control is passed to system so that the returned parameter |list is not set at all and return code is not filled up. | |How to handle the abend is up to the code invoking EQQYCOM | |module and can be different according to the used language. | |TO | | If EQQYCOM abends, processing is immediately interrupted | | and the control is passed to the system, therefore no | | return code is provided. | +-------------------------------------------------------------+ (3) +-------------------------------------------------------------+ |TITLE: Managing the Workload | | IWS 9.3.0 | | SC32-1263-09 | | SC32-1263-08 | | SC32-1263-07 | |-------------------------------------------------------------| |Appendix D. Supported z/OS commands | |Section Modifying the scheduler | |ADD following subsystems after GEN | | HTC (HTTP Client) | | HTS (HTTP Server) | +-------------------------------------------------------------+ (4) +-------------------------------------------------------------+ |TITLE: Messagges and Codes IWS for z/OS manual | | IWS 9.3.0 | | SC23-9114-07 | | SC23-9114-06 | | SC23-9114-04 | |-------------------------------------------------------------| |Chapter 216. Messages and codes overview | |Section Message format | | | |ADD | | the following NOTE after I Information message. Processing | | continues and, an almost alla cases no action by the user | | required | |NOTE: | |Informational messages issued by IBM Workload Scheduler are | |not documented in this guide because they are complete in | |themselves and require no further information or explanation.| |This also applies to informational messages giving the usage | |of the product's commands. If you require more information | |than is given on the screen, see User's Guide and Reference. | +-------------------------------------------------------------+ (5) +-------------------------------------------------------------+ |TITLE: Planning and Installation IWS for z/OS manual | | IWS 9.3.0 | | SC32-1264-09 | | SC32-1264-08 | | SC32-1264-07 | |-------------------------------------------------------------| |Chapter 2. Installing IBM Workload Scheduler for z/OS | |Section Step 9. Allocating data sets | |CHANGE FROM | | EQQPCS01 EQQNSTDS KSDS UNIQUE | | NSPND | | EQQPCS01 EQQSTDS KSDS UNIQUE | | NSPND | |TO | | EQQPCS01 EQQNSTDS KSDS UNIQUE | | SPANNED | | EQQPCS01 EQQSTDS KSDS UNIQUE | | SPANNED | +-------------------------------------------------------------+ (6) +-------------------------------------------------------------+ |TITLE: Managing the Workload IWS for z/OS manual | | IWS 9.3.0 | | SC32-1263-09 | | SC32-1263-08 | | SC32-1263-07 | |-------------------------------------------------------------| | Chapter 15. How work is selected for automatic submission | |Section Identifying the order of submission | | ADD AFTER | | 3. Operation priority (other than 9) | | the following text | | | | Each operation gets the priority assigned to the owing | | application as defined in the AD database. | |When in a dependency chain an operation with priority X has | | predecessors with a priority Y lower than X, then those | | predecessors will automatically get higher priority X | | as soon as they come in the Current plan. This is to avoid | | any delay in the submission of the operations defined as | | urgent in their dependency chain. | | The priority promotion of the predecessors is done at | | operation level and not at application level, because it | | could be that only some operations in a certain application | | have the urgent operation as a successor while the other | | don't have. | +-------------------------------------------------------------+
Temporary fix
Comments
APAR Information
APAR number
PI77416
Reported component name
TIV WRKLD SCHD
Reported component ID
5697WSZ01
Reported release
930
Status
CLOSED DOC
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-03-01
Closed date
2017-06-27
Last modified date
2017-06-27
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
| SC23911407 | SC23911406 | SC23911404 | SC32126607 | SC32126608 |
| SC32126609 | SC32126309 | SC32126308 | SC32126307 | SC32126409 |
| SC32126408 | SC32126407 |
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":"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:
27 June 2017