A fix is available
APAR status
Closed as program error.
Error description
The combination of PRF V2.1 and BBM V1.2 allowed batch backout to be run as part of the cancellation process when an Sx22 abend occurred. This happened because the logic to run batch backout was part of the mainline ESTAI processing for the application task which BBM attached. In PRF V2.2, this logic was removed from the ESTAI mainline code and placed into the mainline PRF logic. Due to the way an Sx22 abend works, the mainline PRF logic does not get control, so backout is not run. This causes database availability issues for customers because batch (DLI/DBB) jobs need to be restarted to allow the backout to occur.
Local fix
Restart the batch job; PRF will cause backout to run at job start when backout is not run at job end.
Problem summary
**************************************************************** * USERS AFFECTED: All Users of Program Restart Facility V2R2. * **************************************************************** * PROBLEM DESCRIPTION: As part of PRF V2.2, application abend * * processing changed in a way that caused * * backout processing to be skipped for * * jobs that encounter an abend that * * cannot be retried. This normally * * happens in Sx22 abends or out-of- * * memory conditions. * **************************************************************** * RECOMMENDATION: * **************************************************************** PRF V2.1/BBM V1.2 contained all application backout logic in an ESTAI exit that was activated as part of the application ATTACH process. This logic was modified and moved to the mainline PRF logic in PRF V2.2. This meant that an abend that could not be retried, such as an Sx22 abend, would cause PRF to skip backout processing during abend processing because the PRF mainline code would not get control. Note that in this case, job restart would cause PRF to proceed with application backout processing prior to application restart.
Problem conclusion
PRF abend processing was modified so that a new PRF ESTAE routine would get control in case of non-retryable abends. This ESTAE routine calls the PRF backout processor before percolating.
Temporary fix
Comments
APAR Information
APAR number
PI53660
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
2015-12-08
Closed date
2015-12-17
Last modified date
2018-01-10
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI33919
Modules/Macros
IRTRCC00
| SC19398501 |
Fix information
Fixed component name
IMS PGM RESTART
Fixed component ID
5655E1400
Applicable component levels
R220 PSY UI33919
UP15/12/19 P F512
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