PM88021: USE CHANGE.PART TO CHANGE THE HIGH KEYS OF EXISTING PARTITIONS.

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• Maintain:  The request for this function is to have it use
  CHANGE.PART to change the high keys if existing partitions based
  on the high keys in the KEYSIN DD and New partitions use the
  INIT.PART.  This will keep the partitions in order
  alphabetically
  RFE 30319 - Use CHANGE.PART to change the high keys of existing
  partitions.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of HALDB Toolkit V3R2 can use the  *
  *                 new KEYSORDR option of KEYS processing for   *
  *                 the MAINTAIN function.                       *
  ****************************************************************
  * PROBLEM DESCRIPTION: 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.             *
  ****************************************************************
  * RECOMMENDATION: It is recommended that a TAKEOVER(N) JOB be  *
  *                 run prior to a TAKEOVER(Y) job. This is for  *
  *                 the purpose of examining in advance the      *
  *                 potential results of KEYSORDER processing.   *
  ****************************************************************
  With this APAR, IMS HALDB Toolkit's MAINTAIN function has a new
  option that is activated by adding the KEYSORDR(Y) keyword when
  using the KEYS(dd) feature.  Just as before, 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.  Processing for this new option
  subsequently reassigns the high-keys to the partitions, in both
  their individual ascending EBCDIC order, by issuing CHANGE.PART
  commands.
  
  When the KEYSORDR(Y) option is specified, PARTITION(*) is also
  required; otherwise, all of the HALDB segments might not be
  unloaded then reloaded into the correct partitions.
  Message IHC01182E is issued for any incorrect specification.
  
  When the KEYSORDR(Y) option is specified, the subsequent
  CHANGE.PART commands are issued in ascending EBCDIC order of
  partition name, the same order as is presented by a DBRC
  LIST.DB command. KEYSORDR processing is done whether
  adding or deleting partitions, and/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)
  
  It is worth stating here that in ascending EBCDIC order
  PHDO2A comes before PHDO26, which is opposite from
  alphabetical order.
  
  Taking a KEYSORDR example: If there are two partitions of
  DBD(PHDAM1) named PHDO26 (partition number 1) and PHDO2A
  (partition number 2) and two high-keys of ABC and ABC1 found in
  the KEYS(dd), then the resulting commands issued by Toolkit
  are:
  
  CHANGE.PART DBD(PHDAM1) PART(PHDO2A) KEYSTRNG(ABC1)
  CHANGE.PART DBD(PHDAM1) PART(PHDO26) KEYSTRNG(ABC)
  
  Note that, if necessary, as in this case, DBRC appends X'FF'
  values to these two high-keys out to the length of the
  partition's root key. Therefore, ABC1 comes before ABC.
  
  A subsequent LIST.DB DBD(PHDAM1) command would display
  partitions in ascending EBCDIC order of partition name showing
  the KEYSTRNGs as assigned by Toolkit, in their own ascending
  EBCDIC order.
  
  DBRC does not allow changing a partition's high-key to an
  an existing high-key; therefore, prior to issuing the two
  commands above, by necessity IMS HALDB Toolkit issues the
  following two commands:
  
  CHANGE.PART DBD(PHDAM1) PART(PHDO26) KEYSTRNG(X'FA00000001')
  CHANGE.PART DBD(PHDAM1) PART(PHDO2A) KEYSTRNG(X'FA00000002')
  
  For ease of use, it is recommended that the high-keys specified
  in the KEYS(dd) all have the same length. It is also recommended
  that a MAINTAIN KEYSORDR JOB with the TAKEOVER(N) option be run
  prior to a JOB with the TAKEOVER(Y) option. This for the purpose
  of examining in advance the potential final results of takeover
  processing.
  

Problem conclusion

Temporary fix

Comments

APAR Information

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

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

  UI12009

Modules/Macros

• IHCULEV0 IHCWDBR1 IHCWDBR2 IHCWLIU0 IHCWTDBA IHCWTDBB IHCWTDBG
  IHCWTDB0 IHCWTDB2 IHCWTDB3 IHCWTDB4 IHCWTDB5 IHCWTDRC IHCWTKOV
  IHCWUNL0 IHCYCCDF IHCYMSGT
  

Fix information

• Fixed component name

  IMS HALDB C&M A

• Fixed component ID

  5655I0100

Applicable component levels

• R320 PSY UI12009

     UP13/11/03 P F311

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.