IBM Support

PI95333: THERE IS NO WAY TO DETECT IF A COMPUTE GRID BATCH JOB IS PRODUCING GROSSLY EXCESSIVE OUTPUT IN ITS JOB LOG.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If a Compute Grid job produces very very much output in its job
    log, the the Compute Grid's scheduler is impacted. When a user
    tries to display the job with the Job Management Console, the
    Scheduler could abend, and/or cause Compute Grid jobs to fail.
    Additionally, the file system containing the job log itself
    could become full, which could cause problems even beyond
    Compute Grid.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Java Batch                           *
    ****************************************************************
    * PROBLEM DESCRIPTION: There is currently no mechanism to      *
    *                      obtain an alert or warning as to        *
    *                      whether a WebSphere Java Batch job may  *
    *                      be runaway and producing excess log     *
    *                      output.                                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A WebSphere Java Batch job that produces too much log output
    can potentially cause a file system space issue and also impact
    other operations that access the job logs, like the Java Batch
    Job Scheduler.
    

Problem conclusion

  • A new WebSphere environment variable has been added:
    JobLogCountAlert
    
    This variable is used to specify the number of job log parts
    that can be written before an audit message is issued
    indicating that number has been reached.  After which, the
    count is reset and the tracking will start anew.
    
    By default, this is set to 0 (disabled).
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 9.0.0.10.  Please refer to the Recommended Updates
    page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI95333

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-03-16

  • Closed date

    2018-12-03

  • Last modified date

    2018-12-03

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

  • 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

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"900","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
18 October 2021