PQ65086: ORIGINAL SECONDARY INDEX DATASET IS NECESSARY WHEN DBRC=Y AND INDEXBLD=YES,NEW IS SPECIFIED.

Obtain the fix for this APAR.

APAR status

• Closed as unreproducible in next release.

Error description

• Original Secondary Index dataset is necessary when DBRC=Y and
  INDEXBLD=YES,NEW is specified.  Logic will be changed such that
  if an original secondary index dataset does not exist in
  DBRC=Y and INDEXBLD=YES,NEW environment, IPR will bypass the
  nameswap process for the original secondary index dataset only.
  The nameswap process will continue for all other datasets.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of IPR Driver of IMS Parallel      *
  *                 Reorganization for z/OS Version 2 Release 1  *
  *                 (FMID=H25N210).                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: All original secondary index data sets  *
  *                      is necessary when INDEXBLD=YES,NEW is   *
  *                      specified.                              *
  ****************************************************************
  * RECOMMENDATION: Apply the maintenance for this APAR.         *
  ****************************************************************
  All original secondary index data sets is necessary when
  INDEXBLD=YES,NEW is specified and one of the following statement
  is specified.
  
  - NAMESWAP=YES
  - DYNALLOC=YES or DYNNALOC=xxx,xxx,YES
  - DBRC=Y
  
  This APAR supports expanded functions for the secondary indexes.
  If you specify INDEXBLD=YES,NEW and if an original secondary
  index data set does not exist, IPR bypasses the name swapping
  process for the original secondary index data set.
  Then the name swapping process continues for all other data
  sets.
  

Problem conclusion

Temporary fix

Comments

• ========================
  = DOCUMENTATION CHANGE =
  ========================
  IMS Parallel Reorganization for z/OS Version 2 Release 1 User's
  Guide (Document Number: SC27-1180-00) should be changed as
  follows.
  
  ================================================================
   Chapter 2. IMS Parallel Reorganization Driver
  
    2.1 Overview
     2.1.2 Reorganization Manager
      2.1.2.4 Automated Data Set Name Swapping
                               :
  | Notes:
  |  1.If you are reorganizing a HISAM, HDAM, or HIDAM database
       involved in logical relationships, you must swap the names
       manually. You are responsible for running prefix resolution
       and update utilities before the name swapping process, as
       well as providing the DFSURCDS information created by the
       IMS Prereorganization utility. For details, see
       "Reorganizing Logically Related Databases" in topic 2.11.4.
       Automated name swapping is always performed for a HALDB.
  
  |  2.If you specify INDEXBLD=YES,NEW, be careful in handling
  |    an original secondary index database data set. For details,
  |    see "Secondary Indexes" in topic 2.6.3.2.
  
    2.6 JCL Requirements
     2.6.3 Considerations for Database Data Sets
      2.6.3.2 Secondary Indexes
                               :
      If you specify NAMESWAP=YES and INDEXBLD=YES,NEW, the data
      names of the secondary indexes are swapped; that is, the
      output secondary indexes are renames to the original name
      and the original secondary indexes are renamed to temporary
      names.
  |   If you specify NAMESWAP=YES and INDEXBLD=YES,NEW and if
  |   there is no corresponding to the original data set, only
  |   the cluster name is renamed. Regardless of whether the
  |   component names are renamed, you can get access to the
  |   database.
  
  |   If you delete an original secondary index database data set
  |   before running IPR, IBM recommends that you reallocate an
  |   original secondary index database data set, specify
  |   INDEXBLD=YES,CURRENT, and then run IPR.
  
  |   If you delete an original secondary index database data set
  |   before running IPR, and if you specify NAMESWAP=YES and
  |   INDEXBLD=YES,NEW, the component names are not renamed.
  |   IBM recommends that you specify component names that do not
  |   need to be renamed after running IPR if you allocate the
  |   new secondary index database data set.
  |   If you need only to rename the component name after running
  |   IPR, generate the IDCAMS command streams to rename the
  |   component names, and then run the job.
  |   For details, see "Manual Name Swapping" in topic 2.9.2.
  
      If you specify NAMESWAP=YES and INDEXBLD=YES,CURRENT,
                               :
  
    2.9 Post-Reorganization Processing
     2.9.2 Manual Name Swapping
  
      The following steps apply when you complete the data set
      name swapping task manually:
  
      Step 1................
      Step 2................
  
  | Notes: When HPSG0311I is issued, the original secondary
  |        index data set does not exist.
  |        If necessary, rename the component names by doing the
  |        following:
  |
  | - NAMESWAP=YES
  |  Only the cluster name is renamed. You can get access to the
  |  database regardless of whether the component name is renamed.
  |  If necessary, generate the command streams as follows to
  |  rename the component names.
  |
  |       ALTER   new.secondary.index.comp_data.name         -
  |       NEWNAME(original.secondary.index.comp_data.name   )
  |       ALTER   new.secondary.index.comp_index.name        -
  |       NEWNAME(original.secondary.index.comp_index.name  )
  |
  | - NAMESWAP=NO
  |  The command stream is generated for renaming only the cluster
  |  name. If necessary, add the command streams (*1) as follows
  |  to rename the component names.
  |
  |       ALTER   original.primary.database.name          -
  |       NEWNAME(temporary.primary.database.name        )
  |                            :
  |       IF MAXCC EQ 0 THEN -
  |         DO
  |           ALTER   shadow.primary.database.name          -
  |           NEWNAME(original.primary.database.name         )
  |                            :
  |           ALTER   new.secondary.index.cluster.name         -
  |           NEWNAME(original.secondary.index.cluster.name   )
  | *1        ALTER   new.secondary.index.comp_data.name       -
  | *1        NEWNAME(original.secondary.index.comp_data.name )
  | *1        ALTER   new.secondary.index.comp_index.name       -
  | *1        NEWNAME(original.secondary.index.comp_index.name  )
  |         END
  ================================================================
   Appendix E. Messages and Codes
    E.3 Messages
     E.3.4 HPSG Messages
                               :
  | HPSG0311I DATA SET FOR ORIGINAL SECONDARY INDEX: dbdname
  |           NOT FOUND
  | Explanation:
  |      The original secondary index database dbdname data set is
  |      not found. If NAMESWAP=YES is specified, only cluster
  |      name of the data set is renamed.
  |      If NAMESWAP=NO is specified, the IDCAMS command steam for
  |      renaming only the cluster name for the data set is
  |      generated in the IDCAMS Command Stream for Name Swapping
  |      report.
  | System Action: IPR Driver continues processing.
  | Programmer Response:
  |      If necessary, rename the component name.
  |      For details, see "Manual Name Swapping" in topic 2.9.2.
  |      If you do not need to rename the component name, ignore
  |      this message.
  

APAR Information

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

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

  UQ69303

Modules/Macros

• HPSGGDIB HPSGGDLB HPSGGRGB HPSGGRG0 HPSGMSGT
  HPSGRA00 HPSGRI00 HPSGRS00 HPSGRS10
  

Fix information

• Fixed component name

  IMS PARALLEL RE

• Fixed component ID

  5655F7400

Applicable component levels

• R210 PSY UQ69303

     UP02/08/28 P F208

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.