PK01604: WEBSPHERE ABEND0E0 FOR INVALID PROGRAM CALL | |||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||
APAR status Closed as fixed if next. Error description Running WebSphere V4 under z/OS 1.6 customer complains about multiple ABEND0E0-27 ABEND0E0 RC27 S0E0-27 S0E0 RC27 in CR. In our case the abends occurred in module BBOCLSCS +x'19C' and BBOCLSUR +x'46E' but there might be other modules as well. Program interruption code 0027 hex means : 'LSX-Translation Exception' An LSX-translation exception may be recognized only when the ASN-and-LX-reuse facility is installed and the ASN-and-LX-reuse control in control register 0 is one. An LSX-translation exception is recognized during PC-number translation in PROGRAM CALL when bit 0 of the linkage-second-table entry specified by the linkage-second-index part of the PC number is not zero. z/OS 1.6 provides a LX reuse facility which is described in the z/OS V1R6.0 MVS Extended Addressibility Guide: The LX reuse facility is available with z/OS V1R6 to provide additional LXs and improve reusability of LXs. It is enabled when running on a z890 or z990 processor at driver level 55 or above, with APAR OA07708 installed. Investigation of the provided dump showed that the CR we were trying to PC has ended previously. So the PC number we were using (which we got from an WebSphere internal table) was not valid anymore. Hence the abend was validly issued. It seems that these ABEND0E0 with RC 26, 27 and 2E are similar to the ABEND0D6 with RC 00, 22 and 23 we know from the past. With z/OS 1.6 and 'ASN /LX resuse enabled' these PROGRAM CALL abends show up as S0E0 with above mentioned return codes. Development will ship code in the next version, both V5 and V5.1, to recognize the 0E0 abend with a reason code of 26, 27, or 2E, and treat it as we are treating a 0D6 abend currently (what means cleanup the table, suppress the dump and retry). In the meantime, these messages are not harmful and can be ignored.Local fix These messages can be ignored in z/OS 1.6 as they are not harmful: ABEND0E0-27 ABEND0E0 RC27 S0E0-27 S0E0 RC27Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * version 4.0.1 for z/OS and OS/390 * **************************************************************** * PROBLEM DESCRIPTION: ABEND0E0/ABENDS0E0 REASON=00000026, * * REASON=00000027, or REASON=0000002E in * * a WebSphere Application Server V4.0.1 * * for z/OS control or server region. * **************************************************************** * RECOMMENDATION: * **************************************************************** An Application Server running under z/OS V1R6.0 with the LX reuse facility enabled may encounter ABEND0E0's when the target address space of a Program Call (PC) has terminated. This is occurring in the normal termination of a target address space and the subsequent attempt to PC to it. The current recovery code produces a dump and then recovers. The dumps taken for this scenario are undesirable.Problem conclusion Temporary fix Comments This APAR is being closed FIN with concurrence from the submitting customer. A solution to this problem will be delivered in a WebSphere Application Server for z/OS release within the next 18 months.
APAR is sysrouted FROM one or more of the following: PK01478 APAR is sysrouted TO one or more of the following: Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 401
Software edition:
Reference #: PK01604
IBM Group: Software Group
Modified date: May 10, 2005
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.