IBM Support

PM81423: THE CONNECT API FOR JAVA LOGGING HAS BEEN ENHANCED FOR INCREASEDUSABILITY AND IMPROVED LOGGING CONTROL FOR CLIENT APPLICATIONS.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Currently, the Connect API for Java overwrites the existing
    log file with the name specified in the
    ApiLoggingConfiguration object when logging is started. Due
    to this behavior, previously logged messages are overwritten.
    
    Currently, the file handler of the Connect API logger is not
    exposed. The client application cannot use the API logger
    for programmatic logging control.
    
    In the Connect API log file, the value of the correlator
    token for a synchronous callout transaction is printed in
    EBCDIC (Cp1047), which might not render correctly in some
    environments.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All IMS Enterprise Suite V2R2                *
    *                 IMS Connect API for Java users.              *
    ****************************************************************
    * PROBLEM DESCRIPTION: The Connect API for Java logging has    *
    *                      been enhanced for increased usability   *
    *                      and improved logging control for        *
    *                      client applications.                    *
    ****************************************************************
    * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
    ****************************************************************
    Currently, the Connect API for Java overwrites the existing
    log file with the name specified in the
    ApiLoggingConfiguration object when logging is started. Due
    to this behavior, previously logged messages are overwritten.
    
    Currently, the file handler of the Connect API logger is not
    exposed. The client application cannot use the API logger
    for programmatic logging control.
    
    In the Connect API log file, the value of the correlator
    token for a synchronous callout transaction is printed in
    EBCDIC (Cp1047), which might not render correctly in some
    environments.
    

Problem conclusion

  • GEN:
    KEYWORDS:
    
    *** END IMS KEYWORDS ***
    The Connect API for Java logger can now append log entries to
    an existing log file. The client application can set whether
    the logger appends new entries or overwrites the existing
    entries with a new method:
    setLoggerToAppendMode(boolean aBooleanAppendValue). The
    default value for this method is set to FALSE to retain the
    Connect API's original behavior.
    
    The log file handler has been exposed with a new method:
    getLoggerFileHandler()
    
    The synchronous callout correlator token value is now
    converted to displayed in  hexadecimal for better readability.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM81423

  • Reported component name

    IMS ENTERPRISE

  • Reported component ID

    5655T6200

  • Reported release

    223

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2013-01-25

  • Closed date

    2013-02-15

  • Last modified date

    2013-03-04

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

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

    UK91746

Modules/Macros

  • HWSCAJJ  HWSCAJS
    

Fix information

  • Fixed component name

    IMS ENTERPRISE

  • Fixed component ID

    5655T6200

Applicable component levels

  • R223 PSY UK91746

       UP13/02/19 P F302

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.

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"223","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
04 March 2013