ANTX8117I

Explanation
The data mover for session session_id has
detected a delay in mainline data mover processing. The source of
the delay is indicated by the specified function.
The functions are described below:Note: The indicated function can
not necessarily be the only source of the delay, but it is likely
the cause of most of the delay.
PRIMARY(ssid:scid)
The indicated XRC session detected a delay while reading updates
from the primary storage controls. If XRC was able to identify the
storage control (ssid) and storage control session
number (scid) that caused the delay, it will also
report them on this message.
JOURNAL
The indicated XRC session detected a delay while processing XRC
journal records for updates made to primary volumes in the session.
SECONDARY(volser)
The indicated XRC session detected a delay while writing to secondary
volumes for updates made to primary volumes in the sessions. If XRC
is able to identify the XRC secondary volume serial number (volser)
that is causing the delay, the volume serial number will be reported
on this message.
MASTER(msession_id:lsession_id)
The indicated XRC session detected a delay in processing coupled
sessions associated with the indicated master session name (msession_id).
If XRC was able to identify the logical session that caused the delay,
it reports the logical session name (lsession_id)
on this message.
BUFFERS
The indicated XRC session detected a delay because of insufficient
availability of data mover buffers. Typically, this condition will
be associated with transient delays in other areas (Journal, Master,
or Secondary). Configuration of additional memory buffers can provide
relief from such delays.

The delay for the session is indicated by delay
time delay_time, given in hours, minutes, seconds,
and hundredths of seconds (hh:mm:ss.hh).
A delay_time value
of '***********' indicates that session delay could not be determined,
due to the inability to obtain information about a storage control
session. This is typically reported as a delay at PRIMARY, along with
an SSID and storage control session ID. It may be associated with
the abnormal termination of a storage control session, or with the
loss of connectivity to the primary storage subsystem.
More commonly, the '***********' value will
be associated with an I/O timeout that occurred while querying
an active storage control session. If such I/O timeouts persist, it
may indicate a problem with the channels or network that connects
the data mover to the primary storage subsystem. If,
however, you determine that the timeouts are normal for your
environment, you may consider increasing the
timeout value. See the description of the IOTIMING MiscLow parameter
in z/OS DFSMS Advanced Copy Services.
This
message can indicate a temporary peak in application activity on the
primary storage control, possibly as a result of volume synchronization
or resynchronization activity on that storage control. This message
can be repeated periodically until the condition is relieved, as indicated
by the ANTX8118I message.

System action
XRC functions are active.

System programmer response
This message reports a condition,
but does not indicate an error. If the delay condition continues for
a long period of time, the application can be impacted if primary
storage control cache capability is exceeded. When this message states
that the primary rate exceeds the specified function, ensure that
the DASD fast write option is on for the volumes associated with the
function. If volume synchronization or resynchronization activity
is present on any primary storage control, you can want to issue an
XSUSPEND command to suspend the volume pairs that are being added
until the application update rate on the primary storage controls
has returned to normal.

Source
Extended remote copy (XRC).