APAR status
Closed as program error.
Error description
Server region abends with an ABEND0C4 protection exception (interruption code: 0004). The abend is generated when attempting to write CPU data to an SMF record asynchronously. This is caused by internal processing that copies the CPU data from the source buffers to the destination buffers where the length of the source data exceeds the size of the allocated destination buffer. The Threads reporting the 0C4 shows the following: Naive thread: DSA Entry E Offset Statement Load Mod Program 1 bboosmfs(unsigned int,unsigned int,char*,unsigned int,char*, +00000000 *PATHNAM 2 SMFRequestActivity::cutSmfSt9AsyncRecord(char*,char*,char*,i +000014E8 *PATHNAM 3 Java_com_ibm_ws390_sm_smf_SmfJActivity_cutSmfSt9AsyncRecord +00000FE6 *PATHNAM 4 FFISYS +00000570 *PATHNAM FFISYS Java thread: Java stack frames: bp: 0x000000003653ab70 method: void com/ibm/ws390/sm/smf/SmfJActivity.cutSmfSt9AsyncRecord(byte[], byte[], byte[], int, String, String, byte[], byte[], byte[], byte[], byte[], byte[], byte[], byte[], byte[], byte[], String, boolean, boolean, long, long, long, long, long, long, int, long, long, int, String, int, String, int, String, byte[], byte[]) (Native Method) bp: 0x000000003653ac58 method: void com/ibm/ws390/asynchbeans /services/smf/SmfAsyncBeanServiceContext.generateSMFRecordFromC ontext()source: SmfAsyncBeanServiceContext.java:773 bp: 0x000000003653ada8 method: void com/ibm/ws390/asynchbeans /services/smf/SmfAsyncBeanDataService.pop(com.ibm.ws.asynchbean s.ServiceContext,com.ibm.ws.asynchbeans.CallInfo) source: SmfAsyncBeanDataService.java:506 bp: 0x000000003653ae80 method: void com/ibm/ws/asynchbeans/J2 EEServiceManager.popContext(com.ibm.ws.asynchbeans.AsynchContex tDescriptor,java.util.Map, java.util.Set, com.ibm.ws.asynchbeans boolean) source: J2EEServiceManager.java:632 bp: 0x0000000000000000 method: void com/ibm/ws/asynchbeans/J2 EEContext.pop(com.ibm.ws.asynchbeans.AsynchContextDescriptor)sou bp: 0x000000003653afe8 method: commonj.work.WorkException com /ibm/ws/asynchbeans/J2EEContext.run(com.ibm.websphere.asynchbea ns.EventSource,com.ibm.ws.asynchbeans.AsynchContextDescriptor, commonj.work.Work, commonj.work.WorkListener, com.ibm.ws.asynchbeans.J2EEContext, com.ibm.ws.asynchbeans.WorkEventStatusListener, com.ibm.ws.asynchbeans.WorkTimeoutListener, com.ibm.ws.asynchbeans.CJWorkItemImpl, int, int) source: J2EEContext.java:1111
Local fix
A possible workaround would be to issue the following console command (not persistent across server restarts): F <server>,SMF,REQUEST,ASYNC,OFF Or set the environment variable: server_SMF_request_activity_async to zero on the server.
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V9.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4/ABENDS0C4 in bbooboam in a * * WebSphere Application Server for z/OS * * servant. * **************************************************************** * RECOMMENDATION: * **************************************************************** With server_SMF_request_activity_async and server_SMF_request_activity_CPU_detail enabled for SMF 120 Subtype 9 records an 0c4 abend can occur in bbooboam when copying the CPU information into a destination buffer. This is caused by processing that copies the CPU data from a source buffer to a destination buffer where the length of the source data exceeds the size of the allocated destination buffer. Traceback of abending thread DSA Entry E Offset Statement Load Mod Program 1 bboosmfs(unsigned int,unsigned int,char*,unsigned int,char*,) 2 SMFRequestActivity::cutSmfSt9AsyncRecord(char*,char*,char*,i) 3 Java_com_ibm_ws390_sm_smf_SmfJActivity_cutSmfSt9AsyncRecord
Problem conclusion
Changed the code to not write past the end of the destination buffer. The fix for this APAR is targeted for inclusion in fix pack 9.0.5.9. For more information, see 'Recommended Updates for WebSphere Application Server': https://www.ibm.com/support/pages/node/715553
Temporary fix
Comments
APAR Information
APAR number
PH37257
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2021-05-14
Closed date
2021-07-01
Last modified date
2021-07-01
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
R900 PSY
UP
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"900"}]
Document Information
Modified date:
16 July 2021