PI21788: FORWARD FIT HALDB TOOLKIT V3.2 APARS TO DBSP V2.1 HALDB TOOLKIT

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• Forward fit HALDB Toolkit V3.2 APARs to DBSP V2.1 HALDB Toolkit
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of IBM IMS Database Solution Pack V2.1 *
  *                 IMS HALDB Toolkit                            *
  ****************************************************************
  * PROBLEM DESCRIPTION: Forward fit of fix in HALDB Toolkit     *
  *                      V3.2 APAR PM88015, PM88021, PI07978,    *
  *                      PI09883, PI11396, PI13953, and PI17672. *
  ****************************************************************
  * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
  ****************************************************************
  This APAR provides the following new functions:
  
   1. ANALYZEPART and MAINTAIN with PARTNUM spread the high keys
      over that number of partitions as evenly as possible.
   2. For the MAINTAIN function's KEYS processing, a new option of
      KEYSORDR is added.
      This new option results in the high-keys found in the
      KEYS(dd) being sorted in EBCDIC order, then assigned to the
      partitions in their own ascending EBCDIC order.
   3. ANALYZEPART accepts databases with logical relationships.
  
  
  In addition, this APAR fixes the following problems:
  
   1. MAINTAIN job fails with SB37 on shadow dataset even though
      VOLALLO parameter is specified.
   2. When a database contains a root segment with null key value
      x'00..00', an incorrect Repartitioning Report can be
      generated.
   3. HALDB Toolkit can cause ABENDS0C4 when an open error for a
      RECON dataset, such as IEC161 058(018)-061 for RECON1,
      occurs.
   4. CONVERT and MAINTAIN functions can cause ABENDS0C4 in
      IHCYILIU0 when IMS Library Integrity Utilities (LIU)
      library is concatenated to the STEPLIB.
  

Problem conclusion

Temporary fix

Comments

• The following modules have been changed:
  IHCUANA0 IHCULEV0 IHCWANA3 IHCWANA4 IHCWCPY0 IHCWDBR1 IHCWDBR2
  IHCWLIU0 IHCWTDBA IHCWTDBB IHCWTDBG IHCWTDB0 IHCWTDB2 IHCWTDB3
  IHCWTDB4 IHCWTDB5 IHCWTDRC IHCWTKOV IHCWUNLF IHCWUNL0 IHCWUOW
  IHCWWANA IHCYCCDF IHCYDBD3 IHCYDBD5 IHCYDBD8 IHCYLIU0 IHCYMSGT
  IHCYOF11 IHCYOF12 IHCYOF13
  
  
  ========================
  = DOCUMENTATION CHANGE =
  ========================
  IBM IMS Database Solution Pack for z/OS Version 2 Release 1
  IMS High Availability Large Database Toolkit for z/OS User's
  Guide (SC19-4102-00)
  ----------------------------------------------------------------
  Chapter 2. Simulating HALDB using ANALYZEPART
    Simulating conversion to a HALDB
      About this task
        By simulating the effect of the HALDB partition settings,
        you can determine the most effective partition settings
        before you convert a full-function database to HALDB by
        using the CONVERT command.
  |     About a database with logical relationships, the database
  |     specified in the DBD parameter is only to be simulated.
  |     All logically related databases are not to be simulated.
  
    Simulating repartitioning of a HALDB
      About this task
        By simulating the effect of the new partition settings,
        you can determine the most effective partition settings
        before you consolidate or split partitions by using the
        MAINTAIN command.
  |     About a database with logical relationships, the database
  |     specified in the DBD parameter is only to be simulated.
  |     All logically related databases are not to be simulated.
  
  
  Chapter 4. Maintaining HALDB using MAINTAIN
   Maintaining databases offline
    table 5. Common MAINTAIN functions
    ADD:
  | Scenario:
  | Add, change, or delete partitions such that four partitions
  | result, and that their high-keys are assigned in EBCDIC order
  | based on the high-keys found in KEYSIN
  |
  | MAINTAIN Parameters:
  | MAINTAIN DBD(xxx) PARTITION(*)-
  |          KEYS(KEYSIN) KEYSORDR(Y)
  |
  | KEYSIN input:
  | //KEYSIN DD*
  | A999
  | G999
  | M999
  | Z999
  
  
    MAINTAIN command parameters
    table 6. MAINTAIN command parameters
    ADD:
    KEYS
  
    If the high keys are created during analysis, there must be
    at least as many database records as there are requested
    partitions.
  | If KEYSORDR(Y) is specified with KEYS, then the keys are
  | sorted in EBCDIC order, then assigned to the partitions in
  | are name order (also EBCDIC order).
    If PARTNUM, PARTSIZE, or KEYS is not ...
  
  
  | KEYSORDR
  
  | When KEYS(dd) is specified, IMS HALDB Toolkit reads the
  | high-key values from the KEYS(dd) and then assigns them to
  | partitions in ascending partition number order by issuing
  | CHANGE.PART commands to DBRC.  When KEYSORDR is also
  | specified, IMS HALDB Toolkit subsequently reassigns the
  | high-keys to the partitions, in both their individual
  | ascending EBCDIC order, by issuing CHANGE.PART commands again.
  |
  | The CHANGE.PART commands that are issued when reassigning
  | the high-keys are in ascending EBCDIC order of partition name,
  | which is the same order as is presented by a DBRC LIST.DB
  | command. KEYSORDR processing is done whether adding or
  | deleting partitions, or changing partitions' attributes.
  |
  | This option can also be used for the single purpose of
  | reorganizing partitions' high-keys, which is accomplished by
  | placing unchanged high-keys in the KEYS(dd).
  |
  | Specify Y or N. The default value is N.
  |
  | When the KEYSORDR option is specified, PARTITION(*) is also
  | required.
  

APAR Information

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

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

  UI19674 010PC2Ÿ 010PC2Ÿ

Modules/Macros

• IHCUANA0 IHCULEV0 IHCWANA3 IHCWANA4 IHCWCPY0
  IHCWDBR1 IHCWDBR2 IHCWLIU0 IHCWTDBA IHCWTDBB IHCWTDBG IHCWTDB0
  IHCWTDB2 IHCWTDB3 IHCWTDB4 IHCWTDB5 IHCWTDRC IHCWTKOV IHCWUNLF
  IHCWUNL0 IHCWUOW  IHCWWANA IHCYCCDF IHCYDBD3 IHCYDBD5 IHCYDBD8
  IHCYLIU0 IHCYMSGT IHCYOF11 IHCYOF12 IHCYOF13
  

Fix information

• Fixed component name

  IM DB SOLUTION

• Fixed component ID

  5655S7700

Applicable component levels

• R210 PSY UI19674

     UP14/07/21 P F407

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.