PI34479: ADDITIONAL SUPPORT OF IMS V14 HALDB 8-GB OSAM DATA SETS.

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• ANALYZEPART and MAINTAIN functions already support IMS V14 HALDB
  8-GB OSAM data sets via APAR PI27633.
  In addition to that, this APAR will enable the following
  functions to support the IMS V14 HALDB 8-GB OSAM data sets.
  - BACKUPDBRC
  - CHECK
  - CONVERT
  - COPYDBRC
  - HALDBCOPY
  - HALDBLOAD
  - RESETILK
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of IBM IMS Database Solution Pack V2.1 *
  *                 IMS HALDB Toolkit.                           *
  ****************************************************************
  * PROBLEM DESCRIPTION: Provide additional support of IMS V14   *
  *                      HALDB 8-GB OSAM data sets for IMS       *
  *                      Database Solution Pack V2.1 IMS HALDB   *
  *                      Toolkit.                                *
  ****************************************************************
  * RECOMMENDATION: Apply the maintenance for this APAR.         *
  ****************************************************************
  ANALYZEPART and MAINTAIN functions already support IMS V14 HALDB
  8-GB OSAM data sets via APAR PI27633.
  In addition to that, this APAR enables the following functions
  to support the IMS V14 HALDB 8-GB OSAM data sets.
  1. Using a single step batch process
     - BACKUPDBRC
     - CHECK
     - CONVERT
     - COPYDBRC
     - HALDBCOPY
     - HALDBLOAD
     - RESETILK
  2. Using an ISPF user interface
     - BACKUPDBRC
     - CONVERT
     - COPYDBRC
     - HALDBCOPY
     - HALDBLOAD
     - MAINTAIN
  
  In addition, this APAR fixes the following problems:
  
   1. After running HALDBCOPY function, ILK and/or KEYSTRNG
      can be incorrect.
   2. CHECK function may report Partition pointer information
      for M-V data sets incorrectly.
   3. For the ISPF user interface, the following problems are
      fixed:
        - Project KSDS data set can overflow.
        - Option 'C' and 'E' of Setup Parameter panel does not
          work correctly.
  

Problem conclusion

Temporary fix

Comments

• Code has been added to support the IMS V14 HALDB 8-GB OSAM data
  sets additionally for IMS HALDB Toolkit.
  
  =========================
  = 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 3. Converting to HALDB using CONVERT
   CONVERT command parameters
    Table 4. CONVERT command parameters
  
    PARTSIZE
  
    Specifies the size of partitions to create.
  
    PARTSIZE cannot be used with PARTNUM or KEYS.
  | The value can be in the following ranges:
  |  - For a VSAM full-function database without OSAM(Y) parameter
  |    1 - 4095.
  |  - For an OSAM full-function database and a VSAM full-function
  |    database with OSAM(Y) parameter, 1 - 8191.
  
    Specifying this parameter causes IMS HALDB Toolkit to find the
    high keys. The specifications are analyzed to determine whethe
    the requested partitioning is feasible.
    If either PARTNUM, PARTSIZE, or KEYS is not specified, the
    default setting PARTSIZE(2048) is used.
  
  Chapter 29. Messages and codes
  
  | IHC01187E PARTSIZE must be less than 4096 when you do not
  |           specify OSAM(Y)
  |
  | Explanation: The PARTSIZE value must be less than 4096 when
  | you do not specify OSAM(Y).
  |
  | System action: The process terminates.
  |
  | User response: Either specify the OSAM(Y) or specify less
  | than 4096 as the PARTSIZE value.
  
    IHC01200E FROMDBD dbdname1 TODBD dbdname2 compare failed:
    reason
  
    Explanation: The merge process detected one or more errors.
    Potential reasons include:
    - DBD names are identical
    - Segment structure is different
    - Segment definition is different
    - DBD type is different
    - DBD has secondary index
    - DBD has logical relation
    - DBD has different partition selection exits
    - IHCPSEL0 is defined different
  | - Maximum capacity of OSAM is different
  
    System action: The process terminates.
  
    User response: None. Merging these two HALDBs is not possible.
  

APAR Information

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

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

  UI26247

Modules/Macros

• IHCPCOD2 IHCPCOH2 IHCPCON2 IHCPSETH IHCSINDB
  IHCSRELE IHCUANAA IHCUANA0 IHCUANA1 IHCUANA2 IHCUANA3 IHCUANA4
  IHCUANA5 IHCUANA6 IHCUANA7 IHCUANA8 IHCUANA9 IHCULEV0 IHCUTIC0
  IHCWANA3 IHCWANA4 IHCWCPY0 IHCWDBRN IHCWDBR1 IHCWJCLG IHCWLIU0
  IHCWMI00 IHCWMI10 IHCWMI20 IHCWMI30 IHCWMI40 IHCWMI50 IHCWMI60
  IHCWMI70 IHCWMI90 IHCWTDBA IHCWTDBB IHCWTDBF IHCWTDBG IHCWTDB0
  IHCWTDB1 IHCWTDB2 IHCWTDB3 IHCWTDB4 IHCWTDB5 IHCWTDB6 IHCWTDB7
  IHCWTDB9 IHCWTDRC IHCWTKOV IHCWWANA IHCXDSIN IHCYMSGL IHCYMSGT
  

Fix information

• Fixed component name

  IM DB SOLUTION

• Fixed component ID

  5655S7700

Applicable component levels

• R210 PSY UI26247

     UP15/03/28 P F503

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.