IBM Support

PK85563: TRAS0024I DID NOT GET PRINTED IN JOBLOG WHEN THE ERROR MESSAGE WAS LARGER THAN LOGSTREAM'S MAXBUFSIZE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The TRAS0024I message did not get written out in the joblog when
    the error message was larger than the logstream's configured
    MAXBUFSIZE while the original message did not get printed in
    any logs.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V7.0                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: When WebSphere Application Server for   *
    *                      z/OS attempts to write a message to a   *
    *                      log stream and the message is larger    *
    *                      than the log stream's MAXBUFSIZE, a     *
    *                      TRAS0024I informational message is      *
    *                      written to the error log, but the       *
    *                      content of the original message is      *
    *                      not written.                            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When WebSphere Application Server encounters an error
    attempting to write a message to a log stream, the IXGWRITE
    return code and reason code are written to the error log along
    with the original message. For IXGWRITE reason code 809
    (message too big), a TRAS0024I informational message is written
    to the error log, but the content of the original message is
    not written.
    

Problem conclusion

  • We removed the TRAS0024I informational message when IXGWRITE
    fails with reason code 809. All errors encountered while
    writing to a log stream result in a BBOO0082E error message
    with the return code and the reason code, and now the
    original message will also be written to the error log.
    
    APAR PK85563 is currently targeted for inclusion in
    Service Level (Fix Pack) 7.0.0.9 of WebSphere
    Application Server
    
    Please refer to URL:
    //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack availability.
    

Temporary fix

Comments

  • ž**** PE10/06/16 PTF IN ERROR. SEE APAR PM16512  FOR DESCRIPTION
    

APAR Information

  • APAR number

    PK85563

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-04-28

  • Closed date

    2009-08-13

  • Last modified date

    2010-07-19

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

    PK85438

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

Fix information

  • Fixed component name

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R700 PSY UK55133

       UP10/03/26 P F003

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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
10 February 2022