PK25090: AFTER INSTALLING APAR PK11407 THE GENERATED VSAM STATEMENTS FOR THE PHIDAM RECORDSIZE DEFINITION ARE INCOR 06/05/19 PTF PECHANGE

APAR status

• Closed as program error.

Error description

• DBDGEN output ´RECOMMENDED VSAM DEFINE CLUSTER PARAMETERS´
  *NOTE1
  DEFINE CLUSTER (NAME(        ) -
  INDEXED KEYS (20,5) -
  REUSE -
  RECORDSIZE (24,24)) -
  DATA (CONTROLINTERVALSIZE (4096))
  are incorrect. The RECORDSIZE should be (25,25).
  Using the above VSAM statements results in the following IDCAM
  error messages:
  IGD17103I CATALOG ERROR WHILE DEFINING VSAM DATA SET
  data.set.name
  RETURN CODE IS 204 REASON CODE IS 0 IGG0CLEP
  IGD17219I UNABLE TO CONTINUE DEFINE OF DATA SET
  index.data.set.name
  IDC3031I KEY EXTENDS BEYOND MAXIMUM RECORD LENGTH
  IDC3009I ** VSAM CATALOG RETURN CODE IS 204 - REASON CODE IS
  IGG0CLEP-0
  IDC3003I FUNCTION TERMINATED. CONDITION CODE IS 12
  

Local fix

• Modify the RECORDSIZE(x,x) parameter.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All IMS R910 users running DBDGEN for        *
  *                 HALDB PHIDAM with apar/ptf PK11407/UK08782   *
  *                 applied.                                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: Message IGD17103I catalog error while   *
  *                      defining VSAM data set dsname return    *
  *                      code is 204 reason code is 0 IGG0CLEP   *
  *                      was issued when running a JCL job to    *
  *                      define and allocate a PHIDAM primary    *
  *                      index dataset using the recommended     *
  *                      VSAM defined cluster recordsize.        *
  ****************************************************************
  * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
  ****************************************************************
  After apar PK11407 was installed, the recommended recordsize of
  the PHIDAM index data set was always less than the PHIDAM index
  LRECL by one in the case the length of the root key is even.
  This value is incorrect, and if used, it would cause the DEFINE
  IDCAMS job to fail with MSGIGD17103I.
  *
  Apar PK11407 inadvertently decremented the record size of the
  PHIDAM primary index segment by one when its record size is odd.
  This was done on the basis that the PHIDAM primary index segment
  contained one extra byte of segment code that was not needed.
  However, for PHIDAM, the segment prefix is calculated correctly
  with 5 bytes of prefix (1 delete byte + 4 bytes of the address
  of the root segment). This caused the recordsize to be less than
  the segment length and the IDCAMS DEFINE job then failed with
  message IGD17103I catalog error.
  *
  The code change made by PK11407 needs to be moved from the PINDX
  section to the PSINDEX section in macro DBDLRECL.
  

Problem conclusion

• AIDS: RIDS/DBS RIDS/GEN DBS GEN
    DEP: PCSS/SECINDX D/SECINDX PCSS/HIDAM D/HIDAM
    GEN:
  
  *** END IMS KEYWORDS ***
  DBDLRECL macro.
  Modify macro DBDLRECL macro to undo the logic change made by
  PK11407, and move it to the PSINDEX section.
  

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:

  UK15630

Modules/Macros

• DBDLRECL
  

Fix information

• Fixed component name

  IMS V9

• Fixed component ID

  5655J3800

Applicable component levels

• R900 PSY UK15630

     UP06/06/26 P F606 «