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
The batch packager creates a completely new version of the manifest file for the JAR file referenced by -jarfile. Also, there are couple more issues associated with this: 1. In the printSyntax() method the property nonxadsjndiname is wrongly spelled. 2. In the output of the batch packager the version is not shown: "[INFO] BatchPackager Version: null"
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of WebSphere Compute Grid version * * 8.0 * **************************************************************** * PROBLEM DESCRIPTION: The batch packager creates a new * * manifest file. This new file does not * * include the information from the * * existing manifest file. The batch * * packager also does not show valid * * version, and there is a typo in the * * syntax help output. * **************************************************************** * RECOMMENDATION: * **************************************************************** The batch packager generates a new manifest file when it packages the application. However it does not include the data from the existing manifest file of the jar in the application. The batch packager displays "null" version, and the help syntax has a typo.
Problem conclusion
The batch packager has been updated to include the data from existing manifest file. The version of the batch packager also has been updated, and the typo corrected for the syntax. The fix for this APAR is currently targeted for inclusion in 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
PI05203
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-10-31
Closed date
2014-04-07
Last modified date
2014-04-07
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