PI43348: DB2 DDF QWHDSVNM VALUE IS BINARY ZERO PADDED

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• DB2DDF defect pi43348 dpi43348
  QWHDSVNM value may be binary zero padded for a DB2
  DDF server thread when a non z/os requester flows
  an EXCSAT with an SRVNAM value that is less than 18
  characters and is not blank padded in a new connection
  
  A QWHDSVNM_VAR and QWHDSVNM_OFF will also be
  provided, when it's not really necessary, and this QWHDSVNM_VAR
  value will also be binary zero padded.
  **************************************************************
  Additional Symptoms and Keywords:
   CCBEUWN Work Station Name CLIENT WRKSTNNAME CLIENT_WRKSTNNAME
   QWHDSVNM QWHDSVNM_VAR binary zero null padded
   EXCSAT.SRVNAM
   SQLSPECIALREG
  

Local fix

• no local workaround/fix
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
  ****************************************************************
  * PROBLEM DESCRIPTION: The initial CURRENT CLIENT_WRKSTNNAME   *
  *                      special register value may be           *
  *                      incorrectly padded with binary zeroes   *
  *                      instead of blanks.                      *
  *                      The QWHDSVNM field may also be          *
  *                      incorrectly padded with binary zeroes   *
  *                      and the QWHDSVNM_Var field, via a non   *
  *                      zero QWHDSVNM_Off value, may also be    *
  *                      unnecessarily provided and it too is    *
  *                      incorrectly padded with binary zeroes.  *
  *                      The condition occurs after applying     *
  *                      the change for APAR PM94679.            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The initial CURRENT CLIENT_WRKSTNNAME special register value
  may be incorrectly padded with binary zeroes, instead of
  blanks, relative to remote non DB2 for z/OS requester
  environments (such as DB2 Connect) that provide a DRDA EXCSAT
  SRVNAM value that is not blank padded.
    Note: The condition will not occur relative to DB2 for z/OS
      requester environments because DB2 for z/OS requester
      environments provide a DRDA EXCSAT SRVNAM value that is
      blank padded.
  This incorrect binary zero padded value may also be reflected
  in the QWHDSVNM trace record header field.  The QWHDSVNM_Var
  field may also be unnecessarily provided, via a non zero
  QWHDSVNM_Off value, and it too will be incorrectly padded with
  binary zeroes.
  The condition occurs after applying APAR PM94679, but only when
  the DRDA EXCSAT SRVNAM value is accepted on behalf of a new
  connection.  The condition will not occur when the DRDA EXCSAT
  SRVNAM value is accepted on behalf of an existing connection
  that is being reused by the remote requester environment.
  

Problem conclusion

• DSNLTEXC is changed to anticipate that the DRDA EXCSAT SVRNAM
  value may not be blank padded.
  

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:

  UI28905 UI28906

Modules/Macros

• DSNLTEXC
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RA10 PSY UI28905

     UP15/07/11 P F507

• RB10 PSY UI28906

     UP15/07/11 P F507

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.