PQ61447: IPR DRIVER SUPPORTS HISAM AND SHISAM DATABASE

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• IPR Driver SUPPORTS HISAM and SHISAM Database.
  

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: This APAR provides new function of IPR  *
  *                      Driver. IPR Driver now supports HISAM   *
  *                      and SHISAM.                             *
  ****************************************************************
  * RECOMMENDATION: Apply the maintenance for this APAR.         *
  ****************************************************************
  This APAR provides new function of IPR Driver. IPR Driver now
  supports HISAM and SHISAM.
  

Problem conclusion

Temporary fix

Comments

• Four existing modules and an existing macro have been modified.
  
  ========================
  = DOCUMENTATION CHANGE =
  ========================
  IMS Parallel Reorganization for z/OS Version 2 Release 1 User's
  Guide (SC27-1180-00) should be changed as follows.
  
  Chapter 1. Introduction
  1.1 Major Features and Benefits
  1.1.1 Features and Benefits of Parallel Reorganization
     :
     :
     IPR Driver supports the following database organizations:
  |  - HISAM and SHISAM
     - HDAM
     - HIDAM
  |  - PHDAM
  |  - PHIDAM
  
    *** Delete following restriction:
     Note: HALDB and (S)HISAM are not supported by IPR Driver.
  
  1.2 Processing Environments
  1.2.1 Software Requirements
   IPR V2 requires the following products and maintenance
    1. For basic functions of IPR Driver, IPR Unload, and IPR
     Reload, the following are required:
     - IMS High Performance Unload for OS/390 Release 1 (5655-E06)
       - The maintenance provided by APAR PQ50674 must be applied
     - IMS High Performance Load for OS/390 Release 1 (5655-E07)
       - The maintenance provided by APAR PQ50675 must be applied
  |    - For HISAM and SHISAM support, the PTF to be provided by
  |      APAR PQ53316 must be applied.
    2. For INDEXBLD=YES function of IPR Driver, the following is 2
     required in addition to the products and the maintenance
     listed in item 1:
     - IMS Index Builder for OS/390 Version 2 Release 1 (5655-E24)
       - The maintenance provided by APAR PQ51252 must be applied
    3. If you are to reorganize HALDB by using IPR Driver or to
     use the DBD decoding function, following maintenance must be
     applied:
     - IMS High Performance Unload for OS/390 Release 1
       - APAR PQ59838
     - IMS High Performance Load for OS/390 Release 1
       - APAR PQ59841
    4. If you are to reorganize HALDB by using IPR Driver, the
     following maintenance must be applied to IMS Version 7:
     APARs PQ36991, PQ38822, PQ50606, and PQ59200
    5. If you are to use DBD decoding function of IPR Driver, IPR
     Unload, or IPR Reload, the following product is required in
     addition to the products and the maintenance listed in items
     1 and 3:
     - IMS Library Management Utilities for OS/390 Release 1
       (5655-E04)
       - The maintenance provided by APAR PQ58966 must be applied
  | 6. If you are to reorganize HISAM or SHISAM by using IPR
  |  Driver, the following maintenance must be applied:
  |  - IMS High Performance Load for OS/390 Release 1
  |    - APAR PQ61448
  
  Chapter 2. IMS Parallel Reorganization Driver
  2.1 Overview
  |  By using IPR Driver, you can reorganize a HISAM, SHISAM,
  |  HDAM, HIDAM, PHDAM, or PHIDAM database in a single job step.
     :
     :
     IPR Driver renames the shadow data sets with the original
     data set names after a successful reorganization. This is
     called the data set name swapping or just name swapping.
  |  The name swapping process can be automated for HDAM, HIDAM
  |  and HISAM if the database has no logical relationship.
     The name swapping process can always be automated for HALDB
     even if the database has a logical relationship.
     :
     :
  2.6 JCL Requirements
  2.6.3 Considerations for Database Data Sets
  2.6.3.1 Database and Primary Index
     :
     :
     A HIDAM database requires at least four DD names and four
     data set names: that is, a DD name and a data set name are
     required for primary index and each data set group for input
     and output database.
  |
  |  A HISAM database requires at least four DD names and four
  |  data set names: that is, a DD name and a data set name are
  |  required for primary and overflow data sets for input and
  |  output database.
  |
  |  SHISAM database and root-only HISAM require at latest two
  |  DD names and two data set names: that is, a DD name and a
  |  data data set name are required for primary data set for
  |  input and output database.
  
     If the database contains multiple data set groups, each data
     set group requires two pairs of DD names and data set names,
     one for input and the other for output.
  

APAR Information

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

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

  UQ67179

Modules/Macros

• HPSGCM00 HPSGGDIB HPSGRA10 HPSGRD00 HPSGTM00
  

Fix information

• Fixed component name

  IMS PARALLEL RE

• Fixed component ID

  5655F7400

Applicable component levels

• R210 PSY UQ67179

     UP02/06/17 P F206

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.