PK33846: IPR DRIVER ALLOWS NEWDBD=DDNAME AND IC=YES CONTROL STATEMENTS

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• IPR Driver rejects the keyword combination NEWDBD=ddname and
  IC=YES.  This APAR removes the restriction.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of IPR Driver of                   *
  *                 IMS Parallel Reorganization for              *
  *                 z/OS Version 3 Release 2 (FMID=H25N320)      *
  ****************************************************************
  * PROBLEM DESCRIPTION: IPR Driver allows NEWDBD=ddname and     *
  *                      IC=YES control statements.              *
  ****************************************************************
  * RECOMMENDATION: Apply the maintenance for this APAR.         *
  ****************************************************************
  This APAR provides the following functional engancements
  about the NEWDBD control statement of IPR Driver:
  
   1. IC=YES control statement can be specified together.
  
   2. The change of the randomizing parameters of HDAM database
   in the new DBD is allowed.
  
   3. The SORT control statement for the IPR Reload task
   can be specified to run the physical sequeintial sort
   before the reload process. For the change of
   the randomizing parameters of HDAM database, SORT=COND
   is recommended.
  
   4. When IPR Driver does not accept the new DBD, the reason
   is shown in the HPSG0303E message and the snaps of
   the original DBD and the new DBD are produced in the HPSSNAP
   data set. The HPSSNAP data set is allocated dynamically.
  
  
  The following APARs are also needed to use this new function:
  - PK33847  IMS High Performance Unload (FMID: H1IN110)
  - PK34472  IMS High Performance Load (FMID: H1IM210)
  - PK35237  IMS High Performance Image Copy (FMID:H1J0320)
    or PK35129 IMS High Performance Image Copy (FMID:H1J0410)
  - PK35073  IMS High Performance Pointer Checker (FMID:HPC2220)
  

Problem conclusion

Temporary fix

Comments

• ========================
  = Documentation Change =
  ========================
  IBM IMS Parallel Reorganization for z/OS User's Guide
  (SC18-9228-02) should be changed as follows:
  ================================================================
   2.0 IMS Parallel Reorganization Driver
  
   2.7 Control statements
    2.7.4 Control statements for Reload task
  
     ____________________________________________________________
    | Table 13. Control statements for Reload task               |
    |------------------------------------------------------------|
    | keyword|Acceptable|Default| Description                    |
    |        | values   |       |                                |
    |------------------------------------------------------------|
    | :      | :        | :     | :                              |
    |------------------------------------------------------------|
  | | SORT   | YES, NO  | NO    | Specifies whether to run       |
  | |        | or COND  |       | physical sequential sort       |
  | |        |          |       | before the reload process. See |
  | |        |          |       | "SORT control statement" in    |
  | |        |          |       | topic 4.7.26.                  |
    |------------------------------------------------------------|
  ================================================================
   2.7.8 Description of control statements for Reorganization
         Manager
   2.7.8.20 NEWDBD control statement
  
    The NEWDBD control statement enables you to change a DBD
    during a reorganization. You cannot change DBDs for a HALDB
    unless you reorganize the entire database.
      ________________________________________________________
     |                                                        |
     | >>__NEWDBD=ddname___________________________________>< |
     |________________________________________________________|
  
    The NEWDBD control statement specifies a 1- to 8-byte DD name
    (ddname) of the library containing the new DBD definition
    (the DBD that is used by the Reload task and the Index Builder
    task). The library defined by the IMS DD statement contains
    the original definition (the DBD that is used by the Unload
    task).
  
    Note: Any DD name that is reserved for system use cannot
    be specified in the NEWDBD statement. For details of
    the reserved DD names, see "DD statements" in topic 2.6.2.
  
    When you change DBDs, you are responsible for ensuring that
    the new DBD is valid. The DBD changes that are supported
    in parallel reorganization are described in "Supported DBD
    changes" in topic 2.7.8.20.
    If you need to change any DBD parameter that is not
    supported in parallel reorganization, you must reorganize
    the database by using stand-alone utilities. In general,
    you should make major changes to database structures
    outside of the reorganization.
  
    For the post-reorganization processing that is required
    when the NEWDBD control statement is specified,
    see "Considerations for post-reorganization processing"
    in topic 2.7.8.20.
  
  D If IC=YES is specified, the NEWDBD control statement is not
  D allowed.
  
    Supported DBD changes: When using a new DBD for a non-HALDB,
    you can change any DBD parameters except the following:
     - database organization
     - access method
     - number of data set groups
     - DD names
     - segment hierarchy
  D  - randomizing module and randomizing parameters
     - adding or deleting secondary indexes
     - changing a fixed-length segment to a variable-length
       segment, and vice versa lessening the length of the
       sequence field of a segment changing the start position of
       the sequence field
     - changing the type of the sequence field from M to U
   D - increasing the length of the root sequence key of
   D   an HDAM database
   D - changing the length of the root segment of an HDAM
   D   database if the root segment does not have
   D   sequence field
     - adding a logical relationship
  
    When you use a new DBD for a HALDB, the following restrictions
    apply in addition to the above:
     - Logical relationships must not be deleted.
     - The definition of partitioned secondary indexes must not
       be changed.
  
    If INDEXBLD=YES is specified, changing the secondary index
    definition to one that is not supported by IMS Index Builder
    is not allowed.
  
  | For the following changes of segmengt compression,
  | DECOMPRESS=YES should be specified for the unload task.
  |  - adding, deleting, or changing COMPRTN parameter
  |    of a SEGM statement
  |  - changing the length of a compressed segment
  |
  | For the following changes on HDAM, SORT=YES or SORT=COND
  | should be specified for the load task.
  |  - changing randomizing module name or randomizing parameters
  |  - increasing the length of the root sequence key
  
    Considerations for post-reorganization processing:
  
  |  If NEWDBD=YES is specified, DBRC PROHIBIT
  |  AUTHORIZATION flags are not turned off automatically
  |  after the nameswap processing.
     This enables you to perform some tasks such as
     running the ACBGEN or updating DBD libraries
     before you allow the access to the reorganized
     database.
     You must run the DBRC utility (DSPURX00) to turn this flag
     off after you have made an image copy of the database
     and before using the database. For details,
     see "Manual DBRC notification processing" in topic 2.9.3
     steps 2 to 3 apply in this case, because the NOTIFY.REORG
     commands are issued by Reorganization Manager
     in the IPR Driver job step.
  
  ================================================================
  4.0 The IPR Reload utility
  4.7 Control statements
    4.7.26 SORT control statement
  
    Specifies whether to run the physical sequential sort
    processing before reloading.
    This control statement is optional. If you do not explicitly
    specify this control statement, SORT=NO is used.
   ________________________________________________________
  |               _NO___                                   |
  | >>__SORT = __|_YES__|_______________________________>< |
  |              |_COND_|                                  |
  |________________________________________________________|
  
    YES
      Runs physical sequential sorting before the reload process.
      It sorts in the physical sequence of the block, then the
      RAP numbers.
  
    NO
      Does not run the sort process.
  
    COND
      Runs the physical sequential sorting if any of the following
      conditions is satisfied:
  
  |   When using IPR Driver with REORGINPUT=DBDS option and
  |   APAR PK33847 is applied for HP Unload, the following
  |   conditions are used as the criteria:
  |   -  Any of the following is changed between unload and
  |      reload processes:
  |      -  Randomizing module name
  |      -  RAP number
  |      -  The maximum BLK/CI number in RAA
  |      -  The starting position of the root key
  |      -  The length of the root key
  |      -  Whether the root segment has key sequence field
  
  |   When using IPR Driver with REORGINPUT=ULDS option or using
  |   IPR Reload utility, the following conditions are used as
  |   the criteria:
      -  Load API function is used.
      -  The input unloaded data set was created in the *CS
         format.
      -  The input unloaded data set was not created by HP Unload
         with the CHECKREC=YES option.
      -  The input unloaded data sets are concatenated.
  
        When the input unloaded data set was created by HP Unload
  |     with APAR PK33847 and with the CHECKREC=YES option,
        the following conditions are also used as the criteria:
        -  DB organization is changed from (P)HIDAM to (P)HDAM.
        -  The input unloaded data set was created via a
           secondary index database.
        -  Any of the following is changed between unload and
           reload processes:
           -  Randomizing module name
           -  RAP number
           -  The maximum BLK/CI number in RAA
           -  The starting position of the root key
           -  The length of the root key
  |        -  Whether the root segment has key sequence field
  
    The HDAM/PHDAM data must be in the order for reloading, so if
    it is not in that order, SORT=YES or SORT=COND is required.
    Instead of reloading with SORT=YES or SORT=COND, you can run
  | PSSR before reloading except when using IPR Driver with
  | REORGINPUT=DBDS option.
    This statement is applicable for HDAM/PHDAM, and there are
    some restrictions as follows:
    -  This statement is exclusive with the USERHDR= and the
       USERHDRX= control statements.
    -  The data updated by the DATXEXIT= control statement is
       not supported.
    -  The root key updated by USEREXIT is not supported.
    -  The compressed root key data created by specifying the
       DECN option is not supported for the reload process.
  D -  The statement is ignored when the program is run under the
  D    IPR Driver.
  
  | If you specify SORT=COND, it is determined in the reload task
    whether to run the physical sequential sort processing
    according to the criteria listed above. Therefore, in some
    cases, it does not sort input unloaded data sets even if the
    sort process is required for the reload process. In such a
    case, you have to run PSSR before reloading or specify
    SORT=YES instead of SORT=COND.
  ================================================================
   10.0 Messages and codes
   10.3 Messages
   10.3.2 HPSG messages
  
  (The HPSG0303E message is modified and the HPSG0345I message is
   added.)
  ----------------------------------------------------------------
  | HPSG0303E UNSUPPORTED DBD CHANGE: DBD=dbd_name (change,ii)
  | HPSG0303E UNSUPPORTED DBD CHANGE: DBD=dbd_name,DD=dd__name
  |                   (change,ii)
  | HPSG0303E UNSUPPORTED DBD CHANGE: DBD=dbd_name,SEGM=segmname
  |                   (change,ii)
    Explanation: An unsupported DBD change is requested by
    the new DBD that is specified by the NEWDBD control statement.
  | The change for the data set group ddname or the segment
  | segmname is one of the following change types and
  | the change is not supported. ii indicates the internal code.
  |
  |  Change      Description
  |  ACCESS      Changing DB organization or access method
  |  DSGROUP     Changing data set group
  |  HIERARCHY   Changing segment position in the hierarchy
  |  SEGM_NAME   Changing segment name
  |  SEGM_LEN    Changing segment length type; fixed or variable
  |  SEGM_KEY    Changing segment sequence key field
  |  COMPRTN     Changing COMPRTN= parameter or compressed key
  |  LOGICAL     Changing logical relationship
  |  INDEX       Changing index relationship
  |  RANDOMIZER  Changing randomizing module parameter for PHDAM
  |
    For the DBD changes supported in parallel reorganization,
    see NEWDBD control statement.
    System Action: The IPR Driver ends with a return code of 8.
    If DECODEDBD=YES and DECODESXD is specified, the DBD sources
    are produced in the HPSOUT2 data sets.
  | The DBD snap dump for the original DBD and new DBD is produced
  | in the HPSSNAP data set.
    Programmer Response: Check if the correct DBD is used as
    the new DBD. If the correct one is used, consider
    using the stand-alone reorganization utilities of IPR.
  ----------------------------------------------------------------
  | HPSG0345I COMPRTN IS CHANGED IN NEW DBD: DBD=dbd_name,
  |           SEGM=segmname,ii
  |
  | Explanation: One of the following parameters is modified
  | in the new DBD which is specified by the NEWDBD control
  | statement:
  | - The parameters on the SEGM COMPRTN parameter
  | - The length of a segment or a sequence key field which is
  |   compressed
  | System Action: The IPR Driver continues processing.
  | If Unload-task DECOMPRESS=NO is specified, the message
  | is followed by message HPSG0303E and the IPR Driver ends
  | with a return code of 8.
  | Programmer Response: None
  ----------------------------------------------------------------
  
  ================= 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:

  UK20109

Modules/Macros

• HPSGCM00 HPSGGIOB HPSGGIO0 HPSGGVT0 HPSGLINK
  HPSGMSGT HPSGODA0 HPSGRD00 HPSGRD20 HPSGRR00 HPSGTJ00 HPSGTY00
  H25N320J
  

Fix information

• Fixed component name

  IMS PARALLEL RE

• Fixed component ID

  5655F7400

Applicable component levels

• R320 PSY UK20109

     UP06/12/03 P F612

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.