A fix is available
APAR status
Closed as program error.
Error description
Customer's system is running on zOS 2.5 on level OA64882 - HZFS450. Customer is experiencing Terminating exception causing 0C4 PIC38, during ZFSCREAT routine. At the time of the 0C4 the trace back: DSA (F4SA) at address: 50912E1FD8 DSA (F4SA) at address: 50912E19D0 Routine at addr 26279050 name: epiv_CreateAnode Routine at addr 26753C18 name: epif_CreateOE Routine at addr 26056808 name: efsvn_file_create Routine at addr 26650C80 name: efsvn2_create Routine at addr 26062330 name: efsvn_create Routine at addr 259AB7A0 name: ZFSCREAT Routine at addr 25735860 name: CNCREAT The routine epiv_CreateAnode was called with bad handle pointer, where efsvn2_create ended up passing garbage to efsvn_file_create. At the time of the 0C4, register 8(R8) had a bad handle pointer. (007 .404639) General Registers 08: 00E01057_A0250E19 00000000_00000000 00E01057_A0250E19 00000050_912E22F8 Register 8 had a bad value because the filesystem was corrupted, which was the reason for triggering the ABEND0C4 PIC38.
Local fix
Run the salvager utility with "-verifyonly" option to make sure that filesystem is not corrupted.
Problem summary
**************************************************************** * USERS AFFECTED: z/OS File System (zFS) 2.5 * * zFS FMID:HZFS450 * * * * z/OS File System (zFS) 3.1 * * zFS FMID:HZFS510 * **************************************************************** * PROBLEM DESCRIPTION: zFS encountered a terminating ABEND0C4 * * exception while processing an anode * * create request during a ZFSCREAT * * function call. * * * * Additional symptoms/information: * * * * epiv_CreateAnode ABEND0C4 PIC x'38' * * * * * **************************************************************** * RECOMMENDATION: APPLY PTF * **************************************************************** The routine epiv_CreateAnode was called with a bad handle pointer that caused the abend to be taken. It was determined that the abend was potentially the result of a corrupted ZFS file system.
Problem conclusion
Code has been added to detect the reported condition to avoid the terminating ABEND0C4. As the source of the potential corruption has not been determined, a diagnostic dump will be collected for future analysis. The ZFS aggregate may also be marked disabled to prevent further disruptions.
Temporary fix
Comments
APAR Information
APAR number
OA67277
Reported component name
ZFS ZSERIES FIL
Reported component ID
5696EFS00
Reported release
450
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2024-11-28
Closed date
2025-03-07
Last modified date
2025-04-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UJ96772 UJ96773
Modules/Macros
IOEAGFMT IOEAGSLV IOEDUMPF IOEFSCM IOEFSKN IOEFSTHD IOEFSUTL IOEZADM
Fix information
Fixed component name
ZFS ZSERIES FIL
Fixed component ID
5696EFS00
Applicable component levels
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":"BU011","label":"Systems - zSystems software"},"Product":{"code":"SG19O"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"450"}]
Document Information
Modified date:
02 April 2025