Fixes are available
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.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
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.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
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
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
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
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
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
When WebSphere's FRR routine BBORFRR got control during handling of an abend, it SDUMPX macro to take a dump. However, this resulted in ABEND S233 RC=10 and the original dump was never taken. ABEND S233-10 means that caller passed incorrect parameters in a request for an SVC dump. Systrace shows: *RCVY FRR 070C0000 A2DD01E8 84052000 >> orignal abend S052 ... *SVCE D 00000000_0139288C 00000010 A2DD0564 8423300 >> ABEND S233-10 PSW @ A2DD01E8 from FRR: ...\....BBORFRR 11/05/10 BBORFRR 18.27 H28K510 BOSS FRR Routine .BFRRPRIM . .\...<......h....2i0..x....3.. In this case, SUMLIST(StoreList(1)) was bad. SUMLP in SDUMP_PL control block is the pointer to the caller's summary list: SUMLP.... 0000236C This showed that a high bit was on in the first starting address. This bit should never bit on. 0000236C A69766C0 | wp.{ |
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V6.1.0 and V8.0. * **************************************************************** * PROBLEM DESCRIPTION: WebSphere Application Server for z/OS * * BBORFRR routine encounters an * * ABEND233/ABENDS233 reason code 10 * * when a bad address is placed in the * * SUMLIST passed to SDUMP. * **************************************************************** * RECOMMENDATION: * **************************************************************** Since the bgvt address is the last parameter on the calls to connect and disconnect RRS to Websphere, it gets its high order bit turned on. If the SRB connecting or disconnecting to RRS takes an abend, the FRR, BBORFRR, gets control and invokes SDUMP with the BGVT address in SUMLIST. SDUMP issues an abend 233 reason code 10 because the bgvt address has its high order bit on.
Problem conclusion
The code has been changed to turn off the high order bit of the BGVT address when adding it to the SDUMP SUMLIST. APAR PM63264 is currently targeted for inclusion in Service Level (Fix Pack) 6.1.0.45 of WebSphere Application Server V6.1 and Fix Pack 8.0.0.4 of WebSphere Application Server V8.0. The fix will also be delivered as sysrouted APAR PM63265 in WebSphere Application Server V7.0 for z/OS Fix Pack 7.0.0.25. Please refer to URL: //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970 for Fix Pack availability. //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970 for Fix Pack availability.
Temporary fix
Comments
APAR Information
APAR number
PM63264
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
2012-04-25
Closed date
2012-05-01
Last modified date
2012-10-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
R610 PSY UK81646
UP12/09/23 P F209
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:
28 October 2021