A fix is available
APAR status
Closed as program error.
Error description
When the IRTRCC00 program is used as the IVP program in place of DFSRRC00, and the IRT$IGNR DD statement is present, IRTUPX00 will loop, transferring control to itself.
Local fix
If you wish to test DD statement exclusion, use the PRF ISPF interface to define an exclusion DD name with DISABLE PRF=YES, and specify that DD name in your test instead of IRT$IGNR.
Problem summary
**************************************************************** * USERS AFFECTED: All Users of Program Restart Facility V2R2 * * that run the PRF IVP job and want to test * * DD name exclusion by using the //IRT$IGNR * * exclusion DD name. * **************************************************************** * PROBLEM DESCRIPTION: The PRF IVP job is meant to be used to * * test PRF without having to install PRF * * Usermod A. The IVP job calls program * * IRTRRC00 instead of DFSRRC00. When * * using PRF in this fashion, and testing * * the DD name exclusion capability by * * specifying the //IRT$EXCL DD name, PRF * * will loop. The loop manifests itself as * * continual rapid WTOs of message * * IRT316I. The only way to stop the loop * * is to cancel the job. * **************************************************************** * RECOMMENDATION: Apply the PTF that corrects this APAR. * **************************************************************** The PRF IVP job is meant to be used to test PRF without having to install PRF Usermod A. The IVP job calls program IRTRRC00 instead of DFSRRC00. In this case, IRTRRC00 mimics Usermod A by loading IRTUPX00 and issuing an IDENTIFY call to identify IRTUPX00's entry point as DFSRRA00. IRTRRC00 then transfers control to DFSRRC00. When DFSRRC00 links to DFSRRA00, IRTUPX00 gets called instead. In normal IVP processing, IRTUPX00 ensures that it cleans up after itself. However, when the //IRT$IGNR exclusion DD name is found by IRTUPX00, this cleanup process is skipped. When IRTUPX00 finds the exclusion DD name, it immediately transfers control to DFSRRA00. However, since the IDENTIFY that aliases DFSRRA00 as IRTUPX00 has not been cleaned up, this transfer simply re-calls IRTUPX00, which then immediately checks for the //IRT$IGNR exclusion DD name again, causing the loop.
Problem conclusion
PRF has been modified to clean up the DFSRRA00 alias of IRTUPX00 when it discovers that the //IRT$IGNR exclusion DD name has been specified.
Temporary fix
Comments
APAR Information
APAR number
PI65082
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
2016-06-30
Closed date
2016-07-28
Last modified date
2016-08-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI39715
Modules/Macros
IRTUPX00
Fix information
Fixed component name
IMS PGM RESTART
Fixed component ID
5655E1400
Applicable component levels
R220 PSY UI39715
UP16/07/30 P F607
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