PI43900: PARALLEL JOB MANAGER SUBJOB STUCK IN SUBMITTED STATE.

8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.0.0.5: WebSphere Extended Deployment Compute Grid V8.0 Fix Pack 5
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
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

• Parallel Job Manager subjob remains in submitted state after
  the Endpoint's servant region is cancelled and a new one is
  started.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All WebSphere Compute Grid V8 zOS users of  *
  *                  the Parallel Job Manager function.          *
  ****************************************************************
  * PROBLEM DESCRIPTION: A Parallel Job Manager subjob that      *
  *                      has been submitted and dispatched to    *
  *                      the Endpoint remains in submitted       *
  *                      state after the Endpoint's servant      *
  *                      region is cancelled and a new one is    *
  *                      started.                                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When the new Endpoint servant region is started, the status of
  all in-flight jobs is set to "execution failed" or
  "restartable" and sent to the scheduler.  The status set is
  dependent on the job type. If the job had not yet reached the
  point where the job type was set, a NullPointerException was
  thrown and the status of the job was
  never set to the correct status.
  

Problem conclusion

• The code was changed to check for a null job type before
  trying to use it to determine the status of the job.
  The fix for this APAR is currently targeted for inclusion in
  WebSphere Compute Grid fixpack 8.0.0.5 and WebSphere
  Application Server 8.5.5.8.  Please refer to the Recommended
  Updates page for delivery information:
  http://www.ibm.com/support/docview.wss?uid=swg27022998
  or
  http://www.ibm.com/support/docview.wss?uid=swg27036319
  

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

  WXD Z COMP GRID

• Fixed component ID

  5655V6201

Applicable component levels

• R800 PSY

     UP