Fixes are available
8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
8.0.0.4: WebSphere Extended Deployment Compute Grid V8.0 Fix Pack 4
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
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.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.14: WebSphere Application Server V8.5.5 Fix Pack 14
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
With WCG V8.0 the job log in the restart case contains the output of the previous failed run. This behavior can lead to incorrect actions by operators support team because only careful evaluation of the log timestamps will reveal the portion belonging to the current execution.
Local fix
Careful evaluation of the log timestamps will reveal the portion belonging to the current execution.
Problem summary
**************************************************************** * USERS AFFECTED: Users of WebSphere Compute Grid v8.0 and * * above * **************************************************************** * PROBLEM DESCRIPTION: Job log of restarted job contains * * logs from previous execution. * **************************************************************** * RECOMMENDATION: * **************************************************************** On the endpoint, job logs are not stored per execution. They are stored per jobid. Therefore, when a user restarts a job, job logs from the new execution are written in the same directory as the previous execution.
Problem conclusion
The runtime on the endpoint has been updated to create a timestamp directory under the jobid directory. For each execution, job logs that are generated will be stored in the timestamp directory. This will be the default behavior. If a user would like to see the behavior where all job executions' joblogs are stored under the jobid directory, set this websphere variable "USE_TIMESTAMP_FOR_JOBLOG"= false The fix for this APAR is currently targeted for inclusion in WCG fixpack 8.0.0.4 Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?uid=swg27022998
Temporary fix
Comments
APAR Information
APAR number
PM96316
Reported component name
WXD Z COMP GRID
Reported component ID
5655V6201
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-09-03
Closed date
2014-02-03
Last modified date
2014-03-12
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
Document Information
Modified date:
28 April 2022