A fix is available
APAR status
Closed as program error.
Error description
ABENDS0C4 occurs in a nodeagent when using local communications from a nodeagent to an application server that is being stopped. The callback stack that generated for the NA TCB that had the 0C4 looked like this: CF_Local_Connection::clientSend(LocalComm_IOV_Header*,int,in -04850B48 *PATHNAM CF_Local_Connection::async_send_msg(msghdr*,int,bool,bool,in +00000AAA *PATHNAM CF_TCP_Request::write(void*,msghdr*,int,int,bool,bool) +0000011A *PATHNAM Java_com_ibm_ws_tcp_channel_impl_ZAioTCPChannelCPPUtilities_ +00000794 *PATHNAM RUNJAVATHREAD -01F17B88 *PATHNAM javaProtectedThreadProc +000000AA *PATHNAM j9sig_protect +000005B2 *PATHNAM javaThreadProc +00000054 *PATHNAM thread_wrapper +0000049A *PATHNAM CEEVROND +000011F4 CEEPLPKA
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V6.1 * * * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4/ABENDS0C4 occurs in a * * nodeagent when using local * * communications from a * * nodeagent to an application server * * that is being stopped. The 0C4 abend * * occurs because the private storage of * * the target application server needed * * by the local communications PC is gone. * * * **************************************************************** * RECOMMENDATION: * **************************************************************** When a application server is being stopped there is a timing window in which the private storage for the PC routine has been removed but the PC entry in the LXLIST has not. This can result in an Abend S0C4 if the nodeagent attempts to use local communucations to access the application server as it is stopping.
Problem conclusion
During controller task level termination processing an LXFRE was added to remove the PC routine from the LXLIST to prevent access to the PC routine, whose private storage has been removed, during controller termination. APAR PM26869 is currently targeted for inclusion in Service Level (Fix Pack) 6.1.0.35 of WebSphere Application Server V6.1. Please refer to URL: //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970 for Fix Pack availability.
Temporary fix
Comments
APAR Information
APAR number
PM26869
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
610
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-11-16
Closed date
2010-11-30
Last modified date
2011-01-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
BBGUBINF BBOUBINF
Fix information
Fixed component name
WEBSPHERE FOR Z
Fixed component ID
5655I3500
Applicable component levels
R610 PSY UK62676
UP10/12/17 P F012
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
10 February 2022