0F4

Explanation
An error was detected by some system components. The ABEND reason code (in register 15) is the
service return code. The service reason code is in register 0 and its first byte can be used to aid
in identifying the reporting component:.
X'04' - IGWSPZAP
X'71' - CICS® VR Logger
X'77' - CICS VR Logger
X'83' - Program Management Binder
In most other cases, DFSMSdfp is the
source

System action
Most commonly, recovery routines retry to allow the failing module to return to its caller. If
DFSMS or CICS VR Logger issued the abend, an SVC dump will usually have been taken. A failure in the
binder will ordinarily produce an extensive snap dump if an IEWDUMP DD has been allocated. Failure
information for IGWSPZAP can be captured through one of the following:
SYSUDUMP
SYSABEND
SYSMDUMP

System programmer response
See the problem determination information for this abend. In some cases a SLIP trap on 0F4 may
catch a situation from which the system will be able to recover completely. The SLIP 0F4 should be
ignored in these cases if there are no other symptoms of a
problem.

Programmer response
System error. Rerun the job providing any diagnostic DD indicated earlier under System
Action.

Problem determination
If the error recurs and the program is not in error, look for a logrec record related to this
abend. In the logrec record, look for the abend return and reason codes. See
z/OS DFSMSdfp Diagnosis for a description of the return and
reason codes. If none found, search problem reporting data bases for a fix for the problem. If no
fix exists, contact the IBM® Support Center. Provide the JCL,
the SYSOUT output for the job, and the logrec data set error record.

Source
DFSMSdfp, Binder, SPZAP, VSAM
RLS, TVS, or CICS VR Logger

Module
Many modules.