APAR status
Closed as documentation error.
Error description
This APAR will be used for documentation changes for the z Workload Scheduler product (all releases). Please number all entries beginning with (1). (1) In the "Workload Automation Programming Language for z/OS User's Guide and Reference Version 10.1 (Revised December 2023)" there is a typo at table 83 + 45 for CPSAI. Please change the argument name 'COMMETXT' to 'COMMTEXT'. . (2) In the Customization and Tuning Guide, under OPCOPTS statement, add a note under the EXIT01SZ parameter that although larger values can be coded, the maximum size that will be used is 65,534 (64K). However it is not recommended to make this value larger than required as it can cause a lot of memory to be used . (3) In the WAPL manual in table 9 for the DELETE AD add the VALFROM value in the argument name and in the description Valid-from date . (4) To better document an existing requirement that any task having an OMVS segment must have a HOME directory for which the userid has write access, in the Planning and Installation Guide, migration chapter (chapter 6) after section: "Running on upgraded operating systems" add a new section "HOME directory requirements for started tasks" and include the following text: To avoid error message EQQHT03E and/or EQQPH62E any task which is required to have an OMVS segment (including controller, server , output collector, datastore, and TCP connected tracker tasks), must have a HOME directory in its OMVS segment and this directory must exist and be mounted, and the started task must have write access to this HOME directory. . For example if you have a task named TESTF which is required to have an OMVS segment, the RACF commad LU TESTF OMVS NORACF must show a HOME directory, for example HOME= /u/TESTF and the userid TESTF which is the associated userid for task TESTF, must have WRITE access to this HOME directory. . Also in the Planning and Installation Guide chapter 4, section "Step 7. Setting up the RACF® environment" add after "MONOPTS statement."; See section "HOME directory requirements for started tasks" in chapter 6. . Also in section Step 18 add after the sentence "You always have to define OMVS segments for server started tasks.": See section "HOME directory requirements for started tasks" in chapter 6. Also at the end of section "Step 19. Activating support for end-to-end scheduling with z-centric capabilities" add: The userid of the output collector task will require an OMVS segment with a HOME directory. See section "HOME directory requirements for started tasks" in chapter 6. Also in section "Step 20. Activating support for Dynamic Workload Console" in subsection "Activating server support for the Dynamic Workload Console" after the sentence: "You always have to define OMVS segments for IBM Z Workload Scheduler server started tasks" add: See section "HOME directory requirements for started tasks" in chapter 6. . (5) In order to avoid getting an error like ICH408I USER(uuuuuu ) GROUP(gggg) CL(PROCESS) OMVS SEGMENT NOT DEFINED for a controller task which has ROUTOPTS HTTP or ROUTOPTS HTTPS in effect, the following change needs to be made to the Planning and Installation Guide, chapter 4, section Step 7. Setting up the RACF® environment, subsection: Controlling the user ID of the address space, after: TPLGYSRV parameter in the OPCOPTS statement. TCPIP parameter in the ROUTOPTS statement. MONOPTS statement, add: HTTP or HTTPS parameter in the ROUTOPTS statement. .
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: (1) All zWS 950, 101 and 102 users * * FUNCTION=WAPL * * (2) All ZWS 950, 101 and 102 users * * FUNCTION=EXIT * * (3) All ZWS 950, 101 and 102 users * * FUNCTION=WAPL * * (4) All ZWS 950, 101 and 102 users * * FUNCTION=HTTP * * (5) All ZWS 950, 101 and 102 users * * FUNCTION=HTTP * **************************************************************** * PROBLEM DESCRIPTION: (1) * * Changed the argument name 'COMMETXT' * * to 'COMMTEXT' * * (2) * * Added a note under the EXIT01SZ * * parameter * * (3) * * Added the VALFROM value in the * * argument name for the DELETE AD * * (4) * * Added many sentences and notes to * * manage the OMVS segment * * (5) * * Added many sentences and notes * * to manage the OMVS segment * **************************************************************** PROBLEM SUMMARY (1) Changed the argument name 'COMMETXT' to 'COMMTEXT' (2) Added a note under the EXIT01SZ parameter (3) Added the VALFROM value in the argument name for the DELETE AD (4) Added many text, notes and section to manage the OMVS segment (5) Added many text, notes and section to manage the OMVS segment
Problem conclusion
(1) !--------------------------------------------------------------! !TITLE: Workload Automation Programming Language for z/OS ! ! ! ! Version 9.5 ! ! Version 10.1 ! ! Version 10.2 ! !--------------------------------------------------------------! ! Chapter: INSERT - Add objects into the plan ! ! paragraph: INSERT CPSAI - Current Plan System Automation ! ! Info ! !--------------------------------------------------------------! ! ! ! Change the argument name ! ! FROM: ! ! COMMETXT ! ! TO: ! ! COMMTEXT ! !--------------------------------------------------------------! (2) !--------------------------------------------------------------! !TITLE: Customization and Tuning Guide ! ! ! ! Version 9.5 ! ! Version 10.1 ! ! Version 10.2 ! ! ! !--------------------------------------------------------------! !Chapter: Chapter 1. Defining initialization statements ! ! paragraph: OPCOPTS ! ! subparagraph: Parameters ! !--------------------------------------------------------------! !In the EXIT01SZ(number of JCL lines|0) section ! ! ADD following note ! ! Larger values can be coded: the maximum size that will be ! ! used is 65,534 (64K). However it is not recommended to ! ! make this value larger than required as it can cause a ! ! lot of memory to be used ! !--------------------------------------------------------------! (3) !--------------------------------------------------------------! !TITLE: Workload Automation Programming Language for z/OS ! ! ! ! Version 9.5 ! ! Version 10.1 ! ! Version 10.2 ! !--------------------------------------------------------------! !Table 7: DELETE AD - Application Definition ! !--------------------------------------------------------------! ! ! ! ADD the following value in the table ! ! ARGUMENT NAME ! ! VALFROM ! ! DESCRIPTION ! ! Valid-from date ! !--------------------------------------------------------------! (4) !--------------------------------------------------------------! !TITLE: Planning and Installation Guide ! ! ! ! Version 9.5 ! ! Version 10.1 ! ! Version 10.2 ! !--------------------------------------------------------------! ! Chapter 6: Migrating ! !--------------------------------------------------------------! ! ! ! After section "Running on upgraded operating systems" ! ! ADD a following new SECTION ! ! "HOME directory requirements for started tasks" ! ! with following text ! ! To avoid error message EQQHT03E and/or EQQPH62E any task ! ! which is required to have an OMVS segment (including ! ! controller, server , output collector, and TCP connected ! ! tracker tasks), must have a HOME directory in its OMVS ! ! segment and this directory must exist and be mounted, and ! ! the started task must have write access to this HOME ! ! directory. ! ! For example if you have a task named TESTF which is ! ! required to have an OMVS segment, the RACF command ! ! LU TESTF OMVS NORACF must show a HOME directory, ! ! for example HOME= /u/TESTF and the userid TESTF which is ! ! the associated userid for task TESTF, must have WRITE ! ! access to this HOME directory. ! !--------------------------------------------------------------! ! Chapter 4: Installing ! ! section "Step 7. Setting up the RACF environment" ! ! Sub-section: Controlling the user ID of the address space ! !--------------------------------------------------------------! ! ! ! After "MONOPTS statement." ! ! ADD a new point ! ! See section "HOME directory requirements for started ! ! tasks" in chapter 6. ! !--------------------------------------------------------------! ! Chapter 4: Installing ! ! section "Step 18. Activating support for the end-to-end ! ! scheduling with fault tolerance capabilities" ! ! Sub-section: Activating server support for end-to-end ! ! scheduling with fault tolerance capabilities ! !--------------------------------------------------------------! ! ! ! After "You always have to define OMVS segments for server ! ! started tasks" ! ! ADD following text ! ! See section "HOME directory requirements for started ! ! tasks" in chapter 6. ! !--------------------------------------------------------------! ! Chapter 4: Installing ! ! section "Step 19. Activating support for end-to-end ! ! scheduling with z-centric capabilities" ! !--------------------------------------------------------------! ! ! ! At the End of the section ! ! ADD following text ! ! The userid of the output collector task will require an ! ! OMVS segment with a HOME directory. ! ! See section "HOME directory requirements for started ! ! tasks" in chapter 6. ! !--------------------------------------------------------------! ! Chapter 4: Installing ! ! section "Step 20. Activating support for Dynamic Workload ! ! Console" ! ! sub-section: "Activating server support for the Dynamic ! ! Workload Console" ! !--------------------------------------------------------------! ! After the sentence "You always have to define OMVS segments ! ! for IBM Z Workload Scheduler server started tasks" ! ! ADD: ! ! See section "HOME directory requirements for started ! ! tasks" in chapter 6. ! !--------------------------------------------------------------! (5) !--------------------------------------------------------------! !TITLE: Planning and Installation Guide ! ! ! ! Version 9.5 ! ! Version 10.1 ! ! Version 10.2 ! !--------------------------------------------------------------! ! Chapter 4: Installing ! ! section "Step 7. Setting up the RACF environment" ! ! sub-section "Controlling the user ID of the address space"! !--------------------------------------------------------------! ! ! ! After ! ! - TPLGYSRV parameter in the OPCOPTS statement. ! ! - TCPIP parameter in the ROUTOPTS statement. ! ! - MONOPTS statement. ! ! ADD a new point ! ! - HTTP or HTTPS parameter in the ROUTOPTS statement. ! !--------------------------------------------------------------!
Temporary fix
Comments
APAR Information
APAR number
PH62691
Reported component name
TIV WRKLD SCHD
Reported component ID
5697WSZ01
Reported release
A10
Status
CLOSED DOC
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2024-08-09
Closed date
2024-12-03
Last modified date
2024-12-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU029","label":"Software"},"Product":{"code":"SSRULV","label":"IBM Workload Scheduler for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A10"}]
Document Information
Modified date:
03 December 2024