A fix is available
APAR status
Closed as program error.
Error description
Dynamic backout RC=003C when customer includes //IMSLOGR2 DD statement in failing PRF DLI job step In addition, the IRT174 message does not differentiate between backout success and failure. This can confuse the issue for the customer.
Local fix
Remove the //IMSLOGR2 DD statement. It is not sufficient to specify the DD statement as DUMMY or DSN=NULLFILE. The DD statement must be *removed* from the JCL
Problem summary
**************************************************************** * USERS AFFECTED: All Users of Program Restart Facility V2R2 * * who use PRF's automated batch backout * * functionality. * **************************************************************** * PROBLEM DESCRIPTION: If a PRF-controlled batch DLI job * * fails and requires a backout, the * * backout will fail with RC=x'003C' if * * the job step contains a DD statement * * prefixed with 'IMSLOG'. This is true * * even when the DD statement is specified * * as DDDUMMY or DSN=NULLFILE. * * * * In addition, the IRT174I BATCH BACKOUT * * PROCESSING COMPLETE message is * * confusing when batch backout processing * * failes. * **************************************************************** * RECOMMENDATION: * **************************************************************** Some customers specify IMSLOGR/IMSLOGxx DD statements in their batch DLI jobs so that manual backout can be accomplished through simple JCL substitution overrides. When PRF generates backout logic, it normally uses only the primary output log of the failing job as input to batch backout. PRF therefore did not check for the existence of any //IMSLOGxx DD statements prior to passing control to the IMS Batch Backout utility. This causes the utility to fail because the correct logs are not allocated to the DD statement. In addition, PRF generates the same message at batch backout completion whether or not batch backout completed successfully. This is confusing.
Problem conclusion
Prior to calling the batch backout utility, PRF will check for the existence of any //IMSLOGxx DD statements, and deallocate the associated files if any are found. The confusing message will be modified to indicate success or failure of the batch backout operation.
Temporary fix
Comments
APAR Information
APAR number
PI74893
Reported component name
IMS PGM RESTART
Reported component ID
5655E1400
Reported release
220
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-01-13
Closed date
2017-02-06
Last modified date
2017-03-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI44448
Modules/Macros
IRTRCC00 IRTXBBO0
Fix information
Fixed component name
IMS PGM RESTART
Fixed component ID
5655E1400
Applicable component levels
R220 PSY UI44448
UP17/02/08 P F702
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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"220","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSAVHR","label":"IMS Program Restart Facility for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"220","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
24 January 2022