IBM Support

IT39057: INITIAL CONNECTION ERRORS LIKE -4499 ARE NOT COLLECTED IN DIAGNOSTIC DATA THROUGH DB2.JCC.DIAGLEVELEXCEPTIONCODE SETTING

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When initial connection establishment fails with error -4499,
    error is not capture in diagnostic log when the property to
    collect diagnostics only for particular error codes is set.
    
    e.g:
    db2.jcc.diagLevelExceptionCode=-4499
    db2.jcc.dumpDiagLevel=1
    db2.jcc.outputDirectory=C:\\JCC\\Workspaces\\logs
    
    When the application is executed with above properties set(e.g
    in DB2JccConfiguration.properties file), and if application
    receives -4499 error, no diagnostics file is generated under
    location set to db2.jcc.outputDirectory.
    
    The expected behavior is that the logs must be generated only
    for -4499 error under the location db2.jcc.outputDirectory.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Db2 JCC Users                                                *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 V11.1.4.7                                     *
    ****************************************************************
    

Problem conclusion

  • Problem fixed in Db2 V11.1.4.7
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT39057

  • Reported component name

    DB2 CONNECT

  • Reported component ID

    DB2CONNCT

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-11-12

  • Closed date

    2022-01-10

  • Last modified date

    2022-01-10

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

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

    IT39194

Fix information

  • Fixed component name

    DB2 CONNECT

  • Fixed component ID

    DB2CONNCT

Applicable component levels

  • RB10 PSN

       UP

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"11.1"}]

Document Information

Modified date:
04 May 2022