9C4

Explanation
An abend has been issued by the system data mover
(SDM) function.
Register 15 contains one of the following reason
codes. You may also receive message ANTX5000E, ANTX5001E, or ANTX5002E
with this abend. These messages can contain information that is related
to this abend code. Code
Explanation
4
The ANTMAIN address space has restarted due to an operator-initiated
CANCEL command, or due to an error condition that ended the session.
The session can be a concurrent copy, FlashCopy®, XRC, or PPRC session.  Any program
that attempts to access the ANTMAIN address space is ended with this
abend condition. Check the results of the ended jobs to determine
if data movement was successful before the jobs ended. Resubmit the
job if data movement was unsuccessful.
8-100
The XRC function has detected an error that requires an abend
dump to isolate the cause. The reason codes contain specific diagnostic
information to help isolate the specific error condition. In all cases,
data on the secondary volumes is preserved at a known consistent state
as reported by XRC messages.  A dump is generated only if the XRCTRAP
function is ON. The following are some of the more common reason
codes for configuration ration-type errors that can produce 9C4 abend
dumps: 10
A record from the storage control cannot be found.
2C
An invalid track format error has occurred when writing to a secondary
volume.
30
34
The data mover has not read from the storage control for at least
the timeout interval specified. The storage control session has been
canceled; all XRC volume pairs associated with this storage control
must be reinitialized.
38
A storage control logic error has occurred.
54
A nonstandard Record 0 has been detected on the primary volume.

 The reason codes indicate why the abend
was generated. In every case, data on the secondary volumes is left
in a consistent, recoverable state. The following are some of the
reasons why a 9C4 can occur: A volume has been initialized using an XADDPAIR command with NOCOPY
specified, but the volume contents were not identical.
The secondary volume has been updated by a function other than
the data mover. The secondary volume must be dedicated to the data
mover for all update operations. Other functions may read the volume,
but only the data mover can make updates.
Multiple data movers are updating the secondary volume. It is
possible that more than one data mover is copying data to the same
secondary volume. Only one data mover may have ownership of a secondary
volume.
I/O has stopped in a subsystem. I/O may not be active on a primary
storage control, secondary volumes, or journal volumes. Activity may
be stopped because the subsystem is not accepting I/Os or because
of a line failure in a channel extended environment.
A session has been restarted after maintenance has been applied
to the data mover system. If incompatibilities exist in the journal,
state, or control data sets, a 9C4 abend with reason codes 10 or 2C
may result. Ensure that the data sets have been properly allocated
before starting or restarting the data mover.

200-250
The system data mover (SDM) detected an error in a function necessary
to enable XRC to protect against dynamic I/O configurations.  Because
of this error, SDM is unable to protect against dynamic deletes of
XRC primaries, secondaries, and swaps devices.  Accompanying message
ANTX8061E message indicates the reason for this abend code.  If the
reason associated with ANTX8061E is not sufficient to identify and
resolve the problem, search problem reporting databases for a fix
for the problem. If no fix exists, contact the IBM® Support Center.

System action
The system abnormally ends the task that encountered
the abend condition.

System programmer response
Register 15 contains the nonzero return
code that describes the reason the abend was issued. The abend error
may be the result of a hardware- or software-detected error. Search
problem reporting data bases for a solution. If no solution exists,
contact the IBM Support Center.
Provide the console log, the dump data set, and the LOGREC data set
error record.
The data mover issues the 9C4 abend to freeze
the environment for problem diagnosis, and to ensure that the error
does not result in data integrity errors.
In most cases, XRC
suspends one or more volume pairs as a result of the error and the
error level specified. You can usually issue an XADDPAIR command to
return the volume pairs to the session, and then resynchronize them.
In some cases, you may need to issue the MODIFY ANTAS001,RESTART command,
followed by XADDPAIR commands, to rebuild the failed  data mover sessions.

Source
System data mover (ANT).