PM94787: ENABLE THE SMART REORG UTILITY TO BUILD PSINDEXES WHILE A HALDB IS BEING REORGANIZED.

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• Enable the Smart Reorg utility to build PSINDEXes while a HALDB
  is being reorganized.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of IMS Database Reorganization     *
  *                 Expert for z/OS Version 4 Release 1          *
  *                 (FMID=H25N410)                               *
  ****************************************************************
  * PROBLEM DESCRIPTION: This APAR enables the Smart Reorg       *
  *                      utility to build PSINDEX by invoking    *
  *                      IMS Index Builder while a HALDB is      *
  *                      being reorganized.                      *
  ****************************************************************
  * RECOMMENDATION: Apply the maintenance for this APAR.         *
  ****************************************************************
  This APAR enables the Smart Reorg utility to build PSINDEX by
  invoking IMS Index Builder while a HALDB is being reorganized.
  
  Two new control statements are provided:
   -'PSINDEXBLD=YES' to build PSINDEXes
   -'ILDSBLD=YES,INITONLY' to skip loading ILE records to ILDS
     This is effective when PSINDEXs are rebuilt after
     reorganization of HALDB, in which no logical relationships
     are defined.
  
  To use the new functions, the following APARs are also required
  for the related products:
  - PM94788 IMS High Performance Unload V1R2 (FMID: H1IN120)
  - PM94789 IMS High Performance Load V2R1 (FMID: H1IM210)
  - PM94790 IMS Index Builder V3R1 (FMID: H22O310).
  

Problem conclusion

Temporary fix

Comments

• ========================
  = DOCUMENTATION CHANGE =
  ========================
  The IBM IMS Database Reorganization Expert for z/OS User's Guide
  Version 4 Release 1 Suffix 2 (SC19-1137-02) should be changed
  as follows:
  
  (Here, major changes are included. The other changes will be
   updated in the next suffix-up of User's Guide.)
  ---------------------------------------------------------------
  3.5.2.2 Control statements for the Smart Reorg Driver
   3.5.2.2.16 ILDSBLD control statement
  
   Specifies whether the ILDS for the HALDB is to be built in the
   Smart Reorg job step. The statement is valid only for a HALDB.
   This control statement is optional. If you do not explicitly
   specify this control statement, ILDSBLD=YES,DSPR is used.
    _______________________________________________________
   |                                                       |
   |                _YES___,DSPR_______                    |
  ||               |     |           | |                   |
  ||               |     |_,INITONLY_| |                   |
   | >>__ILDSBLD=__|_NO________________|________________>< |
   |                                                       |
   |_______________________________________________________|
  :
  | If you specify ILDSBLD=YES,INITONLY, the shadow ILDS is just
  | initialized and no ILEs are built. If the HALDB has no logical
  | relationships and every PSINDEX is rebuilt after HALDB
  | reorganization, this statement is effective in reducing
  | the ILDS spaces and the elasped time of HALDB reorganization.
  
    If you specify ILDSBLD=NO, no shadow ILDS is built processed.
    If the HALDB has ILDS and ILDSBLD=NO is specified, you must
    rebuild ILDS after the Smart Reorg job. To do this, scan
  | the reorganized database by using DFSPREC0 or IBM IMS Index
  | Builder.
  ---------------------------------------------------------------
  | 3.5.2.2.30a PSINDEXBLD control statement
  |
  |  Specifies whether the partitioned secondary indexes (PSINDEX)
  | for the database are built in the Smart Reorg job step.
  | This is an optional control statement for a HALDB.
  | If the database to be reorganized is a non-HALDB, this
  | control statement is ignored.
  | If you do not explicitly specify this control statement,
  | PSINDEXBLD=NO is used.
  | ______________________________________________________
  ||                                                      |
  ||                   _NO________________                |
  ||                  |      _,NEW_____   |               |
  || >>__PSINDEXBLD=__|_YES_|_,CURRENT_|__|____________>< |
  ||                                                      |
  ||______________________________________________________|
  |
  |  If you specify PSINDEXBLD=YES, an Index Builder task is
  | attached to build all PSINDEXs for the database.
  |  If PSINDEXBLD=YES,NEW, PSINDEXs are rebuilt in new data sets.
  |  If PSINDEXBLD=YES,CURRENT, PSINDEXs are rebuilt in the data
  | sets that are being used.
  |
  | If you specify PSINDEXBLD=NO, the Index Builder task is not
  | attached and no PSINDEX is built.
  |
  | The PARTITION control statement cannot be specified with
  | PSINDEXBLD=YES. If you want to reorganize the HALDB
  | in certain separate jobs with the PARTITION control statement,
  | remove PSINDEXBLD=YES and add the WFPHLQ control statement
  | for the Reload task. For the details, see "WFPHLQ control
  | statement".
  |
  |Notes:
  | 1. PSINDEXBLD=YES requires that an appropriate version of
  | IMS Index Builder is installed.
  | 2. You need to set up IMS Index Builder before using this
  | control statement. For details, see "Setting up IMS Index
  | Builder" in topic 2.2.5.1.
  ---------------------------------------------------------------
    3.6 JCL examples for Smart Reorg
  | 3.6.13 Example 13: Reorganizing a HALDB database and
  | rebuilding PSINDEXes
  |
  |  The database to be reorganized is an PHDAM database that
  | has two partitioned secondary indexes (PSINDEXes). This
  | example shows the JCL statements to reorganized all the
  | partitions of the PHDAM database and built each PSINDEX will
  | be built.
  |
  | //REORG    EXEC PGM=HPSGMAIN,PARM='DBD=SAMPLEDB,DBRC=Y'
  | //STEPLIB  DD DISP=SHR,DSN=IMSTOOLS.SHPSLMD0
  | //         DD DISP=SHR,DSN=IMSTOOLS.SIIULMOD
  | //         DD DISP=SHR,DSN=IMS.SDFSRESL
  | //         DD DISP=SHR,DSN=DBSAMP01.PGMLIB
  | //DFSRESLB DD DISP=SHR,DSN=IMS.SDFSRESL
  | //IMSDALIB DD DISP=SHR,DSN=IMS.MDALIB
  | //IMS      DD DISP=SHR,DSN=IMS.DBDLIB
  | //HPSIN    DD *
  | (REORG)
  |  IMSCMD=YES,TOSI
  |  SPACEALLOC=YES
  |  ILDSBLD=YES,INITONLY
  |  PSINDEXBLD=YES,NEW
  |  IC=YES
  |  NAMESWAP=YES
  |  STARTDB=YES
  |  DISPOLDDS=DELETE
  | /*
  | //ICEIN    DD *
  |  GLOBAL   ICHLQ=IMSICA,
  |           DSN=&ICHLQ..&DDN..IC1,
  |           UNIT=SYSALLDA,
  |           SPACE=(CYL,10,10)
  | /*
  | Figure 20. Reorganizing a HALDB that has partitioned secondary
  | indexes
  |
  |  Each control statement coded in the HPSIN data set can be
  | either:
  | - IMSCMD=YES,TOSI specifies to issue /DBR DB commands for all
  |  the PHDAM partitions and the PSINDEX partitions by using the
  |  IMS Tools Online System Interface.
  | - SPACEALLOC=YES specifies to dynamically allocate shadow
  |  spaces for the data sets of all the PHDAM partitions and
  |  the PSINDEX partitions.
  | - ILDSBLD=YES,ONLY specifies to initialize ILDS but no ILE
  |   records are built in the Reload task. It reduces the ILDS
  |   spaces and the elasped time of HALDB reorganization.
  | - PSINDEXBLD=YES,NEW specifies to activate the Index Builder
  |  task to rebuild each PSINDEX. The index records are loaded
  |  to the shadow data sets.
  |  If PSINDEXBLD=YES,CURRENT is coded, the index records are
  |  loaded to the original data sets directly. The shadow spaces
  |  for the PSINDEX partitions are not needed.
  | - IC=YES specifies to take image copy for the data sets of all
  |  the PHDAM partitions and the PSINDEX partitions by the Type-B
  |  Image Copy. You can specify some control statements for the
  |  Image Copy task in the ICEIN data set so that DASD space is
  |  allocated for image copy data sets automatically.
  | - NAMESWAP=YES specifies to do name swapping between the
  |  original data set and the shadow data for all the PHDAM
  |  partitions and the PSINDEX partitions.
  | - STARTDB=YES specifies to issue /STA DB commands for all the
  |  PHDAM partitions and the PSINDEX partitions by using the IMS
  |  Tools Online System Interface after the completion of
  |  reorganization.
  | - DISPOLDDS=DELETE specifies to delete all the old data sets
  |  for all the PHDAM partitions and the PSINDEX partitions.
  ---------------------------------------------------------------
  ================= End of Documentation Change ==================
  

APAR Information

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

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

  UK97614

Modules/Macros

• HPSCOPT  HPSCOPTS HPSGBBLA HPSGBBLB HPSGBBLC HPSGBBLD HPSGBBL9
  HPSGCM00 HPSGCM10 HPSGCM20 HPSGCR00 HPSGCSC0 HPSGCSC1 HPSGDI00
  HPSGGIO0 HPSGGRG0 HPSGGVM0 HPSGGVT0 HPSGIRM0 HPSGLIC0 HPSGLINK
  HPSGMAC  HPSGMAIN HPSGMSGT HPSGODA0 HPSGOPTG HPSGOPTR HPSGRA00
  HPSGRA10 HPSGRA40 HPSGRA50 HPSGRD00 HPSGRD20 HPSGRE00 HPSGRM00
  HPSGRM10 HPSGRP00 HPSGRP10 HPSGRP20 HPSGRP30 HPSGRR00 HPSGRS00
  HPSGRS10 HPSGRS40 HPSGSTMI HPSGSTMT HPSGTI00 HPSGTJ00 HPSGTM00
  HPSGTM30 HPSGTP00 HPSGTR00 HPSGTU00 HPSGTU2A HPSGTU2B HPSGTU2C
  HPSGTU2D HPSGTU29 HPSGTU3A HPSGTU3B HPSGTU3C HPSGTU3D HPSGTU39
  HPSPRP00 H25N410J
  

Fix information

• Fixed component name

  IMS DB REORG EX

• Fixed component ID

  5655F7400

Applicable component levels

• R410 PSY UK97614

     UP13/09/19 P F309

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.