IOEZ00337E zFS kernel: non-terminating exception 2C3 occurred, reason EA2F0385

The abend reason of EAxx0385 indicates that the dump was requested by zFS from another sysplex member. If zFS does not automatically request a dump from the other sysplex members, you should enter the MODIFY ZFS,DUMP command on these other systems.

zFS also sends the trace to the trace output data set when a zFS dump occurs. Note that when a zFS abend occurs, other application failures might occur. For problem determination, these failures are not as important as the original zFS failure and dump.

Typically, zFS does not stop as a result of a zFS failure. An aggregate might become disabled (see Diagnosing disabled aggregates). If zFS does stop, zFS attempts to perform an internal restart after the terminating exception occurs. If the internal restart is unsuccessful, zFS attempts a stop and restart sequence. If the restart is successful, you might need to remount any zFS file systems. You might need to remount zFS file systems. The SETOMVS command can be used to remount file systems that were mounted from a BPXPRMxx parmlib member statement.

If a failure of a zFS operation occurs (other than a user error), but zFS does not dump, you should get a trace of the failure, if possible. Perform the steps outlined in Steps for tracing on zFS.

You can also obtain a dump of the zFS address space by entering the MODIFY ZFS,DUMP command. The dump should contain the zFS trace table. You must ensure the dump is complete. Partial dumps are of little use.

Alternatively, you can enter the MODIFY ZFS,ABORT command to cause zFS to send the trace to the trace output data set and to perform a dump. This also causes zFS to attempt an internal restart.