PM78896: MODIFY RECOVERY - DBID/PSID IS NOT CONVERTED IN MESSAGE DSNU381I

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• MODIFY RECOVERY issues message
  DSNU381I  -DP11 340 15:55:48.31 DSNUGSRX - TABLESPACE
  ****011A.****02E4
  The dbname and tsname aren't being reported properly.
  

Local fix

• N.A.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All DB2 10 for z/OS users who observe        *
  *                 unreadable object names in messages          *
  *                 DSNU381I and DSNU380I                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: Object names in messages DSNU381I and   *
  *                      DSNU380I are sometimes unreadable.      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
    User ran a utility which placed a table space (or table space
  partition) into COPY PENDING state.  In the UTILTERM phase of
  most utilities, MSGDSNU381I or MSGDSNU380I are issued to alert
  the user that an object was put into COPY PENDING state, or
  that an object was already in COPY PENDING state and that state
  was not reset by the utility.
    In some cases under normal activity, the object name is
  not properly stored in the Database Exception Table (DBET)
  even when the actual object is properly identified as
  being in COPY PENDING state.
    In such cases, DB2 displays the object name with asterisks
  in the first four characters of both the database and table
  space name ('****'), each followed by a four hexadecimal digit
  dbid and psid, respectively, for example:
  DSNU381I - TABLESPACE ****124F.****2680 IS IN COPY PENDING
    This APAR was requested to improve the likelihood that DB2
  can display the object names properly.
  

Problem conclusion

•   Utility code was changed to detect when objects in COPY
  PENDING state can't be displayed properly in messages
  DSNU381I and DSNU380I.  When possible in these cases, DB2
  will attempt an alternative means to try to capture the
  object names.
  

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:

  UK91812

Modules/Macros

•    DSNUGSRX
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RA10 PSY UK91812

     UP13/03/06 P F303

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.