The XRC journal data sets are full. Processing of additional primary updates cannot occur until journal space is released. This condition can occur as a result of peak load processing.
Primary updates are not journaled until the full journal condition is relieved and message ANTX8033I is received.
This message means that updates to secondary volumes have fallen behind updates to primary volumes. If ERRORLEVEL(SESSION) is specified, all XRC volume pairs can have become suspended from the session. If ERRORLEVEL(VOLUME) or ERRORLEVEL(group_name) is specified, one or more sets of volumes can have become suspended.
This error can be due to a configuration problem where secondary processing cannot keep up with primary processing. In this case, verify that the journal data sets are large enough. If necessary, increase the size of the existing journal data sets, make them striped, or allocate more journal data sets. Ensure that secondary volumes are properly configured to minimize channel path and device contention, and are attached to storage controls with fast write active.
See z/OS DFSMS Advanced Copy Services for additional details. If all configuration conditions appear to be correct, search problem reporting data bases for a solution for the problem. If no solution exists, contact the IBM® Support Center. Provide the system log and SVC dumps of the ANTAS000 and any ANTASnnn address spaces that are active. To determine which address spaces are active, enter the console command DISPLAY A,ANTAS*.
Extended remote copy (XRC).