PK72628: DDF -30080 SQLSTATE 08001 FROM DSNLVCNS USING SNA AND DB2 DATASHARING SYSIBM.LULIST SUBSETTING WITH PK64405 APPLIED

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• DB2DDF DDFL09 DB2SNA DB2DSHR defect pk72628 dpk72628
  With DB2 datasharing group and apar PK64405 applied, may receive
  -30080 sqlstate 08001 if using sysibm.lulist subsetting to
  access members of the group. This is due to servers in the
  subset not returning a weight when PK64405 is applied.
  
  SRVLST may contain a member of the group that is not in lulist
  or SRVLST may contain no available members.
  *******************************************
  Additional symptoms and keywords:
    SQLCODE -30080 SQLCODE30080 SQL30080N
    MSGDSNL501I DSNL501I SENSE CODE 087D0001 SENSE087D0001
  
  
  
  NOTE: With the apar applied, the requester system may issue a
  DSNL500I sense=0864000 or -30080 SQLERRP=DSNLVCN for a member of
  the remote server datasharing group that is listed in the
  requester's sysibm.lulist but the server member is down and not
  available.
  The DSNL500I would be issued only once on initial CNOS
  negotiation between the requester and the member of
  the server group that is down.
  
  SQLCODE=-30080 SQLERRM=0008 0000-087D0001
  

Local fix

• no local workaround
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Distributed Data Facility (DDF) users    *
  *                 using SNA to communicate with a DB2 for      *
  *                 z/OS data sharing group.                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: Error message DSNL501I is displayed     *
  *                      due to VTAM sense code 087D0001 with    *
  *                      an invalid VTAM LU name in the          *
  *                      message, and/or, a z/OS application     *
  *                      intermittently receives                 *
  *                      SQLCODE -30080, after APAR PK64405      *
  *                      (PTFs UK37272 in V8 and UK37273 in V9)  *
  *                      is applied.                             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The VTAM LU name included in the DSNL501I error message was not
  a valid VTAM LU name, but was the value found in the LINKNAME
  column of the row in the SYSIBM.LOCATIONS table for the
  LOCATION being accessed by the application.  For SNA
  communications, if the LINKNAME column value is not a real
  VTAM LU name, then it must be a value which matches the
  LINKNAME column of a set of rows in the SYSIBM.LULIST table.
  This kind of setup is called member-specific access.  With
  member-specific access, one can then setup the SYSIBM.LULIST
  entries such that a subset of the members of the remote data
  sharing group can be accessed by the requesting DB2 subsystem
  or data sharing group.  With member-specific access, the
  requesting DB2 subsystem determines which specific member it
  will access in response to a request from an application to
  connect to the remote location.  The requesting DB2 utilizes
  information returned to it via a periodic communication it
  makes to any member of the serving data sharing group called
  the DB2 SNA Sysplex Transaction Program to determine which
  LUNAME should next be used to access the remote location.
  The information returned in response to the DB2 SNA Sysplex
  TP request contains a prioritized, weighted, list of the
  LUNAMEs of the members of the serving data sharing group.
  However, the DB2 SNA Sysplex TP response can contain the
  LUNAMEs of ALL of the currently started members of the
  serving data sharing group, not just the subset, as defined
  in the requesting DB2.  Another possible DB2 SNA Sysplex TP
  response is that no LUNAMEs which match those in the requesting
  DB2's LULIST for the LOCATION are returned.  It is WLM on the
  serving data sharing group systems which provides the
  prioritized, weighted, server information and, if it determines
  that a system should no longer receive additional workload
  requests, it will not return a server data sharing group's
  member LUNAME.  This is the reported problem situation.
  With APAR PK64405 (PTFs UK37272 in v8 and UK37273 in v9)
  applied, in order to protect the integrity of the requesting
  DB2's LULIST, the code implemented by the APAR fix made sure
  that the information returned in the DB2 SNA Sysplex TP
  response was ignored for any LUNAME which did not match the
  LUNAMEs defined in the requesting DB2's LULIST.  However, the
  APAR fix went too far when there was no information returned
  for any of the LUNAMEs in the requesting DB2's LULIST.  In
  this situation, the code implemented by the fix to APAR
  PK64405 basically told the requesting DB2 that no LUNAME of
  the serving data sharing group was a candidate for SNA
  communication which resulted in the application receiving
  SQLCODE -30080, and error message, DSNL501I, possibly being
  displayed reporting that the LUNAME in error was the LINKNAME
  value of the row for the LOCATION in the SYSIBM.LOCATIONS
  table.  When the stress on the server system capacity was
  relieved, successful communications were then able to be
  established to the server data sharing group.
  

Problem conclusion

• DB2 has been changed to correct the code implemented by APAR
  PK64405 when the DB2 SNA Sysplex TP response contains no
  information for the LUNAMEs defined in the requesting DB2's
  LULIST.  When this situation is detected, DB2 will now be told
  that any LUNAME of the LULIST can be tried, and, if the LUNAME
  which was successfully used to process the DB2 SNA Sysplex TP
  request is defined in the LULIST, DB2 will be further told to
  use that LUNAME to establish the next SNA communication to the
  remote location.
  Note: A SQLCODE -30080 being returned to an application is a
    valid error situation, if all the members of the serving data
    sharing group whose LUNAMEs are defined in the requesting
    DB2's LULIST, are either down or DDF is stopped.
  

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:

  UK40882 UK40883

Modules/Macros

• DSNLCRFL
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• R810 PSY UK40882

     UP08/11/05 P F811

• R910 PSY UK40883

     UP08/11/05 P F811

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.