PM76385: PDALSTRL/PNTLSTRL VALUE IS NOT THE LARGEST/MAXIMUM PARTITION KEYSTRING SIZE FOR A HALDB.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• PNTLSTRL and hence PDALSTRL, should have maximum/largest key
  length of the all the defined partitions defined in a HALDB.
  In this customers environment, PNTLSTRL and PDALSTRL is set to
  2 not 19 that is the true max size of the key length.
  DFSPSM10 code will be modified correct this base code error.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All IMS V11 HALDB (High Availability Large   *
  *                 Database) users who have defined different   *
  *                 KEYSTRNG lengths for the partitions.         *
  ****************************************************************
  * PROBLEM DESCRIPTION: Records, that belong to a set of        *
  *                      partitions with a certain KEYSTRNG, are *
  *                      inserted into the wrong partitions.     *
  ****************************************************************
  * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
  ****************************************************************
  User has a HALDB that has 222 partitions and a partition
  selection exit (PSE). The partitions are selected by account
  number or part of the account number. 16 of the 222 partitions
  are dedicated to a single account and are defined to DBRC with a
  KEYSTRNG of 19. The rest of the partitions are defined with a
  KEYSTRNG of 2. Two key tables are constructed and the length of
  each table entry is a user defined entry length plus the largest
  string length (PDALSTRL). PDALSTRL is 1 (length-1) and not 18 as
  expected so the 16 dedicated partitions are not selected and
  their records are inserted in other partitions. A batch
  unload/reload puts the records back in their proper partitions.
  The problem is PDALSTRL (DFSPDA) and PNTLSTRL (DFSPNT) both
  contain a length of 2 and not the longest defined key string
  (KEYSTRNG).
  During system initialization of all partitioned database DDIRs
  DBRC is called to obtain partition definition data.  The length
  of the longest KEYSTRNG is returned in the field XDL_MAXPSLEN.
  This first call to DBRC is only for the first 12 partitions and
  DBRC will need to be called again and again until all partition
  definition data has been retrieved for all partitions in the
  HALDB.  XDL_MAXPSLEN will not have the longest KEYSTRNG until
  all partition definition data has been retrieved.  The problem
  is DFSPSM10 does not get the value from XDL_MAXPSLEN on the
  subsequent DBRC calls and PDALSTRL and PNTLSTRL are updated to
  contain the longest KEYSTRNG of the first 12 partitions.
  

Problem conclusion

• GEN:
  KEYWORDS:
  
  *** END IMS KEYWORDS ***
  DFSPSM10 has been changed to get the value from XDL_MAXPSLEN
  after each call to DBRC which will cause PDALSTRL and PNTLSTRL
  to be updated to contain the longest KEYSTRNG.
  

Temporary fix

• *********
  * HIPER *
  *********
  

Comments

APAR Information

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

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

  016AC4Ÿ PM78786 PM78787 UK90810

Modules/Macros

• DFSPSM10
  

Fix information

• Fixed component name

  IMS V11

• Fixed component ID

  5635A0200

Applicable component levels

• R100 PSY UK90810

     UP13/01/15 P F301 Ž

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.