PI06319: IIUB100E REASON=106 WHEN RECON3 DD NOT CODED AND RECON3 MDA NOT FOUND

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• IIUB100E REASON=106 when RECON3 DD not coded and RECON3 MDA not
  found.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of IMS Index Builder for z/OS,     *
  *                 Version 3 Release 1 (FMID=H22O310)           *
  ****************************************************************
  * PROBLEM DESCRIPTION: This APAR fixes the following problems: *
  *                      1. When two RECON data sets are coded   *
  *                      on the RECON1 and RECON2 DD statements, *
  *                      MSGIIUB100E and RC=16 are issued:       *
  *                       IIUB100E INDEX BUILDER INIT FAILURE    *
  *                       - REASON=106                           *
  *                       (DBRC MDA PROCESSING ERROR)            *
  *                                                              *
  *                      2. MSGFABH1000I is issued erroneously   *
  *                      if all of three conditions are met,     *
  *                      - The library of IBM IMS High           *
  *                      Performance Unload is specified in      *
  *                      the STEPLIB or JOBLIB                   *
  *                      - The DFSISVI0 exit which have been     *
  *                      copied from FABHSVI0 is included in     *
  *                      the STEPLIB libraries.                  *
  *                      - The HPU scan is started               *
  *                       FABH1000I DFSISVI0 EXIT IS CALLED      *
  *                        BUT FABHURG1 CANNOT BE INVOKED        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  This APAR fixes the problems listed in the Problem Description
  field.
  

Problem conclusion

• This APAR fixes the problems listed in the Problem Description
  field.
  
  To fix the problem 1, some of the current behaviors of Index
  Builder have been adjusted by this APAR.
  - Index Builder attempts to allocate RECON1/2/3 DDs from MDA
  members if no RECONx DD statement is not coded in the JCL.
  - If Index Builder fails to allocate RECON1 DD from a MDA
  member, MSGIIUB100E and RC=16 are issued.
  - If the RECON2 or RECON3 DD statement cannot be allocated
  from MDA members, Index Builder continues its processing
  without issuing MSGIIUB100E.  However,  IMS DBRC might issue
  any error if RECON2 or RECON3 is unavailable.
  
  ========================
  = Documentation Change =
  ========================
  IBM IMS Index Builder for z/OS, V3R1, User's Guide
  (SC18-9101-04) should be changed as follows:
  
  ================================================================
   2.2 JCL and input control statements
   2.2.1 IMS Index Builder JCL
   2.2.1.2 DD statements
  
  | RECONx DD statement
  |  This statement provides RECON1, RECON2, and RECON3 DDs.
  | If RECON data sets need to be allocated dynamically, do not
  | specify these DDs. If no RECONx DD statement is not specified,
  | Index Builder attempts to allocate the RECONx DD statements
  | from the MDA members in STEPLIB or IMSDALIB.
  ----------------------------------------------------------------
   3.3 IMS Index Builder reason codes
   3.3.2 IMS Index Builder initialization phase primary reason
         codes
  
  (The reason code 106 is modified.)
  | 106    OBTAIN RECON1 DSNAME FAILURE
  |
  | Explanation: RECON1 data set is not provided through DD
  | statement.
  | User Response: Check if the RECON1 DD statement is correct.
  ----------------------------------------------------------------
  (The reason code 136 is modified.)
  | 136    RECON1 ALLOCATION FAILURE
  |
  | Explanation: Failed to allocate the RECON1 DD from a MDA
  | member.
  | User Response: Check if the MDA member for RECON1 is correct.
  ----------------------------------------------------------------
   3.3.3 IMS Index Builder initialization phase secondary reason
         codes
  (The reason code 316 is deleted.)
  D 316    OBTAIN RECON DSNAMES FAILURE
  D
  D Explanation: The code assists with the problem determination.
  D Recons could not be dynamically allocated by DDN.
  ----------------------------------------------------------------
  ================= End of Documentation Change ==================
  

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:

  UI13656

Modules/Macros

• IIUBDBD  IIUBINIT IIUBMSGS IIUDYN00 IIUHX034
  

Fix information

• Fixed component name

  IMS INDEX BUILD

• Fixed component ID

  5655E2400

Applicable component levels

• R310 PSY UI13656

     UP13/12/19 P F312

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.