PK32752: ADB2UCUS USING &NAME IN ASYSUTB SYSUT1 CUSTOMIZATION RESULTS IN JCL ERROR WHEN OBJECT NAME LONGER THAN 8 BYTES

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• A DB2 Administration Tool customization variable suggested
  in member ADB2UCUT:
  &NAME     (OBJECT NAME, UP TO 8 BYTES)
  causes a JCL error when used in for the ASYSUTBSYSUT1
  variable and the object name is longer than 8 bytes ( an index
  name for example ).
  

Local fix

• Do not use &NAME to build the DSN
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of DB2 Administration Tool, who        *
  *                 modify the  &ASYSUTB  variable in the        *
  *                 ADB2UCUS  skeleton  to include  &NAME        *
  *                 (object name), may be affected.              *
  ****************************************************************
  * PROBLEM DESCRIPTION: When using  &NAME  to build a  DSN  for *
  *                      &ASYSUTB  in  ADB2UCUS,  the  resulting *
  *                      qualifer could be longer than  8 bytes, *
  *                      causing a JCL error.                    *
  *                      .*                                      *
  *                      When  &NAME  refers to  an index  name, *
  *                      it's length can exceed  8  bytes (up to *
  *                      128 bytes).  This results in an invalid *
  *                      qualifier for the  DSN if &NAME is used *
  *                      as part of ASYSUTB.                     *
  *                      .* Note:                                *
  *                      This  problem  can be avoided by adding *
  *                      code in the  ADB2UCUS skeleton to check *
  *                      whether &NAME  refers  to an index or a *
  *                      table space for the  ASYSUTB  variable, *
  *                      which is  only  used  for  indexes  and *
  *                      table spaces.  If  it's  an index, then *
  *                      &INDEXSPA ,  which  is   limited  to  8 *
  *                      characters,  can  be  used  instead  of *
  *                      &NAME. If the object being processed is *
  *                      a table space,  &INDEXSPA  will  have a *
  *                      null value, which allows for the check. *
  *                      .*                                      *
  *                      The fix for  PK32752 is provided  as an *
  *                      example  to  the   comment  only   file *
  *                      skeleton  ADB2UCUT.  The  corresponding *
  *                      changes  in the  ADB2UCUS  skeleton can *
  *                      be implemented accordingly and in a way *
  *                      that  the  existing   customization  is *
  *                      maintained (via USERMOD).               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  ADB2UCUS using &NAME in ASYSUTB SYSUT1 customization resulted in
  JCL error when OBJECT NAME was longer than 8 bytes
  

Problem conclusion

• Apply the fix and reference the sample fix provided in ADB2UCUT
  for the fix to be added to the ADB2UCUS skeleton.
  

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:

Modules/Macros

•    ADB2UCUT
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• R710 PSY UK20897

     UP06/12/30 P F612

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.