IBM Support

IC82972: XA AES CONNECTION TO DB2 Z/OS SERVER GETS SQL30082N RC=17

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • XA connection against DB2 z/os v9.1 CM
    mode server with Advanced Encrpytion (AES) fail with.
    SQL30082N rc=17. The issue can happen when client forces
    reconnect through Syncpoint manager ( SPM).
    
    Impacted release:v9.7.4,v9.7.5,v9.7.6 DB2 Connect Server
    

Local fix

  • catalogging  tcpip loop back or setting registry variable
    DB2CONNECT_IN_APP_PROCESS=NO (then restart instance)
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * DB2 Version 9.7 Fix pack 4 users                             *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * On DB2 v9.7 FP5 making XA connection against DB2 z/os v9.1   *
    * CM mode server with Advanced Encryption (AES) fail with      *
    * SQL30082N rc=17.  This same XA connection works fine before  *
    * upgrading to v9.7 FP5.                                       *
    *                                                              *
    * For XA connection, DB2 client forces reconnect to force spm  *
    * connection on gateway and it reuses the security manager     *
    * level that was returned by DB2 z/os v9.1 server.             *
    *                                                              *
    * When security manager level returned by server is lower than *
    * 9, then user will hit this problem. If the server has        *
    * security manager level 9 or higher, then it'll avoid this    *
    * problem. But note that DB2 z/os v9.1 server with security    *
    * manager level 9 or lower is supported with AES connection.   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 Version 9.7 Fix pack 7                        *
    ****************************************************************
    

Problem conclusion

  • Problem first fixed in DB2 Version 9.7 Fix pack 7
    

Temporary fix

  • catalogging  tcpip loop back or setting registry variable
    DB2CONNECT_IN_APP_PROCESS=NO (then restart instance)
    

Comments

APAR Information

  • APAR number

    IC82972

  • Reported component name

    DB2 CONNECT

  • Reported component ID

    DB2CONNCT

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-04-27

  • Closed date

    2012-11-20

  • Last modified date

    2012-11-20

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    IC87891

Fix information

  • Fixed component name

    DB2 CONNECT

  • Fixed component ID

    DB2CONNCT

Applicable component levels

  • R970 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.7","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
20 November 2012