PQ59835: IPR V2 SUPPORTS HALDB AND DBD DECODING.

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• IPR V2 supports HALDB and DBD decoding.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of IMS Parallel Reorganization for *
  *                 z/OS Version 2 Release 1 (FMID=H25N210)      *
  ****************************************************************
  * PROBLEM DESCRIPTION: This APAR provides two new functions:   *
  *                      1. Support of PHDAM and PHIDAM by IPR   *
  *                         Driver                               *
  *                      2. Support of DBD decoding by IPR       *
  *                         Driver, IPR Unload, and IPR Reload   *
  ****************************************************************
  * RECOMMENDATION: Apply the maintenance for this APAR.         *
  ****************************************************************
  This APAR provides the two new functions:
   1. Support of PHDAM and PHIDAM by IPR Driver
   2. Support of DBD decoding by IPR Driver, IPR Unload, and IPR
      Reload
  

Problem conclusion

Temporary fix

Comments

• The documentation for the new functions are provided by
  the following series of APARs including this APAR:
     PQ59835  PQ59836  PQ60330  PQ60338  PQ60339
                             * * *
  ========================
  = 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.2 Processing Requirements
  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
  | 2. For INDEXBLD=YES function of IPR Driver, the following is
  |  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
  Chapter 2. IMS Parallel Reorganization Driver
  2.1 Overview
  |    By using IPR Driver, you can reorganize an HDAM, HIDAM,
  | PHDAM, or PHIDAM database in a single job step. For HDAM and
  | HIDAM, you can optionally reorganize their secondary indexes.
    IPR Driver starts ...
       You can keep the database online and allow read access to
    users during the reorganization, because IPR Driver
  | reorganizes the database or HALDB partition into a shadow
  | database or partition. The database and its indexes need to
    be offline ...
      ...
    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 and HIDAM 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.
       IPR Driver invokes the following sub tasks ...
  2.4 Overview of Parallel Reorganization Tasks
  ### The existing explanation in this section of User's Guide ###
  ### (SH27-1180-00) applies only to HDAM and HIDAM databases. ###
  ### The following two subsections should be added to explain ###
  ### the Parallel Reorganization tasks for HALDB.             ###
  | 2.4.1 Parallel Reorganization of a HALDB Partition <NEW>
  |    This section explains the steps required to reorganize a
  | single HALDB partition by a single IPR Driver job. This is the
  | recommended way to reorganize a HALDB by using IPR Driver.
  | Submitting several IPR Driver jobs to reorganize multiple
  | HALDB partitions concurrently can reduce the reorganization
  | time for HALDB than submitting a job to reorganize them
  | serially. The latter method is explained in the next section
  | although it is not recommended.
  |    Step 0. Setting up processing environments: This step is
  | same as Step 0 for HDAM and HIDAM.
  |    Step 1. Pre-reorganization processing: This step is
  | required if you do not specify IMSCMD=YES. If you do not
  | specify IMSCMD=YES, the HALDB partition to be reorganized must
  | be offline or in read-only mode in a separate step before the
  | IPR Driver job step starts. To do this, one of the following
  | commands must be issued for the HALDB partition to reorganize:
  | - /DBRECOVERY DATABASE part_name GLOBAL NOFEOV (for
  |   DBSHARE=NO in step 2): If you are going to specify
  |   DBSHARE=NO for the IPR Driver job in step 2, issue this
  |   command. This command prevents any authorization for the
  |   HALDB partition part_name during the reorganization.
  | - /DBDUMP DATABASE part_name GLOBAL NOFEOV (for DBSHARE=YES
  |   in step 2): If you are going to specify DBSHARE=YES for the
  |   IPR Driver job in step 2, issue this command. This command
  |   allows read access to the HALDB partition part_name during
  |   the reorganization.
  |    Step 2. Running a Parallel Reorganization job: Submit a
  | parallel reorganization JCL stream for the HALDB partition.
  | This is a required step. For details, see 2.6, "JCL
  | Requirements." The JCL stream for parallel reorganization
  | must include an IDCAMS step, before the IPR Driver job step,
  | to allocated the output (shadow) data sets. For the required
  | data sets, see 2.6.3, "Considerations for Database Data
  | Sets." The name of the partition must be specified by coding
  | the PARTITION control statement. For details, see "PARTITION
  | Control Statement." INDEXBLD=YES cannot be specified. If
  | ILDSBLD=NO is not specified, the output indirect list data
  | set (ILDS) for the partition must be allocated also in the
  | IDCAMS step. If you want any special processing for
  | Reorganization Manager, Unload, or Reload task, code the
  | control statements for each task in the HPSIN DD. For
  | details, see 2.7, "Control Statements."
  |    Step 3. Performing post-reorganization processing: The
  | post-reorganization processing includes the following:
  |  - Data set name swapping
  |  - DBRC notification processing
  | This is a required step. If you specified NAMESWAP=YES and
  | ILDSBLD=YES, Reorganization Manager of IPR Driver swaps the
  | data set names and notifies DBRC of the reorganization
  | automatically. If you did not specify NAMESWAP=YES, you must
  | swap the data set names and do DBRC notification processing
  | manually. ILDS is created by the Reload task by default.
  | But, if you specify ILDSBLD=NO, ILDS must be rebuilt in a
  | separated job step before the DBRC notification processing.
  | If ILDSBLD=NO is specified, the DBRC notification processing
  | is not done automatically even if NAMESWAP=YES is specified.
  | For details, see 2.9.1, "Post-Reorganization Processing."
  |    Step 4. Take an image copy of the partition: An image copy
  | of the reorganized HALDB partition must be taken before it is
  | used by application programs.
  |    Step 5. Start the HALDB partition: The partition must be
  | started explicitly by issuing /START DATABASE command for the
  | partition so that it can be used by online application
  | programs.
  | 2.4.2 Parallel Reorganization of Entire HALDB <NEW>
  |    You can reorganize all HALDB partitions in a single IPR
  | Driver job step by reorganizing each partition sequentially.
  | The required steps are explained below. It is recommended,
  | however, to create an IPR Driver job for each partition and to
  | submit the IPR Driver jobs concurrently.
  |    Step 0. Setting up processing environments: This step is
  | same as Step 0 for HDAM and HIDAM.
  |    Step 1. Pre-reorganization processing: This step is
  | required if you do not specify IMSCMD=YES. If you do not
  | specify IMSCMD=YES, the HALDB to be reorganized must be
  | offline or in read-only mode in a separate step before the
  | IPR Driver job step starts. To do this, one of the following
  | commands must be issued for both the HALDB master database
  | and all partitions of the HALDB:
  | - /DBRECOVERY DATABASE name GLOBAL NOFEOV (for DBSHARE=NO
  |   in step 2): If you are going to specify DBSHARE=NO for the
  |   IPR Driver job in step 2, issue this command. The command
  |   issued for the HALDB master database makes it offline. The
  |   command issued for each HALDB partition prevents any
  |   authorization for the HALDB partition during the
  |   reorganization.
  | - /DBDUMP DATABASE name GLOBAL NOFEOV (for DBSHARE=YES in
  |   step 2): If you are going to specify DBSHARE=YES for the
  |   IPR Driver job in step 2, issue this command. The command
  |   allows only read access to the HALDB during the
  |   reorganization.
  |    Step 2. Running a Parallel Reorganization job: This step
  | is same as step 2 in the preceding section except that the
  | PARTITION control statement is not specified.
  |    Step 3. Performing post-reorganization processing:
  | This step is same as step 3 in the preceding section except
  | that the processing must be done for all partitions.
  |    Step 4. Take an image copy of each partition: An image copy
  | must be taken for each partition of the HALDB before the HALDB
  | is used by application programs.
  |    Step 5. Start the HALDB: Each partition must be started
  | explicitly by issuing /START DATABASE command for each
  | partition. The HALDB master database must be started also so
  | that the HALDB can be used by online application programs.
  | Note: If you define a DBRC DB Group (database group) in which
  |       the HALDB master database and all HALDB partitions
  |       belong, starting the HALDB will be easier.
  2.5 Restrictions
    IPR Driver has the following restrictions:
  | - Parallel reorganization of multiple, but all, HALDB
  |   partitions in a single IPR Driver job is not supported.
  | - INDEXBLD=YES is not supported for PHDAM and PHIDAM
  |   databases. If you want to rebuild any partitioned secondary
  |   index (PSINDEX) of such a database, you must run an Index
  |   Builder job in a separate job step after the parallel
  |   reorganization job step.
    - Parallel reorganization of a database that has a shared
      secondary index is not supported.
  2.6 JCL Requirements
  2.6.2 DD Statements
    STEPLIB DD
     Points to the following library data sets:
     - IMS tools libraries:
       - IPR load module library (mandatory)
         ...
  |    - IMS Library Management Utilities load module library
  |      (optional)
  2.6.3 Considerations for Database Data Sets
  2.6.3.1 Database and Primary Index
    ...
       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.
  |    A PHDAM database requires at least three unique DD names
  | and three unique data set names for each partition to be
  | reorganized: that is, a DD name and a data set name are
  | required for the input and output data sets of each data set
  | group of each partition and a DD name and a data set name are
  | required for the input ILDS for each partition.
  |    A PHIDAM database requires at least five DD names and five
  | data set names for each partition to be reorganized: that is,
  | a DD name and a data set name are required for the primary
  | index and each data set group of each input and output
  | partition and a DD name and a data set name are required for
  | the input ILDS for each partition.
  |    If a logical parent of a unidirectional logical
  | relationship, a bidirectional logical relationship, or a
  | partitioned secondary index (PSINDEX) is defined for HALDB,
  | and ILDSBLD=NO is not specified, a DD name and a data set name
  | are required for the output ILDS for each partition.
  |    If multiple data set groups are defined for PHDAM or
  | PHIDAM, each data set group of each partition requires two
  | pairs of DD names and data set names, one for input and the
  | other for output.
  |    By default, the original data sets and the shadow data sets
  | are allocated dynamically. For details, see 2.6.3.3, "Dynamic
  | Allocation of Input and Output Data Sets." IBM recommends
  | specifying that the input and output data sets be allocated
  | dynamically. The original data sets of a HALDB partition are
  | always allocated dynamically.
  |    On how the DD names for output shadow data sets for
  | non-HALDB are determined, see 2.7.6.3, "DDNMAP Control
  | Statement." The DD names for shadow data sets for a HALDB
  | partition is determined as indicated in the following table:
  |   +----------------------------------------------+
  |   | Table: DD name suffixes for shadow data sets |
  |   +----------------------------------------------+
  |   | Original data set    |A|B|C|D|E|F|G|H|I|J|L|X|
  |   +----------------------------------------------+
  |   | Shadow data set      |M|N|O|P|Q|R|S|T|U|V|Z|Y|
  |   +----------------------------------------------+
  2.6.3.2 Secondary Indexes
  |    Secondary Indexes can be created during the parallel
  | reorganization of a non-HALDB by specifying INDEXBLD=YES.
  | Partitioned secondary indexes for HALDB need not be rebuilt
  | in a usual reorganization that changes neither the database
  | definition nor the partition definition. The following
  | explanation applies to the parallel reorganization of a
  | non-HALDB and its secondary indexes.
       If the use of IMS Index Builder is designated by the
    INDEXBLD=YES option, ...
  2.6.3.3 Dynamic Allocation of Input and Output Data Sets
       The way in which input and output data sets for database
    and indexes are allocated is determined by the DYNALLOC
    control statement.
  |    By default, the data sets are allocated dynamically. For a
  | non-HALDB, the names for the output data sets are determined
    automatically from the data set names defined in the DFSMDA
  | members for the input database and indexes. For PHDAM and
  | PHIDAM, the names for the output data sets are determined from
  | the input data set names registered in RECON. The name of an
  | output database data set (or cluster) consists of the name of
  | the corresponding input data set (or cluster) followed by a
    suffix (the default is .Z). For example, suppose your original
  | data set (or cluster) is named IMS.TESTDB01. By default, the
  | output shadow data set (or cluster) is named IMS.TESTDB01.Z.
  | If you specify 'DYNALLOC=,A', the output data set (or cluster)
    is named IMS.TESTDB01.A. You can specify any alphabetic
    character except T as the suffix. The same rule also applies
  | to the output primary index for a HIDAM database, secondary
  | indexes, and indirect list data sets. The VSAM component names
  | for shadow cluster are need not be conforming to this rule
  | because the component names in the catalog entry are used. For
  | details, see 2.7.6.4, "DYNALLOC Control Statement."
  2.6.5 Considerations for Logical Relationships
  |    If the database to be reorganized is not HALDB and has a
    logical relationship, you must specify the following DDs:
       - DFSURCDS
       - DFSURWF1
  |    These data sets are not required for HALDB even if it has a
  | logical relationship or a partitioned secondary index.
  ### The documentation change continues on to APAR PQ59836.   ###
  

APAR Information

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

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

  UQ65489

Modules/Macros

•    HPSCLAC0 HPSCLA00 HPSCLA10 HPSCMSGT HPSCOPT
  HPSCOPTS HPSGBBL6 HPSGBBL7 HPSGCM00 HPSGCM10 HPSGCM20 HPSGCSC0
  HPSGGDIB HPSGGDLB HPSGGHPE HPSGGHPT HPSGGIOB HPSGGIO0 HPSGGRGB
  HPSGGRG0 HPSGGRMB HPSGGRM0 HPSGHDT0 HPSGLINK HPSGMSGT HPSGOM00
  HPSGOM10 HPSGPCHG HPSGPMA0 HPSGPMC0 HPSGPME0 HPSGPMFT HPSGPMF0
  HPSGPMGR HPSGPMI0 HPSGPMO0 HPSGPMSG HPSGPMT0 HPSGPMX0 HPSGRA00
  HPSGRA10 HPSGRA20 HPSGRA30 HPSGRC00 HPSGRDD0 HPSGRD00 HPSGRM00
  HPSGRM10 HPSGRP00 HPSGRP10 HPSGRP20 HPSGRR00 HPSGRS00 HPSGRS10
  HPSGRS30 HPSGSTMT HPSGTM00 HPSGTR00 HPSGTU00 HPSGUBBL H25N210J
  

Fix information

• Fixed component name

  IMS PARALLEL RE

• Fixed component ID

  5655F7400

Applicable component levels

• R210 PSY UQ65489

     UP02/04/27 P F204

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.