Fixes are available
8.0.0.1: WebSphere Application Server V8.0 Fix Pack 1
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
Obtain the fix for this APAR.
APAR status
Closed as program error.
Error description
During shutdown from WAS server, erep entries for an ABEND00c RSN060B0000 and RSN060B0001 are produced. This are converted ABEND0c4. ABEND0C4 RC10 for TEA: 7350E000 Logrec shows the XCF corresponding ABEND00C RSN060B0001 IXCG2STB for MEMTOKEN: 02000056 00370005 which belongs to: ..... Group: BBBBBBBB Member: MMMMM System: SSSS Member State: Active <------ Memtoken: 02000056 00370005 Permanent Status Recording: OFF System Cleanup Participant: OFF ASID: X'043E' Jobname: IIIIIII Member Association: Address space Address Space STOKEN: 000010F8 00000005 User State: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Time stamp of last update: 03/09/2011 13:33:45.413871 ..... This shows that the group member is still joined (ACTIVE) within XCF group. Page X'7350E000' was referenced because address X'7350EBF8' is the defined XCF GROUP EXIT ADDR. According to VSMDATA the storage area is already freed: FBQE: Addr 2D600000 Size 511A8000 Looking to ASID X'043E' Jobname: ITW3EAI the address space is already terminated. Only basic TCB's are left IEESB605 IEFSD060
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V7.0 and V8.0 * **************************************************************** * PROBLEM DESCRIPTION: EREP contains an ABEND00C * * RSN=060B0000 and RSN=060B0001 after a * * WebSphere Application Server for z/OS * * Controller terminates * **************************************************************** * RECOMMENDATION: * **************************************************************** WebSphere Application Server for z/OS controller address space registers a "group" and "message" exit with XCF's IXCJOIN service. The target exit routines where deleted from storage prior to a successful invocation of the IXCLEAVE service. XCF drove an SRB to the terminating address space where it took an ABEND0C4. XCF's recovery routine logged an ABENDS00C to record the failure.
Problem conclusion
WebSphere's "group" and "message" XCF exits have been moved to storage managed by the Daemon. This ensures that the target exit routines are still in storage while a WebSphere for z/OS controller address space is terminating. The XCF RESMGR that is covering the termination of the WebSphere address space will ensure that the XCF exits are no longer driven after that point. APAR PM40705 is currently targeted for inclusion in Service Level (Fix Pack) 7.0.0.21 of WebSphere Application Server V7.0 and Fix Pack 8.0.0.1 of WebSphere Application Server V8.0. Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PM40705
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-06-02
Closed date
2011-06-30
Last modified date
2012-02-03
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
R700 PSY UK74996
UP12/01/18 P 1201
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.
Document Information
Modified date:
27 October 2021