A fix is available
APAR status
Closed as program error.
Error description
When multiple OPC RECOVER statements are coded in a TWS z/OS job, there are cases when, if a continuation statement is encountered, that the keywords on this continuation statement will apply to all OPC RECOVER statements in this job. Here is an example: Given a single step job with the following AR directives: //* //*%OPC RECOVER JOBCODE=3,ADDAPPL=(APPL01,APPL02), //*%OPC RESTART=Y,ALTWS=CPU2 //*%OPC RECOVER JOBCODE=(1-2,4-4095),RESTART=N,ADDAPPL=APPL03 //* If the job ends with *ANY* non-zero RC, it is restarted on workstation CPU2. However, the RESTART/ALTWS action should ONLY be taken for JOBCODE=3. If the AR directives are re-arranged as follows: //* //*%OPC RECOVER JOBCODE=(1-2,4-4095),RESTART=N,ADDAPPL=APPL03 //*%OPC RECOVER JOBCODE=3,ADDAPPL=(APPL01,APPL02), //*%OPC RESTART=Y,ALTWS=CPU2 //* Then it works correctly, and the RESTART is done only for JOBCODE=3. Also, regardless of what RC the job ends with, and which directives are executed, the "//*%" on the RESTART line is never changed to //*>.
Local fix
Ensure that the OPC RECOVER statement that contains the continued RESTART=Y is the last one in the sequence of other OPC RECOVER statements, or recode the statements to avoid the continuation.
Problem summary
**************************************************************** * USERS AFFECTED: All TWS for z/OS users. * * FUNCTION=AR * **************************************************************** * PROBLEM DESCRIPTION: The Automatic Recovery ALTWS keyword, * * does not work correctly when the jcl * * contains multiple AR statements. * **************************************************************** * RECOMMENDATION: APPLY THE PTF FIXING THIS APAR * **************************************************************** When multiple recovery statements are coded in a TWS z/OS job and on one of the preceding statement the keyword ALTWS is coded, it applies to all following recovery statements.
Problem conclusion
The problem was due a missing initialization of some TWSz internal fields. 202Y 302Y 502Y 512Y EQQARSCJ
Temporary fix
Comments
APAR Information
APAR number
PM29602
Reported component name
TIV WRKLD SCHD
Reported component ID
5697WSZ01
Reported release
500
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2010-12-29
Closed date
2011-02-15
Last modified date
2011-05-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK64878 UK64879 UK64880 UK64881
Modules/Macros
EQQARSCJ
Fix information
Fixed component name
TIV WRKLD SCHD
Fixed component ID
5697WSZ01
Applicable component levels
R202 PSY UK64878
UP11/04/17 P F104
R302 PSY UK64879
UP11/04/17 P F104
R502 PSY UK64880
UP11/04/17 P F104
R512 PSY UK64881
UP11/04/17 P F104
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"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":"500","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":"500","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 May 2011