Fixes are available
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
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
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11
APAR status
Closed as program error.
Error description
An optimization for the JIT Compiler in Java 8 for DAA (Data Access Acceleration, to access data in the COBOL Binary Coded Decimal (BCD) format) can emit code which makes use of hardware instructions designed to handle data in the BCD format. If these instructions encounter data that is not in BCD format the instruction will generate a Data Exception, interrupt code is 0c7 with a DXC code of x'00' / 0x00. DXC code 00 -> Decimal-operand data exception In a WebSphere environment on z/OS this causes the WebSphere provided LE Extension Routine BBORLEXT to take a SVC Dump. Dump title is: DUMP TITLE=COMPON=WEBSPHERE Z/OS, COMPID=5655I3500, ISSUER=BBORLEXT,ABEND IN (MODULE NAME NOT KNOWN) Dump analysis would show the pgm check in JIT Compiled code (Use jdmpview command "info jitm" to dump the addresses in memory for the compiled code). The method involved will either be, or will have inlined, method com/ibm/dataaccess/DecimalData.convertPackedDecimalToLong The failing instruction will most likely be a EX pointing to a ZAP. Please open a PMR for help with analysis is you are not sure if this APAR applies to your specific case. This APAR is taken to suppress the dump for this case. Expected operation is that control returns to the JVM signal handler, operation continues and an IllegalArgumentException is thrown.
Local fix
Switch -Xjit:disableIntrinsics causes the JIT to not emit the instructions used for DAA. After setting -Xjit:disableIntrinsics you should clear the Shared Class Cache with clearClassCache.sh for the server involved, otherwise an AOT compiled version of the DAA code with the DAA instructions might still be used.
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V8.5 and V9.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: A dump of a abend 0c7 reason code * * 00000000 is encountered when running * * WebSphere Application Server for z/OS. * **************************************************************** * RECOMMENDATION: * **************************************************************** Dump of a ABEND0C7/ABENDS0C7 reason code 00000000 is taken by bborlext because application data was encountered that is not in BCD format. bborlext should not take a dump because in Java 8 the JIT generates instructions like ZeroAndAdd that will abend when bad data is encountered. The abend tells them there was bad data and their signal handler gets control to go back to the program with an appropriate exception.
Problem conclusion
Updated bborlext to not dump when an abend 0c7 reason code 00000000 occurs. APAR PI76878 is currently targeted for inclusion in Fix Packs 8.5.5.12 and 9.0.0.5 of WebSphere Application Server. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 In addition, please refer to URL: http://www.ibm.com/support/docview.wss?rs=404&uid=swg27006970 for Fix Pack PTF information.
Temporary fix
Comments
APAR Information
APAR number
PI76878
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-02-20
Closed date
2017-04-26
Last modified date
2017-05-02
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
WEBSPHERE FOR Z
Fixed component ID
5655I3500
Applicable component levels
R850 PSY
UP
Document Information
Modified date:
04 May 2022