General Recovery Actions

For all return codes, if the problem persists after you have taken the actions indicated in the related message and the actions described in Table 1, then:

Search the problem reporting databases for a solution to the problem.
Contact the IBM® Support Center if you are unable to find a documented solution.
Provide the system log and a supervisor call (SVC) dump of both the ANTAS000 and ANTAS001 address spaces, if possible.

Some return code descriptions include a request that you dump additional address spaces, provide a GTF trace, or provide other information to assist the support personnel. The following is an example of all of the responses you will need to dump the local, as well as two other systems:

DUMP COMM=(DUMP LOCAL AND 2 OTHER SYSTEMS)
R n1,JOBNAME=(ANTAS*),DSPNAME=('ANTAS*'.SYSANT*),CONT
R n2,SDATA=(ALLNUC,PSA,SQA,CSA,LPA,TRT,SUM,LSQA,RGN),CONT
R n3,PROBDESC=SYSDLOCL,CONT
R n4,REMOTE=(SYSLIST=(sysname2('ANTAS*'),sysname3('ANTAS*')),DSPNAME
DATA),END

On internal errors, the SDM records critical information regarding the error in SYS1.LOGREC. If XRCTRAP is set to ON, the SDM also dumps the failing address space to the SYS1.DUMP data set. The dump, LOGREC, SYSLOG, and any other requested information listed in the description of the return code is sufficient to document a failure that results from an internal error. For codes indicating an internal error, search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM Support Center.

This topic does not document the reason codes for internal error return codes. In most cases the reason code is returned to the SDM by another system component, and has meaning only in the context of how the data mover uses that component.

Some return codes can be due to processing errors in the data mover internals. For many of these errors, one or more volume pairs can have been suspended by the data mover. If XRC pairs are suspended, for example, you can be able to capture the diagnostic result, and then issue an XADDPAIR command to return the affected volume pairs to the XRC session with minimal system impact. If the volume pairs are not suspended, issue an XSUSPEND command for the affected pairs followed by an XADDPAIR command to resynchronize the pair and bypass the error condition. In some cases you might need to issue a MODIFY ANT0001,RESTART command to force the data mover to save the software bitmaps and restart the session.

If any XRC volume pairs continue to cause a problem, you can issue an XDELPAIR command for those pairs, followed by an XADDPAIR command to reinitialize them into the session. If these actions fail to bypass the error, it can be necessary to shut down the session with an XEND command or CANCEL ANTAS001 command, and then reinitialize the session with an XSTART command. All volume pairs would then require a full resynchronization copy with the restart.