PM71847: TOKEN NOT MATCHING BETWEEN DSNT376I AND DSNT501I MESSAGES

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When DB2 issue the resource unavailable message, it might
  happen that the thread tokens are not matching between DSNT376I
  and DSNT501I messages
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All DB2 10 for z/OS users                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: An incorrect token is shown by          *
  *                      MSGDSNT501I                             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Incorrect fields may be used as a source for DSNT501I message
  generation, causing the token to display as 0 or some other
  invalid value.  The reason for picking up these invalid fields
  was a change to the placement of the fields containing token
  information, resulting in unpredictable values obtained from
  irrelevant fields.
  
  An example of the problem:
  
  DSNT375I  @P PLAN=DISTSERV WITH 555
          CORRELATION-ID=db2jcc_appli
          CONNECTION-ID=SERVER
          LUW-ID=GA321515.CF3C.CA1B8EFD0A20=19840     <--- OK
          THREAD-INFO=VGHA21:PrdSvr01:VGHA21:db2jcc_application
          IS DEADLOCKED WITH PLAN=DISTSERV WITH
          CORRELATION-ID=db2jcc_appli
          CONNECTION-ID=SERVER
          LUW-ID=GA320A6A.DE32.120901230632=51329
          THREAD-INFO=VGHA21:sts:vgha21:db2jcc_application
          ON MEMBER DB2P
  
  DSNT501I  = DSNILMCL RESOURCE UNAVAILABLE 645
             CORRELATION-ID=db2jcc_appli
             CONNECTION-ID=SERVER
             LUW-ID=GA321515.CF3C.CA1B8EFD0A20=673975 <-- NOT OK
             REASON 00C90088
             TYPE 00000304
             NAME DBEMM01 .BITUIN  .X'0002B4'.X'09'
  

Problem conclusion

• Code is changed to use the proper token values when issuing
  DSNT501I.
  
  Please note that due to a large number of paths that might issue
  DSNT501I, this APAR does not fix every possible DSNT501I
  message.
  
  Only reported cases are resolved with this APAR.  A global fix
  is planned for a future release.
  
  If, after this APAR is applied, additional DSNT501I messages
  with an incorrect token are encountered and reported, this code
  may be replicated to the appropriate path as necessary.
  

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:

  UK83708

Modules/Macros

•    DSNIRUMS
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RA10 PSY UK83708

     UP12/12/11 P F212

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.