PH48759: ABEND0C4 IN FRXRAUX0 OF IIUAPIFC

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• 1. ABENDS0C4 may occur in FRXRAUX0 of IIUAPIFC. This is because
  the asparm specified in the ASCRE macro assumed by DRF and the
  asparm created by the Index Builder (IIUAPIFC) were in different
  formats and of different lengths.
  2. ABENDS218 may occur in DRF SAS. This is because ABENDS0C4
  occurred in IGC0002D when the DEVTYPE macro was issued.
  3. ABENDS0C6 may occur in FRXTAS00 of DRF SAS when ADD PC is
  specified. This is because there is a timing when utility
  processing and utility termination processing are executed in
  parallel.
  

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: 1. ABENDS0C4 may occur in FRXRAUX0 of   *
  *                      IIUAPIFC. This is because the asparm    *
  *                      specified in the ASCRE macro assumed by *
  *                       DRF and the asparm created by the      *
  *                      Index Builder (IIUAPIFC) were in        *
  *                      different formats and of different      *
  *                      lengths.                                *
  *                      2. ABENDS218 may occur in DRF SAS. This *
  *                       is because ABENDS0C4 occurred in       *
  *                      IGC0002D when the DEVTYPE macro was     *
  *                      issued.                                 *
  *                      3. ABENDS0C6 may occur in FRXTAS00 of   *
  *                      DRF SAS when ADD PC is specified. This  *
  *                      is because there is a timing when       *
  *                      utility processing and utility          *
  *                      termination processing are executed in  *
  *                      parallel.                               *
  ****************************************************************
  * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
  ****************************************************************
  1. FRXRAUX0 of IIUAPIFC confirms the specification of
  RPTTYPE=SAS in asparm. Therefore, FRXRAUX0 in IIUAPIFC refers to
   the wrong address, so even if ABENDS0C4 does not occur, the STC
   (IIUAPIFC) in SUB-APIP cannot confirm RPTTYPE=SAS. In other
  words, the PC and IC reports output by Index Builder are not
  generated under the following conditions.
   a. RPTTYPE=SAS
   b. ADD IB ICNDX(YES)
   c. ADD IC
   d. ADD PC
   e. STATIPRT, VALIDPRT, and DFSPRINT are not specified in the
  DD of the PROC of IIUBSRT.
  2. When DRF issued the DEVTYPE macro to see if the utility's
  DD was defined in an address space other than DRF MAS, S218
  ABEND occurred. APAR OA63436 for DFSMSdfp for this issue has
  been opened, but will not be addressed immediately because it
  is a FIN APAR.
  Also, DRF issues the DEVTYPE macro multiple times for the same
  DD.
  3. If a write error occurs during the DB recovery process in
  DRF Job with ADD PC specified, ABENDS0C6 may occur in DRF SAS
  region.
  When a write error to DB occurs, DRF immediately calls the
  utility termination process without performing the utility
  result check process. Therefore, the utility termination process
  and the utility process called immediately before it may be
  running concurrently. And since the same HPPC module running in
  the utility process and the utility termination process has the
  NO-RENT and NO-REUSE attributes, an S0C6 ABEND may occur on the
  return from HPPC to DRF.
  

Problem conclusion

• 1. Changed the passing of RPTYPE=SAS from DRF MAS to IIUAPIFC
  to passing data space instead of asparm.
  2. To reduce the likelihood of S218 ABEND occurring, DRF has
  been modified to minimize the issuance of DEVTYPE macros.
  3. DRF is changed to call the utility result check process even
  if a write error occurs, to prevent the utility process and the
  utility termination process from being executed in parallel.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UI82356

Modules/Macros

• FRXGAPI0 FRXIOCN0 FRXIOSM0 FRXIVCN0 FRXIVSM0 FRXLBLD0 FRXMEST0
  FRXMEST1 FRXMSTR1 FRXMTRM0 FRXMTRM1 FRXRAUA0 FRXRAUX0 FRXSDR00
  FRXSDR20 FRXTAPI0 FRXTAU00 FRXTPFS0 FRXTSFS0 FRXTSIB0 FRXTSPR0
  FRXUAPI0 FRXUPRE0 FRXVRCV0
  

Fix information

• Fixed component name

  IMS RCVR SOLUTN

• Fixed component ID

  5655V8600

Applicable component levels

• R210 PSY UI82356

     UP22/09/15 P F209

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.