Explanation
The XRC session identified by session_id has
stopped moving data, for the reason indicated.
- Reason
- Description
- 1
- Data mover is waiting for currently allocated buffers to become
available, and wait limit has been exceeded.
- 2
- Data mover is waiting for newly allocated buffers to become available,
and wait limit has been exceeded.
System action
The XRC data mover address space is dumped, and
then cancelled. An additional dump might also be produced with title
COMPON=VSM,COMPID=SC1CH,ISSUER= IGVGVRGN,
ABEND=C78.
System programmer response
Look into SYSLOG for preceding ANTX8117I
messages to determine the source of delay.
- If delay is detected at journal or secondary data set, look for
problems with the secondary disk subsystem. Delay at journal might
also be a symptom of journal data sets being allocated with an insufficient
number of cylinders.
- If delay is detected at buffers, the cause might be that ReaderPacingWindow,
ReadPacingLimit, and MaxTracksRead parmlib values are too high relative
to the TotalBuffers value and the number of readers in the session.
- If the root cause of the delay is not apparent, search problem
reporting databases for a fix for the problem. If no fix exists, contact
the IBM® Support Center. Provide
the SYSLOG and ISSUER=ANTXBEAR SVC dump.
Following this error, you can restart the XRC session and add
suspended volumes again according to normal operating procedures.
Source
Extended remote copy (XRC).