A fix is available
APAR status
Closed as program error.
Error description
ABENDS0C4 may occur at FRXRLRA0 in DRF Master Address Space. This occurs because of an error in the process of checking whether a log record is eligible for processing.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All IMS Recovery Solution Pack for z/OS * * Version 2 Release 1 ( FMID=HAHM210 ) * * IMS Database Recovery Facility users. * **************************************************************** * PROBLEM DESCRIPTION: ABENDS0C4 may occur at FRXRLRA0 in DRF * * Master Address Space. This is because * * the process of checking whether a log * * record is eligible for processing * * omitted to take into the case where * * the log record was not eligible for * * processing. * **************************************************************** * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF * **************************************************************** In the DRF MAS (Master Address Space) Region, this problem (ABEND 0C4) is occurred in the module (FRXRLRA0) that determines if the log records read are necessary for the recovery process. If the subroutine "RVSortTableSearch" in this module is given the DB name and DD name from the information in the log record, it will identify the entry with the corresponding DB name from the database list (list of databases processed by DRF) and return the index of the database list (what number of the entry in the list). And, if the processed log record is not related to the database being recovered, zero (0) is returned as an index, but there is a bug in the subsequent processing, which inadvertently uses the index = 0 to look for an entry in the database list and then refer to an AREA outside the list. This time, ABEND S0C4 occurred because the address was an inaccessible location. In addition, depending on the usage status of storage of the entire system, ARAE that is mistakenly referenced may be able to access, but DRF will assume that the DB name is in the accessed location and compare it with the DB name in the log record, which will always be a mismatch, and subsequent processing will be bypassed. So, the problem does not occur. Therefore, this problem may or may not occur.
Problem conclusion
FRXRLRA0 has been modified as follows. Bypass the process of checking the log if a database entry is not found in the recovery list.
Temporary fix
Comments
APAR Information
APAR number
PH46990
Reported component name
IMS RCVR SOLUTN
Reported component ID
5655V8600
Reported release
210
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2022-06-03
Closed date
2022-06-10
Last modified date
2022-09-08
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI80972
Modules/Macros
FRXRLRA0
Fix information
Fixed component name
IMS RCVR SOLUTN
Fixed component ID
5655V8600
Applicable component levels
R210 PSY UI80972
UP22/06/14 P F206
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"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"2.1.0"}]
Document Information
Modified date:
08 September 2022