PI28421: LUW REQUESTER GETS SQL30020N ERROR ATTEMPTING TO CONNECT INTO DB2 VIA THE SECPORT WHEN SSL HAS NOT BEEN PROPERLY CONFIGURED

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• DB2DDF DB2DRDA defect pi28421 dpi28421
  A DB2/z requester may receive an SQL30020N error with Reason
  Code 0x124C if it attempts to use the SECPORT and SSL has not
  been setup or configured correctly. A trace of the failure shows
  the DB2/z server returned a DRDA ACCSECRD reply without a
  required EXCSATRD. The SQL30020N error is issued because of this
  incorrect DRDA flow.
  SQL30020 124C
  ***************************************************************
  Additional Symptoms and Keywords:
   SQLCODE -30020 SQLCODE30020 SQL30020N
   DSNL030I MSGDSNL030I DSNLTEXC 00D31205 RC00D31205
  

Local fix

• Use SQL port for connection, or properly configure SSL for
  SECPORT.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
  ****************************************************************
  * PROBLEM DESCRIPTION: An invalid DRDA reply may be returned   *
  *                      when a remote client accesses DB2 via   *
  *                      a SECPORT that is not configured to     *
  *                      accept secured traffic.                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A remote client application attempts to access a DB2 for z/OS
  server via its secure port (SECPORT), as opposed to its
  standard SQL port (TCPPORT), but the connection is not
  configured for secure traffic.  As a result, DB2 issues message
  DSNL031I with reason code 00D31205 and rejects the connection,
  which is expected.
  However, if DB2 received a chained DRDA command sequence, DB2
  will return an invalid DRDA reply.
  

Problem conclusion

• When a 00D31205 reason code condition is detected as part of a
  DRDA chained command sequence, DB2 has been changed to return a
  DRDA compliant reply.  DB2 will now return a DRDA PRCCNVRM
  (CoNVersational PRotoCol error Reply Message) reply containing
  DRDA SRVDGN (SeRVer DiaGNostic) information that actually
  describes the 00D31205 reason code condition that was detected
  at the DB2 server.
  Users should be aware that external symptoms may appear to have
  not changed.  That is, prior to the change, the application
  will have likely received SQLCODE -30020, which is associated
  to a non compliant DRDA reply.  With the change, an SQLCODE
  -30020 will likely still be returned, although it will now be
  associated to a different cause (the reply is now DRDA
  compliant but an unexpected error was still encountered).
  In order to prevent the -30020 condition, users should take
  action as described by the DB2 for z/OS 00D31205 reason code.
  

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:

  UI23644 UI23645

Modules/Macros

•    DSNLTEXC
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RA10 PSY UI23644

     UP14/12/20 P F412

• RB10 PSY UI23645

     UP14/12/20 P F412

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.