APAR status
Closed as documentation error.
Error description
(1) RESTART AND CLEANUP INFORMATIONS LOST IN CERTAIN CASE Whenever a step lvl restart is not able to rerun (for instance, if a special resource is not available) and a replan is is performed before the rerun could be executed (after the special resource becomes available), the STEP RESTART "mutates" to a JOB RESTART. This because RC restart point and rebuild JCL is lost beyond the replan, and the JCL found in JS is used for restart instead. (2) Message EQQS408E is missing from the TWSz V8R6 Message manual. Message 408 was added as part of the ADVANCED PANELS support. (3) Documentation of DSTOPTS MAXSTOL and MAXSYSL is incorrect. . MAXSTOL defines the maximum number of lines for each user sysout dataset that the DATASTORE can store for a single job. For example, if MAXSTOL(4) and the job allocates two USER SYSOUT datsets: -EQQMLOG -SYSOUT2 then 4 lines of EQQMLOG and 4 lines of SYSOUT2 are stored in the UDF file. . MAXSYSL defines the maximum number of lines for each user sysout dataset that the DATASTORE will send to the CONTROLLER. For esample, if MAXSYSL(2) and the job allocates 2 user sysout datasets: -EQQMLOG -SYSOUT2 then 2 lines of EQQMLOG and 2 lines of SYSOUT2 are sent to the controller.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: (1) * * All TWS for zOS users. * * FUNCTION=R&C * * (2) * * All TWS for zOS users. * * FUNCTION=Dialog. * * (3) * * All TWS for zOS users. * * FUNCTION=Datastore * **************************************************************** * PROBLEM DESCRIPTION: (1) * * If a job restart or a step level * * restart is requested but it cannot * * start due to, for example, a Special * * Resource not available, and a CP * * extend or CP replan or a controller * * stop/start is issued then when the * * operation will start, the cleanup step * * will not be added to the job and will * * not run, so the submitted job will be * * the one taken from the JS or jobs * * library. * * (2) * * Messages EQQS406E EQQS408E are not * * documented. * * (3) * * The description of the parameters * * MAXSTOL and MAXSYSL is incorrect. * **************************************************************** * RECOMMENDATION: Read the doc change * **************************************************************** (1) If a job restart or a step level restart is requested but it cannot start due to, for example, a Special Resource not available, and a CP extend or CP replan or a controller stop/start is issued then when the operation will start, the cleanup step will not be added to the job and will not run, so the submitted job will be the one taken from the JS or jobs library. (2) Messages EQQS406E and EQQS408E are missing from the TWSz V8R6 Message manual. Messages 406 and 408 were added as part of the ADVANCED PANELS support. (3) The description of the parameters MAXSTOL and MAXSYSL is incorrect.
Problem conclusion
(1) THE FOLLOWING TWS FOR Z/OS PUBLICATION WILL BE UPDATED: +-------------------------------------------------------------+ |TITLE: Workload Scheduler for z/OS | | Managing the Workload | | Version 8.3 SC32-1263-03| | Version 8.5 SC32-1263-04| | Version 8.5.1 SC32-1263-05| | Version 8.6 SC32-1263-06| |-------------------------------------------------------------| |Chapter: Restart and cleanup | |Section: When are cleanup actions performed? | | | |The following must be added as the third bullet of the list: | |½The step/job restart is not able to rerun | | If a job restart or a step level restart is requested but | | it cannot start due to, for example, a Special Resource | | not available, and a CP extend or CP replan or a controller | | stop/start is issued then when the operation will start, the| | cleanup step will not be added to the job and will not run, | | so the submitted job will be the one taken from the JS or | | jobs library. | +-------------------------------------------------------------+ (2) The messages EQQS406E and EQQS408E are missing in the TWSz Messages and Codes manual. THE FOLLOWING TWS FOR ZOS PUBLICATIONS WILL BE UPDATED: +--------------------------------------------------------------+ |TITLE: Tivoli Workload Scheduler for z/OS | | Messages and Codes | | | | TWSz 8.6.0 SC23-9114-03 | | Topic : EQQSnnn Messages | | | |Add following missing new messages: | | | |EQQS406E Invalid template name | |Explanation: The template for this panel has not been found. | |System action: The template cannot be used. | |Problem determination: Check if the template is present in | | EQQTMPL. | +--------------------------------------------------------------+ +--------------------------------------------------------------+ |TITLE: Tivoli Workload Scheduler for z/OS | | Messages and Codes | | | | TWSz 8.6.0 SC23-9114-03 | | Topic : EQQSnnn Messages | | | |Add following missing new messages: | | | |EQQS408E Err loading def template | |Explanation: Error using default panel template which cannot | | be loaded. | |System action: The default template cannot be used. | |Problem determination: Check if the template is present in | | EQQTMPL. | +--------------------------------------------------------------+ (3) THE FOLLOWING TWS FOR Z/OS PUBLICATION WILL BE UPDATED: +-------------------------------------------------------------+ |TITLE: Tivoli Workload Scheduler for z/OS | | Customization and Tuning | | Version 8.3 SC32-1265-03| | Version 8.5 SC32-1265-04| | Version 8.5.1 SC32-1263-05| |TITLE: Workload Scheduler for z/OS | | Version 8.6 SC32-1265-06| |-------------------------------------------------------------| |Chapter 1. | |Section DSTOPTS | | | |The description of the MAXSTOL parameter has to be changed. | |The first sentence: | |"Defines the maximum number of user sysout(not lines of | | sysout) the data store can store for a single job." | | has to be substituted with the following: | |"Defines the maximum number of lines, for each user sysout, | | that the data store can store; for example, if MAXSTOL(n) | | and the job allocates 2 user sysouts, SYSOUT1 and SYSOUT2, | | then n lines of SYSOUT1 and n lines of SYSOUT2 are stored | | in the UDF file. | | | |The description of the MAXSYSL parameter has to be changed. | |The first sentence: | |"Defines the maximum number of user sysout (not lines of | | sysout) the data store can send back to the controller. | | has to be substituted with the following: | |"Defines the maximum number of lines, for each user sysout, | | that the data store can send back to the controller; | | for example, if MAXSYSL(m) | | and the job allocates 2 user sysouts, SYSOUT1 and SYSOUT2, | | then m lines of SYSOUT1 and m lines of SYSOUT2 are sent back| | to the controller. | +-------------------------------------------------------------+
Temporary fix
Comments
APAR Information
APAR number
PM76631
Reported component name
TIV WRKLD SCHD
Reported component ID
5697WSZ01
Reported release
302
Status
CLOSED DOC
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-11-07
Closed date
2012-12-28
Last modified date
2012-12-28
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
| SC23911403 | SC32126306 | SC32126303 | SC32126304 | SC32126305 |
| SC32126503 | SC32126504 | SC32126505 | SC32126506 |
Fix information
Applicable component levels
Rate this page:
Average rating
Copyright and trademark information
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.