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

9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

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 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