Fixes are available
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.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
Skip record processing works for the job reader but doesn't work for job writer. The exception is not skipped and the job stops processing.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of WebSphere Batch Function * * within IBM WebSphere Application Server * * V8.0 and V8.5. * **************************************************************** * PROBLEM DESCRIPTION: Batch skip record processing * * applications using JPAWriter are * * ignoring defined Exceptions * **************************************************************** * RECOMMENDATION: * **************************************************************** User defined Exceptions for batch skip record processing are being ignored by JPAWriter pattern.
Problem conclusion
The JPAWriter functionality in the batch skip record processing pattern was catching the original exception and rethrowing the exception as a different exception type. A modification was made to ensure the original exception was thrown, thus matching up with those defined by the user for skip record processing. The fix for this APAR is currently targeted for inclusion in WebSphere Compute Grid fixpack 8.0.0.5. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?uid=swg27022998 The fix for this APAR is currently targeted for inclusion in WebSphere Application Server fixpack 8.5.5.6. Please refer to the Recommended Updates page for delivery information: http://www-01.ibm.com/support/docview.wss?uid=swg27036319
Temporary fix
Comments
APAR Information
APAR number
PI32545
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-01-12
Closed date
2015-01-27
Last modified date
2015-01-27
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
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
27 April 2022