PI46303: Issuing a STOP command to a Batch job does not result in the job being in the STOPPED state.

8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
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.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

• Due to the existence of a timing window, attempts to stop a
  Batch job may not be successful. This problem is occurring
  when the status of the job does not correctly match the
  series of commands that have been issued.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty Profile                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: Issuing a STOP command to a Batch job   *
  *                      does not result in the job being in the *
  *                      STOPPED state.                          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Due to the existence of a timing window, attempts to stop a
  Batch job may not be successful. This problem is occurring when
  the status of the job does not correctly match the series of
  commands that have been issued.
  

Problem conclusion

• The synchronization has been modified so as to close the
  existing timing window. This prevents the updated job status
  from being lost.
  
  The fix for this APAR is currently targeted for inclusion in fix
  pack 8.5.5.7.  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

  WAS LIBERTY COR

• Fixed component ID

  5725L2900

Applicable component levels

• R855 PSY

     UP