A fix is available
APAR status
Closed as program error.
Error description
Abend 0C4 with reason 4 which means that the key of the storage that the program is trying to access is different than the key of the psw. The socket calls are being make from the IEFJFRQ installation exit routine. This exit is being called from code that is running in psw key one. The storage was obtained in the key of the TCB which was key 8. The storage was for the autodata area and when EZBSOH03 tried to write in to the storage, this cause the abend. VERIFICATION STEPS: from the dump look at the key of the storage, in this case register 0 points to the storage, and the key of the psw. The instruction that is failing is a move character long used to zero the autodata area. KEYWORDS: abend0C4 abend 0C4 ezbsoh03 key1 key8 k1 k8 sp0 subpool0 1DC x'1DC'
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of the Communications Server for * * OS/390 Releases 7, 8, & 10 IP and * * z/OS Version 1 Release 2 IP: macro API * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 in EZBSOH03 if the PSW key * * differs from the TCB storage key * **************************************************************** * RECOMMENDATION: * **************************************************************** The customer has an IEFJFRQ exit which gets executed in PSW key 1 and issues an EZASMI call. The EZASMI interface, EZBSOH03, is called and issues a STORAGE OBTAIN to allocate working storage. Because EZBSOH03 uses subpool 0 for this, the storage is allocated in the TCB storage key which is 8. EZBSOH03 program checks when it tries to initialize this storage since it is trying to modify key 8 storage while executing in PSW key 1. +-------------------------------------------------------------+ + Please check our Communications Server for OS/390 homepages + + for common networking tips and fixes. The URL for these + + homepages can be found in Informational APAR II11334. + +-------------------------------------------------------------+
Problem conclusion
EZBSOH03 has been amended to allocate its working storage in the correct key. In releases 7, 8, and 10 the macro API still will not support GETHOSTBYADDR and GETHOSTBYNAME calls that are issued in a PSW key that differs from the TCB key. The following documentation change will be made to reflect this: **************************************************************** * FUNCTION AFFECTED: Communications Server TCP/IP (PQ54658) * * macro API * **************************************************************** * DESCRIPTION : Documentation updates * **************************************************************** * TIMING : None * **************************************************************** OS/390 Communications Server IP API Guide Version 2 Releases 7, 8, and 10 Document Numbers SC31-8516-02, SC31-8516-03, and SC31-8516-04. Chapter 10: Using the Macro Application Interface (API) Make the following amendment to the descriptions of GETHOSTBYADDR (topic 3.3.8.8) and GETHOSTBYNAME (topic 3.3.8.9) as follows (the note regarding Amode considerations does not apply to release 7): The following requirements apply to this call: ______________________________________________________________ | Authorization: | Supervisor state or problem state, the | | | PSW key must match the key in which | | | the MVS application task was attached | |_____________________|________________________________________| | Dispatchable unit | Task | | mode: | | |_____________________|________________________________________| | Cross memory mode: | PASN = HASN | |_____________________|________________________________________| | Amode: | 31-bit or 24-bit | | | | | | Note: See "Addressability mode (Amode) | | | considerations" under | | | "Environmental Restrictions and | | | Programming Requirements" in | | | topic 3.4.1. | |_____________________|________________________________________| | ASC mode: | Primary address space control (ASC) | | | mode | |_____________________|________________________________________| | Interrupt status: | Enabled for interrupts | |_____________________|________________________________________| | Locks: | Unlocked | |_____________________|________________________________________| | Control parameters: | All parameters must be addressable by | | | the caller and in the primary address | | | space | |_____________________|________________________________________| * Cross Reference between External and Internal Names
Temporary fix
Comments
×**** PE02/02/25 FIX IN ERROR. SEE APAR PQ58140 FOR DESCRIPTION
APAR Information
APAR number
PQ54658
Reported component name
TCP/IP V3 MVS
Reported component ID
5655HAL00
Reported release
370
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2001-11-12
Closed date
2002-01-16
Last modified date
2002-03-08
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UQ61950 UQ61951 UQ61952 UQ61953
Modules/Macros
EZBSOH03
| SC31851604 | SC31851602 | SC31851603 |
Fix information
Fixed component name
TCP/IP V3 MVS
Fixed component ID
5655HAL00
Applicable component levels
R120 PSY UQ61950
UP02/02/13 P F202
R370 PSY UQ61951
UP02/02/13 P F202
R380 PSY UQ61952
UP02/02/13 P F202
R50A PSY UQ61953
UP02/02/13 P F202
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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"370","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSCY4DZ","label":"DO NOT USE"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"370","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
08 March 2002