IBM Support

II06573: SQLCODE -30080 RCPRI0004 RCSEC000A SENSE084B6031

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as canceled.

Error description

  • 5740XYR00
    User at an AR receives SQLCODE -30080 with primary
    return code 0004 (or 0003 in case of OS/2 AR) and
    secondary return code 000A (or 084B6031 in case of
    OS/2 AR) when accessing a DB2 server.
    This may be caused by a definitional error at the DB2
    server.  This symptom can occur when the MAXDBAT value
    at a DB2 server is set to zero (do not allow any servers
    threads at a DB2 server).
    The DB2 server will issue message DSNL030I with CSECT
    DSNLAGNT and reason 00D300F9 which describes the condition.
    The DB2 server will then deallocate the conversation with
    a sense code of 084B6031.  Deallocating with this sense
    code will cause the requester to receive a primary
    return code of 0004 and a secondary return code of 000A.
    If DB2 is also the AR, the DB2 AR will issue message:
      DSNL500I CSECT DSNLVRPL RCPRI 0004 RCSEC 000ASENSE 084B6031
    and the application will receive SQLCODE -30080 0004 (000A).
    If OS/2 is the requester, the application will receive:
      SQL30080N  A communication error "0003-084B6031" occured
      sending or receiving data from the remote database.
    
    Unless the DSNL500I message is noticed (if AR is DB2) on
    the MVS console (which will contain the sense code information
    084B6031 which may be more descriptive), or the DSNL030I
    message is noticed on the DB2 server console, the user may
    not be able to determine the cause of the failure from the
    SQLCA information returned to the AR application.
    This informational APAR is therefore created to assist users
    with the probable cause of the RCPRI004 RCSEC000A that may
    be seen.
    To correct the problem, the MAXDBAT value at the DB2 server
    should be changed to a value greater than zero.
    *********************************************
    Additional symptoms and keywords:
    5740XYR00 DB2DDF DB2DRDA1
    MSGDSNL030I MSGDSNL030 DSNL030I DSNL030
      DSNLAGNT 00D300F9 RC00D300F9
    MSGDSNL500I MSGDSNL500 DSNL500I DSNL500
      RCPRI0004 0004 RCSEC000A 000A SENSE084B6031 084B6031
    SQLCODE30080 SQL30080N SQL30080 -30080
    

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

  • Closing informational APAR.
    

APAR Information

  • APAR number

    II06573

  • Reported component name

    PB LIB INFO ITE

  • Reported component ID

    INFOPBLIB

  • Reported release

    001

  • Status

    CLOSED CAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    1992-12-07

  • Closed date

    1992-12-07

  • Last modified date

    1992-12-07

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

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

Fix information

Applicable component levels

[{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
13 December 2020