PM56986: NEW CONTROL STATEMENT 'ILDS INITONLY' IS SUPPORTED TO INITIALIZE ILDS WITHOUT LOADING ILE RECORDS

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• A new control statement 'ILDS INITONLY' is supported to
  initialize the ILDS without loading ILE records for the user who
  runs Index Builder with the 'BLD ALL' control statement every
  time after reorganizing a HALDB.
  

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 provides a new control        *
  *                      statement 'ILDS INITONLY' which         *
  *                      specifies not to build ILE records.     *
  *                      The ILDS will be initialized only.      *
  *                                                              *
  *                      And the following problems are fixed:   *
  *                                                              *
  *                      1. The overflow data set of a secondary *
  *                      index with non-unique key is not        *
  *                      initialized when 'DFSURIDX DD DUMMY'    *
  *                      is specified in the JCL.                *
  *                                                              *
  *                      2. The overflow data set of a secondary *
  *                      index with non-unique key is not        *
  *                      allocated when the DDEFPDS DD statement *
  *                      is specified in the JCL.                *
  *                                                              *
  *                      3. When DD statements are coded in JCL  *
  *                      for a HALDB or PSINDEX data sets and    *
  *                      the data set names are different from   *
  *                      the names registered in RECON,          *
  *                      the error                               *
  *                      MSGIIUB079E should be issued:           *
  *                      IIUB079E DATA BASE dbname IS USING DATA *
  *                               SETS NOT REGISTERED WITH DBRC  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  This APAR provides the new functions listed in the Problem
  Description field.
  

Problem conclusion

Temporary fix

Comments

• ========================
  = Documentation Change =
  ========================
  IBM IMS Index Builder for z/OS, V3R1, User's Guide
  (SC18-9101-03) should be changed as follows:
  ================================================================
    2.1 IMS Index Builder functions
    2.1.1 Creating secondary indexes
    2.1.1.4 Initializing secondary indexes
  
    You can use IMS Index Builder to initialize the primary index,
    one or more secondary indexes, and the ILDS by using an empty
    or dummy DFSURIDX file as input.
  
  | For the ILDS, the control statement 'ILDS INITONLY' can be
  | used. See 'ILDS control statement'.
  
  ================================================================
    2.2 JCL and input control statements
    2.2.2 IMS Index Builder input control statements
    2.2.2.2 Optional control statements
  | 2.2.2.2.a ILDS control statement
  |
  |  The ILDS control statement specifies whether ILE records be
  |  built or not in the ILDS build process. This control
  |  statement can be specified with 'PROC BLD_ALL' or
  |  'PROC BLD_ILDS' statement for a HALDB.
  |
  |                 _BUILDILE_
  |                |          |
  |  >>__ILDS______|_INITONLY_|___________________><
  |
  |
  | ILDS
  |    Specifies whether ILE records be built or not for ILDS
  |    of each HALDB partition.
  |
  | BUILDILE
  |    Specifies to build and load the ILE records.
  |
  | INITONLY
  |    Specifies not to build ILE records. The ILDS will be
  |    initialized only.
  |
  | The DBRC commands to turn off the RECOVERY NEEDED flag is
  | issued in either case.
  |
  | The 'ILDS INITONLY' control statement can be specified
  | only if all the PSINDEXs be built after every reorganization
  | of the target HALDB. In this case, ILE records are not read
  | in the HALDB self-healing pointer process.
  |
  | If the ILDS statement is not specified, BUILDILE is used
  | as default.
  |
  | Note: You can override the default value in the runtime
  | parameters module. See the explanation of the IIURDFLT ILDS
  | entry in "Defining runtime parameters" in topic 2.4.
  ================================================================
  2.4 Defining runtime parameters
  
   IIURPRMS CSECT
   IIURPRMS RMODE 31
            DC    CL52'IIURPRMS'                      module start
   *                                 alternate sort procedure name
   *        DC    CL52'IIURSORT  IIUBSRT '
   *                                   run time default parameters
   *        DC    CL52'IIURDFLT  APIP      IIUAPIFC'
   *        DC    CL52'IIURDFLT  CLASS     IIU.STRIPE '
   *        DC    CL52'IIURDFLT  DBAUTH    NO'
  |*        DC    CL52'IIURDFLT  ILDS      INITONLY'
   *
            DC    CL52'IIUREND'                         module end
   *
            END   IIURPRMS
  Figure 21. Example of an IMS Index Builder runtime parameters
              module (Part 2 of 2)
  
  | Using IIURDFLT ILDS
  |   Use the IIURDFLT ILDS entry to specify whether ILE records
  |   be built or not. For details, see the description of
  |   "ILDS control statement".
  ================================================================
  3.3 IMS Index Builder reason codes
  3.3.5 IMS Index Builder processing phase failure reason codes
  
  | 784    ILDS INITIALIZATION FAILURE
  |
  | Explanation: ILDS initialization failed.
  | User Response: See the explanation of the IIUB048E message.
  ----------------------------------------------------------------
  3.4 IMS Index Builder messages
      IUB079E DATA BASE dbname IS USING DATA SETS NOT REGISTERED
              WITH DBRC
  
    Explanation: The DDNAME or DSNAME identified by dbname did not
  | match the names that are registered to DBRC. If the database
  | is a non-HALDB, the RECON data sets were initialized with the
  | FORCER option which requires that all databases be registered.
    System action: Processing stops.
  | User response: For a non-HALDB, if you do not want to register
    this database, specify DBRC=N on the INPUT control statement.
  | For a HALDB, if DD statements for the database data sets are
  | specified in the JCL, it's recommended removing
  | the statements.
  ----------------------------------------------------------------
  ================= End of Documentation Change ==================
  &#215;**** PE13/07/11 FIX IN ERROR. SEE APAR PM92805  FOR DESCRIPTION
  

APAR Information

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

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

  UK77010

Modules/Macros

• IIUBIBCD IIUBINIT IIUBMSGS IIUBSTMS IIUDRVRX
  IIUIFS2A IIUIFS2B IIUIFS22 IIUIFS29 IIUIFS3A IIUIFS3B IIUIFS32
  IIUIFS39 IIUMMSGR IIUNDXRC IIUNTLZR IIUSCA11 IIUSCA12 IIUSIBCD
  IIUSMP10
  

Fix information

• Fixed component name

  IMS INDEX BUILD

• Fixed component ID

  5655E2400

Applicable component levels

• R310 PSY UK77010

     UP12/03/14 P F203

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.