Return Code | Description and Suggested Recovery Action |
---|---|
40 (X'28') | An error has been detected by pause/release processing, in ANTUPET, IEAVPSE, or IEVRLS. The reason code is in the format ssssrrrr, where ssss is the return code, and rrrr is the reason code from the service. |
44 (X'2C') | IEAVPSE returned a nonzero release code, but
no error was indicated in the SERVL return code. The reason code contains
one of the following release code values:
|
100, 101 | These are internal errors. |
102 | This can be an installation error where SVM has not been properly installed on the system. Verify the SVM installation. If it has been properly installed, then this is an internal error. |
103 | This is an internal error. |
104 | The limit on the number of data spaces that can be created has been reached. You might need to increase this limit. If increasing the limit has no effect, then this is an internal error. |
105 to 201 | These are internal errors. |
202 | An internal error occurred that affected inter-module communication. This might be a result of preceding errors, such as the inability to obtain virtual storage. |
203 | The amount of available
virtual storage in the XRC System Data Mover address space (ANTAS00n)
is insufficient. Possible reasons for this condition are:
See z/OS DFSMS Advanced Copy Services for the requirements for a description of the virtual storage requirements of an XRC System Data Mover address space. If the system configuration changes are needed, issue an XSUSPEND command with the TIMEOUT parameter to terminate the data mover address space. After the changes are made, restart the session and resynchronize the volume pairs. |
204, 205 | These are internal errors. |
206 | This can be an installation error where SVM has not been properly installed on the system. Verify the SVM installation. If it has been properly installed, then this is an internal error. |
207 | This is an internal error. |
208 | This can be an installation error where SVM has not been properly installed on the system. Verify the SVM installation. If it has been properly installed, then this is an internal error. |
209 to 246 | These are internal errors. |
247 to 250 | During XADDPAIR processing, storage could not be allocated for the initial volume copy or resynchronization. If new volumes are being added to a session which has been active for some time, shut down the session with XSUSPEND TIMEOUT and restart it with XSTART, and reissue the failed XADDPAIR. If the problem persists or the error is received on the XADDPAIRs immediately following a XSTART, then refer to the description of return code 203 for additional information. |
251 to 349 | These are internal errors. |
350 | The vary offline function did not complete within the expected time frame for the secondary volume of an XRC pair. Reissue the XADDPAIR command for the volume pair indicated. |
351 | Error occurred while you are attempting to vary volume offline. The reason code associated with this return code is generated by IEEVARYD. |
352 | An XADDPAIR for a non-xrcutl volume was attempted and REQUIREUTILITY(YES) is specified in the XRC parmlib, but an active storage control session did not exist for the specified (or default) scsession. Reason codes that accompany this return code are for IBM® diagnostic use. To correct this error, issue an XADDPAIR command to an XRCUTL volume for the specified (or default) scsession. When successful, reissue XADDPAIR for the non-xrcutl volume. |
353 | XADDPAIR for a suspended volume cannot proceed because of the existence of unprocessed updates that occurred before the volume suspension. The system data mover waited for processing to proceed, but did not detect progress for 15 seconds. Wait until session delay is relieved before resubmitting the XADDPAIR command. |
354 to 413 | These are internal errors. |
414 | This error means that you are attempting to start, restart, or recover an XRC session but the MVS™ image already has the maximum number of XRC sessions that are allowed. Issue an XQUERY command with the session ID of ALL to determine which session (if any) is currently active. You can either suspend or end the active session before you start or recover a session. If the XQUERY report shows that there are no active sessions and this problem persists, it is an internal error. Cancel the ANTASnnn address space to clear the error condition.This return code can also be received with an ANTS5100E message from an internal XSTART command that was issued as part of the ANTASnnn,RESTART command. The ANTASnnn address space had not had time to completely end. In addition, if you ended or suspended a session, you can not have given the address space the time necessary to completely end or suspend the session before issuing the XRECOVER or XADVANCE command. In this case, reissue the command. |
415 | The session name specified
is not an active XRC session. Issue an XQUERY command with session_id ALL
to determine which session (if any) is currently active. This return code can result when the XQUERY command is issued with session_id ALL if an active session is in the process of suspension or ending. Wait until the session has completed suspension processing or has ended before reentering the XQUERY command. If the session does not end, you might need to issue a CANCEL ANTASnnn command to force the address space to end. |
416 | The specified session ID is currently active in an XRC session. If this return code appears with message ANTS5100E, the session ID specified in the XSTART command is already active or address space termination for the session has not completed. When the address space no longer exists, reissue the XSTART command. If the return code appears with message ANTR5102E, an XEND or XSUSPEND command must be issued before the XRECOVER command can be processed. |
417 | This is an internal error. |
418 | The volume specified
in an XADDPAIR or XDELPAIR command, or a volume required by the XRECOVER,
XADVANCE, XSTART, or REFRESHS command is not found. For an XADDPAIR or XDELPAIR command, ensure that the volume has been specified properly. For an initial XADDPAIR or an XADDPAIR of a utility volume, ensure that the volume is online to the data mover system. After correcting the problem, reissue the XADDPAIR or XDELPAIR command. For an XRECOVER or XADVANCE command, ensure that the volume is online to the data mover system. After correcting the problem, reissue the command. For an XSTART command (when restarting a session), ensure that the volume is in the data mover system configuration. The storage control report associated with the restarted XRC session indicates that the storage control session is in a quiesced or suspended state. Ensure that all volumes for the storage control are in the configuration, then issue an XADDPAIR command to add this volume and other volumes in the quiesced or suspended storage control into the XRC session. If you are unable to put the volume in the data mover system configuration, you must issue a MODIFY ANTAS000,TERMSESS command for the storage control session(s) to free up resources associated with this volume and other volumes on the storage control from an LPAR which has connectivity to that device. If you do this, ALL VOLUMES on the storage control will then require a full initialization. If you want to restore the session but do not want to resynchronize the volume pairs at this time, you can vary the volumes online, and then issue an XSUSPEND command to suspend the session followed by an XSTART command the restart the session. If the return code appears with message ANTR5102E, verify that the volume to be recovered is online to the recovery system before issuing the XRECOVER or XADVANCE command. When associated with the REFRESHS command error message ANTX8142E, this indicates that the secondary volser is not online to the SDM system. REFRESHS requires an online secondary volume to determine the location of the relocated volume. |
419 | The secondary volume of an XRC pair is currently in use. XRC requires exclusive use of the secondary volume. If the volume is allocated to another function, then XRC will not use the volume. Ensure that the secondary volume is available for XRC use (the volume is not allocated), and then reissue the XRC command. |
420 | The volume or volumes specified in the XADDPAIR command are not attached to storage controls with the proper level of the XRC Licensed Internal Code (LIC) installed. XRC primary volumes must be attached to storage controls that are XRC-capable and have the LIC installed to support XSUSPEND functions. |
421 | Device
characteristics are invalid or unexpected, or the volume is not in
the expected location. This error is due to one of the following
conditions:
See &ieag100t; for information on the DEVSERV command, which can be used with the QDASD and PATHS keywords to determine device characteristics and location. See z/OS DFSMS Advanced Copy Services for information on allowable XRC device configurations. |
422 | The volume specified
in an XADDPAIR command, an XDELPAIR command, in conjunction with an
XRECOVER command, or for a session restarted with an XSTART command
is not found. For an XADDPAIR or XDELPAIR command, ensure that the volume has been specified properly and that the volume is online to the data mover system. After correcting the problem, reissue the XADDPAIR or XDELPAIR command. For an XRECOVER command, ensure that the volume is online to the data mover system. After correcting the problem, reissue the command. For an XSTART command, ensure that the volume is online to the data mover system. The storage control report associated with the restarted session indicates that the storage control session is in a quiesced state. Ensure that all volumes for the storage control are placed online, then issue an XADDPAIR command to add this volume and other volumes in the quiesced storage control into the session. If you want the session to be restored but do not want to resynchronize the volumes at this time, you can issue an XSUSPEND command to suspend the session followed by an XSTART command to restart the session. The session will then monitor record updates. If you are unable to place the volume online to the data mover system, you must issue an MODIFY ANTAS000,TERMSESS command for the storage control session to free up resources associated with this volume and other volumes on the storage control. All volumes on the storage control will then require a full initialization. If the return code appears with message ANTR5102E, verify that the volume to be recovered is online to the recovery system before issuing the XRECOVER command |
423 | This is an internal error. |
424 | XRC is unable to allocate
one of the preallocated XRC state, control, or journal data sets.
This is probably an installation problem. There are three likely causes:
When contacting IBM for assistance, provide a list of the XRC state, control, and journal data set names that are cataloged on both the data mover and recovery systems, in addition to the data requested in the beginning of this section. |
425 | XRC is unable
to deallocate a data set, and the deallocation fails. When contacting IBM for assistance, provide a list of the SYS1.XCOPY or hlq.XCOPY data sets that are cataloged on both the data mover and recovery systems, in addition to the data requested in the beginning of this section. |
426 to 428 | These are internal errors. |
429 | The XSTART or XRECOVER
function is unable to allocate the preallocated hlq.XCOPY.session_id.CONTROL
data set. The default for hlq is SYS1. Ensure that
the hlq.XCOPY.session_id.CONTROL
data set is properly allocated and cataloged on the data mover and
recovery systems. The reason code associated with this return code is generated by the DYNALLOC facility. See the reason codes from the DYNALLOC topic of z/OS MVS Programming: Authorized Assembler Services Reference ALE-DYN for reason code information. When contacting IBM for assistance, provide a list and allocation attributes of the hlq.XCOPY data sets cataloged on both the data mover and recovery systems, in addition to the data requested in the beginning of this section. |
430 | The XRC XSTART or
XRECOVER function is unable to allocate the preallocated hlq.XCOPY.session_id.JRNL01
and hlq.XCOPY.session_id.JRNL02
data sets. The default for hlq is SYS1. Ensure
that the hlq.XCOPY.session_id.JRNL01
and hlq.XCOPY.session_id.JRNL02
data sets are properly allocated and cataloged on the data mover and
recovery systems. The reason code associated with this return code is generated by the DYNALLOC facility. Reason codes of one to 16 indicate which journal data set the allocation is failing on. For reason codes outside of this range, see the DYNALLOC topic of z/OS MVS Programming: Authorized Assembler Services Reference ALE-DYN for reason code information. When contacting IBM for assistance provide a list and allocation attributes of the hlq.XCOPY data sets cataloged on both the data mover and recovery systems, in addition to the data requested in the beginning of this section. |
431 | The XRC XSTART, XCOUPLE with PURGE option, XADVANCE,
or XRECOVER function is unable to allocate the preallocated hlq.XCOPY.session_id.STATE
data set. The default for hlq is SYS1. Ensure that
the hlq.XCOPY.session_id.STATE
data set is properly allocated and cataloged on both the data mover
and recovery systems. The reason code associated with this return code is generated by the DYNALLOC facility. See the reason codes from the DYNALLOC topic of z/OS MVS Programming: Authorized Assembler Services Reference ALE-DYN for reason code information. When you contact IBM for assistance, provide a list and allocation attributes of the hlq.XCOPY data sets cataloged on both the data mover and recovery systems, in addition to the data requested in the beginning of this section. |
432 | The volume is attached
to a storage control that is not XRC-capable. Ensure that the primary
volume is online, and attached to an XRC-capable storage control. When contacting IBM for assistance, provide a list and allocation attributes of the SYS1.XCOPY data sets cataloged on both the data mover and recovery systems, in addition to the data requested in the beginning of this section. You can issue a DEVSERV QDASD command to dump the UCB. |
433 | XRC was unable to
open one of the hlq.XCOPY state, control, or journal
data sets (up to a maximum of 16 journals). Ensure that the data sets
have been allocated with the proper attributes. See z/OS DFSMS Advanced Copy Services for
the data set attributes. When contacting IBM for assistance, provide a list and allocation attributes of the SYS1.XCOPY data sets cataloged on both the data mover and recovery systems, in addition to the data requested in the beginning of this section. |
434 | XRC is unable to close
one of the hlq.XCOPY state, control, or journal
data sets (up to a maximum of 16 journals). This should not affect
the success of the XEND or XSUSPEND function. You should be able to
restart the session again. When contacting IBM for assistance, provide a list and allocation attributes of the SYS1.XCOPY data sets cataloged on both the data mover and recovery systems, in addition to the data requested in the beginning of this section. This problem also requires a GTF trace to determine where the problem occurred during a close. |
435 | A failure has occurred
during XRC processing when one of the functions requested did not
complete in a reasonable timeframe. If the processor has been in a
stopped state, this can be an expected error. If this error occurs
while starting a session or restarting a suspended session, it can
be that the state, control, or journal data sets are unavailable to
the XSTART command. Possibly another processor has reserved the volumes
that these data sets reside on. Correct the condition so that the
XSTART function can proceed normally. If the condition cannot be immediately
corrected, you can issue an XEND command to end the session or an
XSUSPEND to return the session to a suspended state. After correcting
the condition, you can reissue the XSTART command to start or restart
the session. If the problem persists, issue MODIFY ANTASnnn,DUMP to collect diagnostic information. |
436 | A volume specified
with an XADDPAIR command has failed XRC validation for one of the
following reasons:
Issue an XQUERY command to determine what volumes are currently defined to the session. To change the status of a volume already in the session, issue an XDELPAIR command to remove the volume pair from the session, then reissue the XADDPAIR command to add the correct volumes. If an incorrect volume pair was specified with an XADDPAIR command, correct the error and reissue the command. |
437, 438 | These are internal errors. |
439 | During XRC processing
all journal data sets have been filled. No additional extent space
is available on the journal volumes. XRC suspends the session when
this condition occurs. The journal data sets are not large enough
to support the volume of XRC data being copied. This error requires
the XRC session to be suspended and restarted. The error might be
due to an insufficient number of journal data sets being allocated.
The minimum is 2 and the maximum is 16. You can wish to allocate more
journal data sets, or to make the existing ones striped data sets
that span up to 16 volumes. This condition can also occur when updates to the secondary volumes have fallen so far behind the primary system updates that the journals have been filled with unapplied data. In this case, the configuration of the XRC system can be such that the data mover cannot keep up with the primary updates. You might need to reconfigure the system or place fewer volumes under XRC control. You can suspend, reconfigure, and then restart the session. When contacting IBM for assistance, provide a dump of the journal, state, and control data sets, in addition to the data requested in the beginning of this section. |
440 | SMS was not active on the data mover system at the time an XSTART or XRECOVER command was issued. This might be due to a window condition when SMS was not active at the time the XRC command was issued. If this return code appears with message ANTS5100E, then ensure that SMS is made active before issuing the XSTART command. If the return code is present with message ANTR5102E, activate SMS before reissuing the XRECOVER command. |
441 | SMS is not installed on the XRC data mover system. Ensure that SMS is installed on the data mover system where the XRC commands are being issued before reissuing the XSTART or XRECOVER command. The command can have been issued on the wrong system. After verifying that SMS is installed on the proper system, reissue the command. |
442 | This is an internal error. |
443 | This error occurs when an XRC function attempts to communicate to the ANTAS000 address space. This can occur if the control address space, ANTAS000, is canceled and is not active at the time of the error. Ensure that the ANTAS000 address space is active, and then reissue the command. |
444 | This error occurs when an attempt is made to process an XRC request and the XRC session is not currently active or is in the process of ending. If the session does not end, the session cleanup phase can be stalled. In this case, issue MODIFY ANTASnnn,RESTART to force a dump and restart the data mover. You can then resynchronize the volumes into the session with XADDPAIR commands. |
445 | This error occurs when an XRC function attempts to communicate to the ANTASnnn address space. This can occur if the data mover address space (ANTASnnn) is canceled and is not active at the time of the error. |
446 | This is an internal error. |
447 | An XADDPAIR command was issued which specifies the same volume serial number for both the primary and secondary volumes. You cannot use XRC to copy a volume to itself. Reissue the XADDPAIR command specifying unique volumes for the primary and secondary volumes. |
448 | This is an internal error. |
449 | This error occurs when load module ANTSDMLL cannot be loaded. Verify that ANTSDMLL is installed in SYS1.LINKLIB. |
450, 451 | These are internal errors. |
452 | During XRECOVER command
processing, XRC has determined that one or more of the journal data
sets, which were available for the session on the data mover system,
are not available on the recovery system. Scan the SYSLOG output and
look for message IEF237I and locate the last journal data set allocated
to the XRECOVER function (message IGD103I for SMS journal data sets).
Verify that the missing data sets are cataloged on the recovery system
before reissuing the XRECOVER command. This condition can occur if
the recovery system is different from the data mover system, and if
the journal data sets that are cataloged on the data mover system
are not cataloged on the recovery system. Ensure that all journal
data sets are properly cataloged on both systems and that the correct
HLQ is specified, and then reissue the XRECOVER command. When contacting IBM for assistance, provide a report on the cataloged data sets on both the data mover system and the recovery system, in addition to the data requested in the beginning of this section. |
453 | This is an internal error. |
454 | This error occurs when a command is issued that specifies an inactive XRC session name. If there is an active XRC session, issue the XQUERY ALL command to determine the session name, then reissue the failing command using the active session name. |
455 | The XRECOVER or XADVANCE command
has completed processing for an XRC session that was started with
SESSIONTYPE(XRC). All XRECOVER or XADVANCE functions are
not complete because there were no members found in the XRC control
data set. This might be due to one of the following conditions:
If the members do not exist and the system log indicates that an XRC session was properly started with active updates on the volumes, then contact IBM for assistance. Provide a report on the cataloged data sets on both the data mover system and the recovery system, in addition to the data requested in the beginning of this section. |
456 | The XRECOVER or XADVANCE command failed because the state data set indicates that there are no active volumes in the session. Ensure that the state data set has SESSION1, STATE000, and STATE001 members. If none exist, this can indicate either that the wrong data set is cataloged on the recovery system, or that an incorrect HLQ is specified. The error can also occur if the XSTART or XADDPAIR commands have never been issued for the session. If the members do not exist and the system log indicates that an XRC session was properly started with active volumes, search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide a report on the cataloged data sets on both the data mover system and the recovery system, in addition to the data requested in the beginning of this section. |
457 | The XRECOVER or XADVANCE command failed because of an I/O error attempting to read the XRC control data set. This error occurs because of a hardware error. The hardware error should have had message ANTX5014E associated with it. XRC recovery cannot take place until the hardware error has been resolved. Data on the secondary volumes is accurate to the last reported timestamp. Additional updates can have been applied, but not reported. Data consistency across the secondary volumes cannot be ensured because of the error. Correct the hardware error and reissue the XRECOVER or XADVANCE command. If no I/O error is indicated then search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide a report on the cataloged data sets on both the data mover system and the recovery system and a copy of the control data set, in addition to the data requested in the beginning of this section. |
458 | The XRECOVER or XADVANCE command failed because of an I/O error attempting to read the XRC state data set. This error occurs because of a hardware error. The hardware error should have had message ANTX5014E associated with it. XRC recovery cannot take place until the hardware error has been resolved. Data on the secondary volumes is accurate to the last reported timestamp. Additional updates can have been applied, but not reported. Data consistency across the secondary volumes cannot be ensured because of the error. Correct the hardware error and reissue the XRECOVER or XADVANCE command. If no I/O error is indicated then search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide a report on the cataloged data sets on both the data mover system and the recovery system and a copy of the state data set, in addition to the data requested in the beginning of this section. |
459 | The XRECOVER or XADVANCE command failed because of the control data set being invalid. This error occurs when XRC can read the data set, but the data in the data set is invalid. This condition can occur if you have a control data set which follows the XRC naming conventions and has members, CONTROL0 and CONTROL1, but is not used by XRC.This error can occur if an XRECOVER or XADVANCE command is issued for a previous level data mover that was suspended or ended. Ensure that the data mover can recover the environment for which the XRECOVER or XADVANCE command was issued.If the data set is being properly used and the XRECOVER or XADVANCE command is being properly issued, search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide a report on the cataloged data sets on both the data mover system and the recovery system and a copy of the control data set, in addition to the data requested in the beginning of this section. |
460 | An XSTART, XRECOVER, or XADVANCE command failed because of the state data set being invalid. This error occurs when XRC can read the data set, but the data in the data set is invalid. This condition can occur if you have a state data set which follows the XRC naming conventions and has members, STATE0 and STATE1, but is not used by XRC. If the data set is properly being used then search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide a report on the cataloged data sets on both the data mover system and the recovery system and a copy of the state data set, in addition to the data requested in the beginning of this section. |
461 | During processing
of an XRECOVER or XADVANCE command, the recover function
has determined that the secondary volume cannot be found. This is
probably a configuration error. The secondary volume or volumes must
be online to the recovery system before issuing the XRECOVER or
XADVANCE. Ensure that all volumes to be recovered are online,
and then reissue the XRECOVER or XADVANCE command. If the TERTIARY parameter was specified on the XRECOVER command, message ANTR5028E might have been previously issued, indicating that an attempt was made to recover to a secondary volume that is the same device as the secondary in effect when XRC suspended or ended. If XRC abnormally ends during an XRECOVER command, some secondary volume serial numbers can have already been updated. In this case, the XRECOVER command cannot be reissued. Relabel the secondary volumes back to their original volume serial numbers before reissuing the XRECOVER command. |
462, 463 | An XDELPAIR command has been issued to remove one or more volumes from the session, but there are no volumes in the session. Issue the XQUERY command with the VOLUME(ALL) option to determine the status of volumes in the session. |
464 | The primary volume specified in an XADDPAIR command was determined to be invalid. Ensure that the primary volume is a valid volume that is online to the data mover system, and then reissue the command. |
465 | The secondary volume
specified in an XADDPAIR command was determined to be invalid. Ensure
that the secondary volume is a valid volume that is online to the
data mover system, and then reissue the command. If this error is associated with an XADDPAIR command for a suspended pair, use the XQUERY configuration report to determine the secondary volume that was specified when the pair was originally added to the session, then reissue the command. |
466, 467 | Either of these indicate
a probable I/O error that has occurred when XRC attempted to access
the journal, state, or control data sets. Return code 466 indicates
a read error, and return code 467 indicates a write error. Other messages
can also be present, including an associated ANTX5014E error message
providing hardware error diagnostics, and error messages from IOS
or data management. Correct the journal error, then suspend the session
and restart the data mover. When contacting IBM for assistance, provide a copy of the associated SYS1.LOGREC information and a GTF trace, in addition to the data requested in the beginning of this section. |
468, 469, 471 | These are internal errors. |
470, 472 | The session is in a state of being ended or suspended. If the session does not suspend or end, the session cleanup process can be stalled. In this case, issue the MODIFY ANTASnnn,DUMP command followed by the CANCEL ANTASnnn command after the dump has completed. It is likely that all volumes in the session will then require a reinitialization. |
473 to 479 | These are internal errors. |
480 | The specified volume
was not suspended by XRC. Possibly another error associated with a
list of volumes being processed has caused this error. To suspend
the volume, reissue the XSUSPEND command. If the volume cannot be
suspended, delete the volume pair from the session, then add it back
into the session. If this error has been received with a valid active session, issue MODIFY ANTASnnn,DUMP to obtain a dump of the failing session. A dump is required in addition to the data requested in the beginning of this section. |
481, 482 | These are internal errors. |
483 | An attempt has been
made to restart a session, but no storage control session exists on
the storage control associated with this data mover. The previously
existing session has been ended by the storage control. This might
be due to an expired timeout interval for the storage control. If
you want the volume pair to be part of the XRC session, reissue the
XADDPAIR command for the volume pair. A full-volume synchronization
is then required for the volume pair. If this error has been received with a valid active storage control session, issue MODIFY ANTASnnn,DUMP to obtain a dump of the failing condition. Issue MODIFY ANTASnnn,LISTSESS to obtain the storage control information on active sessions and MODIFY ANTASnnn,LISTDVCS to obtain the storage control information for active devices. This information is required in addition to the data requested in the beginning of this section. |
484, 485 | These are internal errors. Issue MODIFY ANTASnnn,DUMP to obtain a dump of the error. |
486, 487 | These return codes
can indicate that the requested command function is taking longer
than expected. Reissue the command. If this error occurs while starting
a session or restarting a suspended session, it can be that the state,
control, or journal data sets are unavailable to the XSTART command.
Possibly another processor has reserved the volumes that these data
sets reside on. Correct the condition so that the XSTART function
can proceed normally. If the condition cannot be immediately corrected,
you can issue an XEND command to end the session or an XSUSPEND to
return the session to a suspended state. After correcting the condition,
you can reissue the XSTART command to start or restart the session. If the problem persists, issue the F ANTASnnn,DUMP command to collect diagnostic information. |
488 | This is an internal error. |
489 | The XADDPAIR command function has determined that the primary volume listed in message ANTA5107E is currently in an active XRC session. Use the XQUERY command to determine which volumes are already part of an XRC session, then reissue the XADDPAIR command with the correct primary volume serial number or SCSESSION identifier. |
490 | The XADDPAIR command function has determined that the secondary volume listed in message ANTA5107E is currently in an active XRC session. Use the XQUERY command to determine which volumes are already part of an XRC session, then reissue the XADDPAIR command with the correct secondary volume serial number or SCSESSION identifier. |
491 | This is an internal error. |
492 | This error occurs if XRC encounters an error when it is writing to either the control or state data set. In most cases, the error occurs because the data set did not have sufficient space to contain XRC information. See z/OS DFSMS Advanced Copy Services to determine the proper allocation sizes for the XRC control and state data sets. If this error occurs, perform the following procedure:
When you contact IBM for assistance, provide a copy of the failing data set, in addition to the data requested at the beginning of this section. |
493 | This can mean that secondary updates are not being performed fast enough to keep pace with primary updates. Verify the configuration to ensure that you have not placed too many secondary volumes behind a single storage control. Verify that DASD fast write is enabled for the secondary volumes. |
494 to 497 | These are internal errors. |
498 | The request has failed
because the session is currently being ended or suspended. This error
can be the result of a previously issued XEND or XSUSPEND command.
See previous messages for an explanation of when the previous command
was issued. If the active command does not complete in a reasonable timeframe, you can issue MODIFY ANTASnnn,DUMP to capture the proper information for problem diagnosis. You might need to issue CANCEL ANTASnnn to force the address space to end. |
499 | This error occurs
if XRC is unable to add any more members to the state data set during
XSTART or XADDPAIR command processing. This error can also occur
while XRC attempts to add the coupling member to the state data set
when it processes an XCOUPLE ADD command. The state data set
must have directory space and data set space for a STATE000, STATE001,
SESSION01, COUPLE, and space for each primary volume serial
number in the XRC session. The primary volume serial number member
name is in the form Vxxxxxx where xxxxxx is the volume serial number
of a primary volume. If this error occurs, perform the following
procedure:
|
500 to 603 | These are internal errors. |
604 | This hardware-detected
error can occur for one of the following reasons:
If the message issued with this return code was accompanied by an ANTX5000E, ANTX5001E, or ANTX5002E message, see those messages for further information. When contacting IBM for assistance with a problem, provide any associated SYS1.LOGREC information, in addition to the data requested in the beginning of this section. A GTF trace of the operations leading to the error can also be required. |
605 | The maximum number of XRC sessions that are supported by a storage control has been reached. If you reissue the XADDPAIR command, this problem can not occur as volumes are deleted from other sessions. This error can occur if you attempt to start too many SCSESSIONS for a single storage control. If this error continues to occur, issue a LISTSESS command to determine which sessions are currently active on the storage control. Issue the TERMSESS command to end sessions that should not be active. If the error persists, see z/OS DFSMS Advanced Copy Services for information about identifying and restarting suspended sessions. When contacting IBM for assistance, a GTF trace of the operations leading to the error can also be required, in addition to the data requested at the beginning of this section. |
606 | This is a hardware I/O error from an attempt to read a track from the specified primary volume; it can indicate a cache error. See accompanying messages to determine the scope of the error. If the message issued with this return code was accompanied by an ANTX5000E, ANTX5001E, or ANTX5002E message, see those messages for further information. |
607 | This is a hardware I/O error from an attempt to read one or more updates from the primary storage control cache. It can indicate a cache error, a session ending, a storage control session timeout condition, or the loss of the path (or line) from the data mover to the storage control cache. See accompanying messages to determine the scope of the error. If the message issued with this return code was accompanied by an ANTX5000E, ANTX5001E, or ANTX5002E message, see those messages for further information. If a path to the storage control has been lost, the associated storage control session might need to be ended with the TERMSESS command, as the data mover is unable to cleanup the session. Issue the MODIFY LISTSESS command to determine if the storage control session is still active, then end it if necessary. |
608 | A hardware I/O error occurred while attempting to add the specified primary volume to the session. If the message issued with this return code was accompanied by an ANTX5000E, ANTX5001E or ANTX5002E message, it provides additional detail about the failure reason. If the failure reason indicates that an XRC session is already active for the device, check if the XADDPAIR command was issued a short time after an XDELPAIR command for the same volume pair. If so, the XADDPAIR command will likely succeed when reissued. Otherwise, issue a MODIFY ANTAS000,DVCDATA command for the device to determine which storage control session it is associated with. Then use XQUERY CONFIGURATION reports on active data movers to determine which session owns the volume pair and/or storage control session. If the volume pair and storage control session cannot be matched to a data mover, contact IBM support for assistance in performing the necessary cleanup. |
609 | A hardware I/O error has occurred while deleting the primary volume from the session. You can force the volume pair to end by issuing MODIFY ANTAS000,LISTDVCS to the volume to determine which storage control session owns the volume. If you do not want the storage control session to be active you can force the storage control session to free the volume for use by issuing MODIFY ANTAS000,TERMDVC to the session. If the message issued with this return code was accompanied by an ANTX5000E, ANTX5001E, or ANTX5002E message, see those messages for further information. |
610 | A hardware I/O error has occurred while ending the XRC session. You can force the storage control session to end by first issuing MODIFY ANTAS000,LISTDVCS to a volume in the session to determine the active storage control sessions for the device. Next issue MODIFY ANTAS000,TERMSESS to end the storage control session. If the message issued with this return code was accompanied by an ANTX5000E, ANTX5001E, or ANTX5002E message, see those messages for further information. |
611 to 614 | A hardware I/O error has occurred while writing data to a secondary volume. The volume pair is suspended. Using the sense information provided, correct the error and issue an XADDPAIR command to resynchronize the volume pair back into the XRC session. If the message issued with this return code was accompanied by an ANTX5000E, ANTX5001E, or ANTX5002E message, see those messages for further information. |
615 to 616 | An error has occurred in track synchronization processing. Issue an XDELPAIR command to remove the volume pair from the XRC session. You can issue an XADDPAIR command to add the volume pair back to the session. The volume pair will then require a full initialization. If the message issued with this return code was accompanied by an ANTX5000E, ANTX5001E, or ANTX5002E message, see those messages for further information. |
617 to 619 | These are internal errors. |
620 | A hardware I/O error has occurred while attempting to determine the device characteristics of the volume. Correct the error and add the volume pair back into the session. |
621 | An I/O error has occurred during I/O to the specified volume. If the error occurred on the primary volume, it is likely that the storage control session has ended. This might have been due to a cache or NVS error, a timeout expiration, or an operator-initiated TERMSESS command. If the error is on a write operation, the error might be due to a cache or NVS error. Correct the error and add the volume pair back into the session. If the message issued with this return code was accompanied by an ANTX5000E, ANTX5001E, or ANTX5002E message, see those messages for further information. |
622, 623 | These are internal
errors. When contacting IBM for assistance, also provide a copy of the SYS1.LOGREC data set, in addition to the data requested in the beginning of this section. |
624 | This is a hardware
I/O error. The XRC data mover function encountered an I/O error while
attempting to write the volume label on the secondary volume. Use
the sense information and SYS1.LOGREC records to determine the cause
of the error. Correct the error and restart the function that encountered
the error. If the message issued with this return code was accompanied
by an ANTX5000E, ANTX5001E, or ANTX5002E message, see those messages
for further information. When contacting IBM for assistance, a GTF trace of the operations leading to the error can also be required in addition to the data requested in the beginning of this section. |
625 | The maximum number
of XRC sessions that are supported by a storage control has been reached.
The session limit includes both concurrent copy and XRC sessions.
Issue the LISTSESS command to determine the number of active storage
control sessions for the storage control. See z/OS DFSMS Advanced Copy Services for
information about determining what sessions are active and restarting
suspended sessions. When contacting IBM for assistance, a GTF trace of the operations leading to the error can also be required in addition to the data requested in the beginning of this section. |
626 | The maximum number
of XRC sessions for a single volume has been reached. No volume can
have more than one active XRC session. This error can be caused when
an XADDPAIR command closely follows an XDELPAIR command, but the delete
operation is not yet complete. Reissue the XADDPAIR command. If the
error persists, issue the LISTDVCS command to determine the number
of storage control sessions. When contacting IBM for assistance, a GTF trace of the operations leading to the error can also be required in addition to the data requested in the beginning of this section. |
627 | The maximum number
of data mover sessions supported for a single volume has been reached.
The session limit includes both concurrent copy (CC) and XRC sessions.
3990 and 9390 Storage Controls allow up to 16 CC sessions, or 15 CC
and one XRC session, per volume. ESS storage subsystems allow up to
64 CC sessions, or 63 CC sessions and one XRC session, per volume.
Issue the LISTDVCS command to determine the number of storage control
sessions. When contacting IBM for assistance, a GTF trace of the operations leading to the error can also be required in addition to the data requested in the beginning of this section. |
628 | This is an internal error. |
629 | This error is due to a nonstandard record zero on the volume. XRC supports only volumes which have a standard record zero. Initialize the volume with standard record zero and add it to the XRC session. If this error occurs and the volume has standard record zero, then search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide a dump of the failing track and records in addition to the data requested in the beginning of this section. |
630 | An I/O error has occurred while attempting to read a track for a suspended volume during volume resynchronization. An IOS error message should accompany this error. Correct the error and issue an XADDPAIR command to return the volume pair to the session. The affected volumes will require a full-volume synchronization after and XADDPAIR command is issued. Processing continues for the rest of the volumes in the session if ERRORLEVEL(VOLUME) was specified for the volume pair. |
631 | This means a non-timestamped write was encountered during resynchronization processing. The volume pair is suspended. The condition can be corrected by issuing an XADDPAIR command for the volume pair. |
632 | This is an internal error. Issue MODIFY ANTASnnn,DUMP to obtain a dump of the error. |
633 | A list of volumes was given on the specified command. The error occurs when the same volume serial number is specified more than once in the list. Correct the error and respecify the command. A volume serial number can only be specified once in the list. |
634 | This error is issued
when a primary storage control session has been ended. The session
might have ended because of any of the following reasons:
Review other diagnostic messages to determine the cause of the problem. All volumes for the storage control are suspended as a result of this error. Based on the ERRORLEVEL specification, other volumes on other storage controls can also be suspended. After determining the reason for the error and correcting the condition, you can issue an XADDPAIR command to add the suspended volumes back to the session. The suspended volumes will require a full resynchronization. |
635 | An I/O error has occurred while attempting to read from a list of sessions that are on a storage control. This can be caused by an LIC error which generates the I/O error. Verify that the LIC level supports remote copy functions. If the message issued with this return code was accompanied by an ANTX5000E, ANTX5001E, or ANTX5002E message, see those messages for further information. If the error persists, obtain a GTF trace for the specified device. |
636 | An I/O error has occurred while attempting to read from a list of devices that are on a storage control. This can be caused by an LIC error which generates the I/O error. Verify that the LIC level supports remote copy functions. If the message issued with this return code was accompanied by an ANTX5000E, ANTX5001E, or ANTX5002E message, see those messages for further information. If the error persists, obtain a GTF trace for the specified device. |
637 | An I/O error has occurred while attempting to read control information from a storage control. Possibly, an LIC error has generated the I/O error. Verify that the LIC level supports remote copy functions. If the message issued with this return code was accompanied by an ANTX5000E, ANTX5001E, or ANTX5002E message, see those messages for further information. If the error persists, obtain a GTF trace for the specified device. |
638 | This is an LIC error. If you have previously issued an SCTRAP ON command, obtain the state save associated with the error and search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM Support Center for hardware-related assistance. |
639 to 643 | These are internal errors. |
644 | An I/O error has occurred during a read of the hardware bitmap. This might be due to an error in the cache or NVS. Correct the error and return the volume to the session. The volume pair will require a full resynchronization. If the message issued with this return code was accompanied by an ANTX5000E, ANTX5001E, or ANTX5002E message, see those messages for further information. |
645 | A device I/O error has occurred while determining device status. Reissue the failing command. If the message issued with this return code was accompanied by an ANTX5000E, ANTX5001E, or ANTX5002E message, see those messages for further information. If the error persists, search problem reporting databases for a fix for the problem. If no fix exists, obtain a GTF trace before contact the IBM Support Center. |
646 | An I/O error has occurred during a read of the hardware bitmap. The volume pair will require a full resynchronization. If the message issued with this return code was accompanied by an ANTX5000E, ANTX5001E, or ANTX5002E message, see those messages for further information. If the error persists, search problem reporting databases for a fix for the problem. If no fix exists, obtain a GTF trace before contact the IBM Support Center. |
647 | This
I/O error is issued when a primary storage control session has been
suspended. All volumes associated with the storage control session
are suspended. Based on the ERRORLEVEL specification, other volumes
can also be suspended. XRC has detected this error during normal data mover processing. The scope of the error is for a single storage control session. After you determine the reason for the error and correct the condition, you can issue an XADDPAIR command to add the suspended volumes back to the session. A reason code accompanies this return code, which gives more specific information as to the reason for the suspension. Additionally, other diagnostic messages might be issued. The following are the reason codes that are
indicated with this return code:
|
648, 649 | These are internal errors. If the message issued with this return code was accompanied by an ANTX5000E, ANTX5001E, or ANTX5002E message, see those messages for further information. |
650 | The volume originally being resynchronized is now being synchronized by a full-volume copy. If a full-volume synchronization is not indicated, issue MODIFY ANTASnnn,DUMP to obtain a dump of the error. |
651 | An I/O error occurred while attempting to read device-blocking status information from the primary storage control. Reference any ANT or IOS error messages associated with the I/O error and correct the problem. If the message issued with this return code was accompanied by an ANTX5000E, ANTX5001E, or ANTX5002E message, see those messages for further information. |
652 | An I/O error occurred attempting to access the master data set. If the message issued with return code 652 was accompanied by an ANTX5000E, ANTX5001E, or ANTX5002E message, see those messages for further information. |
653 | There are no paths available. |
654 to 674 | These are internal errors. If the message issued with return code 652 was accompanied by an ANTX5000E, ANTX5001E, or ANTX5002E message, see those messages for further information. |
661 | Internal error. |
675 | The system data mover has attempted to issue I/O to a device, but the I/O was not completed in the allotted time. If the accompanying reason code is 82, the timeout occurred after the I/O had been started. If the accompanying reason code is 83, the error occurred while the I/O was waiting to start. When reading updates from cache, or writing updates to a secondary volume, this return code is issued only when the data mover determines not to retry the condition. Retry will not be attempted if there is a command in progress (XDELPAIR, XSUSPEND, XEND), or if at least one storage control session is exceeding cache SIDEFILE limits. If the timeout occurs while writing updates to a secondary volume, the number of retry attempts is limited to four. If the timeout occurred while reading updates from cache in a channel extended primary storage control, check the network for connectivity problems. For other timeout events, check the storage subsystems for evidence of recovery actions that can have delayed I/O completion. The z/OS® DEVSERV command can be helpful with problem determination. When the underlying problem is corrected, issue an XADDPAIR command for all of the suspended volumes. |
676 | An error occurred during XRC volume
synchronization or resynchronization. The volume was suspended. XRC
was unable to write data to a secondary volume of an XRC volume pair.
The error occurred for a track on the primary volume which had been
updated before the initialization of the track on the associated secondary
volume. There are two reasons why XRC was unable to perform the
I/O request:
|
677 | The XRC session has detected that a storage control session has been in the long busy condition for 80% of the storage control timeout time. The XRC session will suspend all volumes associated with the storage control session to attempt to free up storage control cache to end the long busy condition. |
678 | The XRC session has determined
that a storage control session has been in the long busy condition
for the storage control timeout time. The storage control session
ends and all volumes associated with the storage control session are
suspended. This frees up the cache resource in the storage control
and ends the long busy condition. Note: If SILB
is enabled in software but not hardware, you will get this return
code instead of a return code 647 reason 17 or 18. Please ensure that
in the SL column of a XQUERY STORAGECONTROL FEATURES report that it
reads YY. If it reads NY or -Y, you will receive a return code of
678.
|
679 | The XRC has determined that a delay in the delivery of I/O to an active LOGPLUS volume is causing a problem in the formation of consistency groups in the active session. Subsequent messages indicate that the volumes were suspended because of this problem. Determine the reason why the I/O was not received by the LOGPLUS volume(s). Fix the problem and re-ADD the LOGPLUS volumes(s) to the XRC session. |
680 | The error is issued if mirror validation detects that the primary device associated with a duplex volume pair does not belong to an XRC storage control session. To return the volume to duplex, issue an XADDPAIR command. The data mover will automatically perform a full copy on the volume. Note that volumes encountering this error are not eligible to be processed by AUTO_READD. |
681 | An attempt is made to add a new LOGPLUS session to an LSS, but there are no available storage control session identifiers in the allowed range. Issue an F ANTAS000,LISTSESS command to the primary device number and look for identifiers in the range EA-FF. Terminate any unexpected sessions and issue the XADDPAIR command again. If there are no unexpected sessions, it is necessary to move the LOGPLUS volume to another LSS in order to mirror it with the XRC session. |
682 to 804 | These are internal errors. When contacting IBM for assistance, also provide a copy of the SYS1.LOGREC data set, in addition to the data requested in the beginning of this section. |
805, 806 | These are internal errors encountered when issuing an MVS attach order. When contacting IBM for assistance, also provide a copy of the ANTMAIN address space, in addition to the data requested in the beginning of this section. |
807 to 900 | These are internal errors. Cancel ANTAS000 and ANTASnnn and restart the XRC session. |
901 | This error is issued if the data mover detects either a No Record Found or Invalid Track Format error on a volume. The data mover will automatically reinitialize the track on which the error occurred. If a subsequent error occurs during resynchronization for the same volume, the volume pair will be suspended. |
902 | This error is issued if the data mover detects either a No Record Found or Invalid Track Format error on a volume. The data mover automatically reinitializes the track on which the error occurred. If a subsequent error occurs during resynchronization for the same volume, the volume pair is suspended. The error was detected on a volume that was added using the NOCOPY option of the XADDPAIR command. |
903 | Internal errors. Cancel ANTAS000 and ANTASnnn and restart the XRC session. |
904 | The error is issued if the data mover detects unexpected XRC device status in the primary storage subsystem for a duplex volume. If an automatic re-add function has been requested through AUTO_READD ON, the data mover will correct the error. |
905 to 1001 | These are internal errors. Cancel ANTAS000 and ANTASnnn and restart the XRC session. |
1002 to 1008 | These are internal errors. |
1009 | An I/O error has occurred during control functions to a volume. The error can be accompanied by an IOS error message or an ANTX5001E error message that provides sense information associated with the error, or an ANTX5002E error message. If this error has occurred when adding or re-adding a volume to the session, correct the error and issue an XADDPAIR command to return the volume to the session. If the error occurs during an XSUSPEND function, reissue the command. If the error persists, obtain a GTF trace for the failing device. When contacting IBM for assistance, provide the GTF and a copy of the associated SYSLOG and SYS1.LOGREC information. |
1010 | This is an internal error. |
1011 | An SSID has been specified that is unknown to XRC. Issue a LISTSESS command for a device on the storage subsystem to determine if there are any active XRC sessions. If not, correct the SSID and reissue the command. |
1012 | This is an internal error. |
1013 | The command is not accepted. There are no volumes in the session, so the requested function cannot be performed. |
1014 | This is an internal error. |
1015 | An I/O error has occurred while attempting to read from a primary storage control or a journal, control, or state data set. Related IOS messages contain the reason for the I/O error. Fix the error and reissue the command. |
1016 | This is an internal error. |
1017 | An XRC volume was not found. If the
return code was received as a result of issuing a command, the volume
serial number specified for the command can have been specified incorrectly.
The volume is not in the XRC session. In this case, reissue the command.
If this return code was issued with message ANTX5101E, the XDELPAIR
command can have been issued using the current volume serial number
of a relabeled volume. Reissue the XDELPAIR command with the initial
volume serial number of the relabeled volume. This error can occur for an ESS storage subsystem if the volume channel connection address is greater than 255, which is the maximum supported. In this case, ensure that the address is between 0 and 255. For a non-ESS storage subsystem, the channel connection address cannot be greater than 127. In this case, ensure that the address is between 0 and 127. If the volume serial number was specified correctly, issue a DEVSERV QDASD command for the failing volume and obtain the UCB information for the volume. Use the MODIFY command to dump the ANTASnnn address space, search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM Support Center. You might need to cancel ANTASnnn and restart the XRC session. The cancel will cleanup the XRC control structures and suspend all volume pairs. |
1018 | This error is issued when a primary
storage control session has been ended. The session can have ended
for any of the following reasons:
Review other diagnostic messages to determine the cause of the problem. The data mover suspends all volumes for the storage control as a result of this error. Based on the ERRORLEVEL specification, other volumes on other storage controls can also be suspended. After determining the reason for the error, you can issue an XADDPAIR command to add the suspended volumes back to the session. The suspended volumes will require a full resynchronization. |
1019 to 1026 | These are internal errors. |
1027 | XRC supports a maximum of 80 primary storage control sessions. You have attempted to add more than this limit. Reduce the number of SCSESSIONS used for this XRC session. If you require more than 80 primary storage control sessions, search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM Support Center. Issue an XDELPAIR command for all volumes behind one or more primary control sessions to reduce the total number of active sessions. |
1028 to 1031 | These are internal errors. |
1032 | This is an internal error. Issue MODIFY ANTAS001,DUMP to obtain a dump of the error. |
1033 | An XDELPAIR, XEND, or XSUSPEND command has been issued with the DRAIN or ATTIME keyword specified. The request is rejected. This error is issued if there are no active volumes in the session or if no updates have been made to any storage control in the session since an XSTART command last started or restarted the session. The data mover has no application system time reference to use to determine when the DRAIN or ATTIME should take effect. Issue an XQUERY command to verify the session status. You can reissue the XDELPAIR, XEND, or XSUSPEND command with the IMMEDIATE option to complete the function. |
1034 | An XDELPAIR command has been issued for a volume pair with the ATTIME or DRAIN keyword specified. The volume pair is currently suspended. If you wish to delete the volume pair, reissue the XDELPAIR command with the IMMEDIATE keyword. |
1035 | The maximum number of XRC sessions that are supported by the data mover has been reached. A single XRC session supports a maximum of 80 storage control sessions. Issue the XQUERY STORAGECONTROL command to see the number of active storage control sessions. Either end any unnecessary sessions or start another data mover to run additional XRC sessions. |
1036 to 1045 | These are internal errors. Cancel ANTASnnn and restart the XRC session. |
1046 to 1048 | There is an error with the STATEXnn member in the STATE dataset. |
1049 to 4000 | These are internal errors. Cancel ANTASnnn and restart the XRC session. |
4001 | The data contained in the state data set does not match the session name that is being recovered. Verify that the state data set is properly named and cataloged on the recovery system for the session that you are recovering. Cancel ANTAS000 and ANTASnnn and reissue the command. |
4002 | This is an internal error. Cancel ANTASnnn and reissue the command. |
4003, 4004 | During processing of an XRECOVER or XADVANCE command, XRC has determined that the timestamps for all groups are zero. This is a normal processing state. There is no unrecovered data, and all data is in a consistent state.If you believe that there is unrecovered data, provide a copy of the state, control, and journal data sets (and the master data set if you are running coupled XRC sessions) in addition to the data that was requested in the beginning of this section when you contact IBM for assistance. |
4005 | This is an internal error. Cancel ANTASnnn and reissue the command. |
4006 | This error can be due to an XADDPAIR command being issued to a non-ECKD volume. Determine if this command has been issued to a volume that does not support ECKD™ commands. |
4007, 4008 | These are internal errors. Cancel ANTASnnn and reissue the command. |
4009 | During XSTART, XRECOVER, or XADVANCE processing,
XRC has determined that the state data set cannot be opened. If this
return code appears with message ANTS5100E, verify that the XSTART
command specified the proper high-level qualifier (HLQ) for the state
data set. Verify that the HLQ state data set is defined and cataloged
on the data mover system. This error can also occur if the ANTASnnn address
space does not have the proper access authority to the HLQ state data
set name. See z/OS DFSMS Advanced Copy Services for
more information about the state data set.If the return code is present
with message ANTR5102E, locate the state data set that is used in
conjunction with the session that is being recovered. The HLQ specified
for the XRECOVER or XADVANCE command can be incorrect. The
reason code provides the specific details about why this data set
was not opened. This can be a non-PDSE data set. Correct the error
and reissue the failing command specifying the correct HLQ on the
command. Note: The message that activates this return code can be
preceded by an IEC143I message that provides additional information
regarding the cause of the data set open failure.
|
4010 | During XSTART, XRECOVER, or XADVANCE processing,
XRC has determined that the control data set cannot be opened. If
this return code appears with message ANTS5100E, verify that the XSTART
command specified the proper high-level qualifier (HLQ) for the control
data set. Verify that the HLQ control data set is defined and cataloged
on the data mover system. This error can also occur if the ANTASnnn address
space does not have the proper access authority to the HLQ control
data set name. See z/OS DFSMS Advanced Copy Services for
more information about the control data set.If the return code is
present with message ANTR5102E, locate the control data set that is
used in conjunction with the session that is being recovered. The
HLQ that is specified for the XRECOVER or XADVANCE command
can be incorrect. The reason code provides the specific details about
why this data set was not opened. Correct the error and reissue the
failing command, specifying the correct HLQ. Note: The message that
activates this return code can be preceded by an IEC143I message that
provides additional information regarding the cause of the data set
open failure.
|
4011 | During XSTART, XRECOVER, or XADVANCE processing,
XRC has determined that a journal data set cannot be opened. If this
return code appears with message ANTS5100E, verify that the XSTART
command specified the proper high-level qualifier (HLQ) for a journal
data set. Verify that a HLQ journal data set is defined and cataloged
on the data mover system. This error can also occur if the ANTASnnn address
space does not have the proper access authority to a HLQ journal data
set name. See SDM and XRC return codes for more information about
the journal data set.If the return code is present with message ANTR5102E,
locate a journal data set used in conjunction with the session being
recovered. The HLQ specified for the XRECOVER or XADVANCE command
can be incorrect. The reason code provides the specific details about
why this data set was not opened. Correct the error and reissue the
failing command specifying the correct HLQ on the command. Note: The
message that activates this return code can be preceded by an IEC143I
message that provides additional information regarding the cause of
the data set open failure.
|
4012 | During XSTART, XRECOVER, or XADVANCE processing, XRC has determined that either the state data set was not defined as a PDSE, or that the control data set was not defined as a PS data set. If this return code appears with message ANTS5100E, verify that the control and state data sets have been properly defined. If the return code is present with message ANTR5102E, locate the control or state data sets that were used in conjunction with the session being recovered. Verify that they are valid data sets (PDSE for the state, and PS for the control). Correct the error and reissue the failing command. |
4013, 4014 | These are internal errors. Cancel ANTASnnn and reissue the command. |
4015 | While processing an XSTART, XRECOVER, or XADVANCE command, SDM determined that the control, state, or journal data sets were not allocated with a DCB RECFM attribute of FB (fixed block). If this return code appears with message ANTS5100E, then verify that the data set in error has been properly allocated with an FB attribute.If the return code is present with message ANTR5102E, locate the control or state data sets that were used in conjunction with the session being recovered. Verify that they have been properly allocated with the FB attribute. Correct the error and reissue the failing command. |
4016 | While processing an XSTART, XRECOVER, or XADVANCE command, SDM determined that the control, state, or journal data sets were not allocated on direct access volumes. XRC requires these data sets to be on disk volumes. If this return code appears with message ANTS5100E, then verify that the data set in error has been properly allocated on disk volumes.If the return code is present with message ANTR5102E, locate the control or state data sets that were used in conjunction with the session being recovered. Verify that they have been properly allocated on disk volumes. Correct the error and reissue the failing command. |
4017 | While processing an XADDPAIR command, it was determined that the primary volume is behind a storage control that is not LRE-capable. XRC supports only ECKD-level systems that have the XRC hardware support. The volume cannot be supported by XRC. To process the volume, place it behind an XRC-supported storage control. See z/OS DFSMS Advanced Copy Services for more information. |
4018 | The data mover detected a lost record.
This is probably a hardware error where a record has been lost. Correct
any errors found in SYS1.LOGREC. When contacting IBM for assistance, provide a GTF trace, from both the application system and the data mover system, of I/O to the primary volume with the lost record, in addition to the data requested in the beginning of this section. |
4019 to 4022 | These are internal errors. Cancel ANTASnnn and reissue the command. |
4023 | This can be due to the system limit on resource managers being reached. You can wish to increase this limit. Cancel ANTASnnn and reissue the command. |
4024 | This is an internal error. Cancel ANTASnnn and reissue the command. |
4025 | An XRC address space cannot be created
in response to an XSTART or XRECOVER command. It is possible that
the number of address spaces allowed by the system has been exceeded.
This error is associated with message ANTU2000E which contains the
system return code and reason code for why the address space cannot
be created. When contacting IBM for assistance, provide associated SYS1.LOGREC information in addition to the data requested in the beginning of this section. |
4026 | This error is caused by an incomplete shutdown of a previous XRC session, and can be associated with a system abend. If the ANTASnnn address space is active, cancel both it and the ANTAS000 address space. Reissue the XSTART or XRECOVER command. If the problem persists, generate a dump (if possible) of the ANTAS000 and ANTASnnn address spaces. |
4027 | This return code is issued when attempting to make the volume specified on an XADDPAIR command, a FIXED utility device. An XADDPAIR command was issued for the specified primary volume with XRCUTL specified as the secondary volser. The specified volume is currently a utility device (which was previously added using the XRCUTL secondary volser) but is not a FIXED utility device, and the XSET UTILITY option of FIXED is currently active. The reason the XADDPAIR command failed is because an XDELPAIR command has not completed (XDELPAIR command was issued with the ATTIME or DRAIN option) for the specified volume. You must allow the XDELPAIR command to complete before issuing the XADDPAIR command. |
4028 to 4033 | These errors are caused by an incomplete shutdown of a previous XRC session, and they can be associated with a system abend. If the ANTASnnn address space is active, cancel both it and the ANTAS000 address space. Reissue the XSTART or XRECOVER command. If the problem persists, generate a dump (if possible) of the ANTAS000 and ANTASnnn address spaces. |
4034 | You have attempted to add a primary volume to the session that already exists within the session as either a primary or secondary volume. Issue an XQUERY VOLUME(ALL) command to determine which volumes are in the session. To change the primary pair, delete the volume pair with an XDELPAIR command, then reissue an XADDPAIR command. |
4035 | You have attempted to add a secondary volume to the session that already exists within the session as either a primary or secondary volume. Issue an XQUERY VOLUME(ALL) command to determine which volumes are in the session. To change the primary pair, delete the volume pair with an XDELPAIR command, then reissue an XADDPAIR command. |
4036 to 4042 | These errors are caused by an incomplete shutdown of a previous XRC session or the inability to start a new XRC session. These errors might also be associated with a system abend. Other error messages can be issued giving more detailed information. If the ANTASnnn address space is active, cancel both it and the ANTAS000 address space. Reissue the XSTART command. If the problem persists, generate a dump (if possible) of the ANTAS000 and ANTASnnn address spaces. |
4043 | This error results when an XSTART,
XRECOVER, or XADVANCE command is issued after an XRC session has logically
completed and before the particular ANTASnnn address
space (where the command was issued) has ended. If you are running
coupled XRC sessions, issue the XQUERY ALL command, and message ANTQ8200I
will be displayed for each currently active address space running
XRC. Then issue the console command DISPLAY A,ANTAS* to determine
all currently active ANTASnnn address spaces. The
address space that is listed on the DISPLAY console command that does
not show up on any of the ANTQ8200I messages is the address space
that caused this error. Wait for the following system console messages
to be issued (for this particular ANTASnnn address
space) before you issue an XRC command:
If the above messages do not appear within two minutes, issue CANCEL ANTASnnn to end the particular address space. It can be necessary to also end the ANTAS000 address space to completely end the XRC session. |
4044 | XRC has detected that the specified volume is defined as a VM minidisk. XRC does not support VM minidisks. If this error persists, search problem reporting data bases for a solution. If no solution exists, contact the IBM Support Center. Provide the system log and a copy of the ANTASnnn address space. |
4045 | An error has been detected while attempting to store a member in the hlq.XCOPY.session_id.STATE or the hlq.XCOPY.session_id.CONTROL data set with the STOW function. Determine why the STOW function failed and correct the error. In most cases, the error occurs because the data set did not have sufficient space to contain XRC information. See z/OS DFSMS Advanced Copy Services to determine the proper allocation sizes for the XRC control and state data sets. If this error causes suspension of a session or volumes in the session, the volumes that encountered this error requires complete synchronization after you have corrected the problem. You might also need to issue the appropriate XCOUPLE command if the session was a coupled XRC session. If this error occurs, perform the following procedure:
When you contact IBM for assistance, provide a copy of the failing control or state data set in addition to the data requested in the beginning of this section. |
4046, 4047 | These are internal errors. Cancel ANTASnnn and reissue the command. |
4048, 4049 | These are internal errors. |
4050 | The journal data set has been defined as a compressed data set, which is not supported. Journal data sets must be defined as noncompressed. The reason code indicates the number of the JRNLxx data set that is incorrectly defined. |
4051 | A journal data set is improperly defined. The journal data set must be defined as a sequential file (DSORG=PS). The reason code indicates the number of the JRNLxx data set that is incorrectly defined. |
4052 | A suspend request has been made for a volume which is already suspended. Reissue the command without specifying this volume. |
4053 | Dynamic allocation has encountered an error. Typical errors might be that the specified data set does not exist, that the data set has been allocated for exclusive use by another process, or in the case of a parmlib dataset that the data set has been migrated. The reason code that is associated with this return code was generated by the DYNALLOC facility. See "Interpreting Error Reason Codes from DYNALLOC" in z/OS MVS Programming: Authorized Assembler Services Guide to interpret the reason code. |
4054 | The requested function is not supported by the storage control LIC. |
4055 | An XQUERY command requesting output to a data set has failed because the data set specified could not be opened. See z/OS MVS System Codes to interpret the abend code reported by this return code. |
4056 | An XSTART or XADDPAIR command has
been issued. XRC has attempted to reinstate the storage control session
that previously existed, but the storage control session is already
active. This error indicates that the session is currently owned by
another session (which can be either XRC or concurrent copy). The
XSTART or XADDPAIR function is not able to use this storage control
session. If this return code is observed after an XSTART to restart an XRC session on a different LPAR, take the following steps to resolve the issue. First issue F ANTAS000,LISTSESS ALL and verify that the session in error is an XRC session and that it should not belong to another XRC session. If it should belong to another XRC session, issue an XDELPAIR, and then XADDPAIR the volume into the appropriate session. If it should belong to this XRC session, a SUSSESS will be required to suspend the active storage control session and allow the session to be re-registered to the appropriate XRC session. For
Enhanced Reader:
For a Non-Enhanced Reader mode:
|
4057 | An error was encountered in SDM data set processing. This might result from an incorrect parameter of a modify command to an ANT address space, or a TSO command for a XRC, FlashCopy®, or PPRC function. Reissue the command with correct syntax and options. If not encountered as a result of command processing, then treat as a SDM internal error. |
4058 | A command specified the ATTIME keyword. The target time specified has already passed. Reissue the command specifying a future time. |
4059 | The CANCEL keyword was specified for an XSUSPEND command, or an XRC internal command was issued to cancel a pending command. No pending command was found. This can be due to either the pending command having been completed, or another cancel command caused the pending command to be canceled. |
4060 | The CANCEL keyword has been specified for an XDELPAIR command, but there is no pending XDELPAIR command. Verify and reissue the command. |
4061 | The CANCEL keyword has been specified for an XEND command, but there is no pending XEND command. Verify and reissue the command. |
4062, 4063 | An XQUERY command requesting output to a data set has failed, probably because the data set size is too small or an I/O error was encountered. See z/OS MVS System Codes to interpret the abend code reported by this return code and see message ANTX5014E for error details. |
4064 | An XQUERY command to a data set has failed because the LRECL specified is too small. Reallocate the data set with a larger LRECL and reissue the XQUERY command. |
4065, 4066 | These are internal errors. |
4067 | An XQUERY command has been issued to an invalid data set type. The XQUERY command has failed. Reissue the command to a sequential data set. |
4068 | The session is being suspended because MODIFY ANTASnnn,RESTART was issued from the operator console. A dump has been generated, the software bitmaps have been saved, and the session will be suspended and automatically restarted. All volumes will remain in a suspended state until an XADDPAIR command is issued. |
4069 | An XDELPAIR or XSUSPEND command has been issued and one or more volumes specified with the command is in error. See previous messages for the cause of the error. Correct the error and reissue the command. |
4070 | An XADDPAIR command has been issued for a suspended primary volume. The volume is either on a different channel or has a different device address than existed when the volume was suspended. Issue an XDELPAIR command to remove the volume from the session followed by an XADDPAIR command to add it back. |
4071 | An XADDPAIR command has been issued for a suspended secondary volume, and the Subsystem Identifier (SSID) and/or Channel Connection Address (CCA) of the device has changed since the volume was last added. If this corresponds to a known reconfiguration event, you can use the REFRESHS function of the XSET command to update the device location information in the System Data Mover, and then retry the XADDPAIR. |
4072 | An XQUERY command to a data set has failed because dynamic allocation was unable to determine the organization of the data set. Verify that the data set has been created with the proper attributes, and cataloged. |
4073 | An XQUERY command requesting output to a data set has failed because the data mover does not have the proper RACF® authority to access the data set. |
4074 | An XQUERY command requesting output to a data set has failed because the data set is in use by another user. When the user frees the data set, the XQUERY command can be reissued. |
4075 | An XQUERY command requesting output to a data set has encountered an I/O error while writing to the data set. See message ANTX5014E for error details. |
4076 | A Catalog Locate error was detected while attempting to locate the journal control data set. The accompanying reason code indicates the catalog return code. |
4077 | An I/O error occurred
while attempting to read from the control data set. Reference any
ANT or IOS error messages associated with the I/O error, correct
the error if possible, and reissue the failing command. If an uncorrectable
error occurred on restart of a suspended coupled session, do the
following:
|
4078 | An I/O error occurred while attempting to write to an XRC data set. Reference any ANT and/or IOS messages for additional details on the nature of the error. If the error was encountered by an active XRC data mover session, correct the error and resynchronize to achieve consistency on the secondary volumes. If the message occurred during XRECOVER or XADVANCE, correct the error and reissue the XRECOVER or XADVANCE command. |
4079 | The unplanned outage function is not supported by this storage control. |
4080 | This error can occur during either
XRC XSTART command processing or during XADDPAIR processing. The data
mover is unable to determine the location of one or more of the primary
volumes associated with the volume’s associated storage control.
This can be because the storage control path is unavailable, the device
number channel connection address has changed (the volume has been
moved to another device), or in the case of a utility volume, the
volume is not online to the data mover system. During XSTART processing, message ANTX5011E is issued with this return code if a suspended primary volume encountered one of the above errors during reregistering of suspended sessions. During XADDPAIR processing, message ANTX5011E is issued with this return code for suspended primary volumes which encountered one of the above errors. Correct the error and reissue an XADDPAIR command to return the volume pair or pairs to the session. If you use an XDELPAIR command to remove the volume pair or pairs from the session(s), note that this will not remove the session on the controller. Additionally, if the volume associated with this error is a utility volume, this problem could be due to the unavailability of a primary volume. Check for previously issued messages associated with the storage control session, for ANTX5011E RC=4080, identifying primary volumes which have encountered one of the above indicated errors. |
4081 | This occurs after an attempt was made to add a volume to an XRC session when the CCA is greater than the XRC-supported number of volumes. |
4082 | This return code is issued when one
of the following occurs:
|
4083 | These are internal errors. |
4084 | The XADDPAIR command could not be processed because of XRC system resource constraints. If you have several XRC volume initializations currently running, wait for one or more of these to complete before resubmitting the XADDPAIR command. You can also use the XRC XSET command to lower the value used for the SYNCH parameter, which will reduce the number of concurrent XRC volume initializations. If the problem persists, issue the F ANTASnnn, DUMP command to collect diagnostic information. |
4085 | An XQUERY command was issued while XRC was processing an XRECOVER or XADVANCE command. The XQUERY command is terminated. The XQUERY command cannot be run during XRC recovery functions. The XRC recovery functions automatically provide the XQUERY output related to the XRC recovery command. |
4086 | An XDELPAIR command for a primary
volume or an XEND command has been issued. If this code is received
as a return code, the primary volume is in error. If it is received
as a reason code, the swap volume is in error. The volume is either in not in the configuration, or it is in the configuration but is not attached. The command was unable to remove the volume from the volume’s associated storage control session. Issue the MVS MODIFY console command with the TERMDVC option to remove the volume from the storage control session. If the volume is the last volume in the session, issue the MVS MODIFY console command with the TERMSESS option to terminate the storage control session. |
4087 | This is an internal error. |
4088 | A TSO XSET PARMLIB ACTION(APPLY) command was executed for a session ID that is not active. The XSET parmlib parameter value for ACTION cannot be APPLY. Only action VERIFY is allowed. |
4089 | A TSO XSET PARMLIB command was executed for a session ID that is not active. The XSET parmlib parameter DATASET is missing. |
4090 | The data set being accessed has an invalid record format. For example, a parmlib data set must have a fixed format. |
4091 | The data set being accessed has an invalid logical record length. For example, a parmlib data set must have a logical record length of 80. |
4092 | The data set being accessed has unknown characteristics. For example, a parmlib data set does not exist on a volume, but the catalog entry for the data set shows it residing on the volume. |
4093 | During volume resynchronization, a storage control has returned a bit map that has an invalid format. If flag SCTRAP is on, a state save is taken. If flag ABEND_LIC is on, a 9C4-6C abend is forced. |
4094 | The MVS system service IEFPRMLB, which is used to access concatenated parmlibs, returned the error indicated by the reason code associated with this return code. The format of the reason code is X'aaaabbbb', where 'aaaa' indicates the return code from IEFPRMLB and 'bbbb' indicates the reason code from IEFPRMLB. For additional information about the IEFPRMLB return and reason codes, see the z/OS MVS Programming: Assembler Services Reference IAR-XCT. |
4095 | During processing of an XRC XSTART or XADDPAIR SUSPENDED command, if the storage control indicates that a utility volume is currently a floating utility volume, but the volume was a fixed utility volume when the session was suspended, XRC fails the request to re-register the volume. This situation might occur if the storage control lost knowledge of whether the device associated with the volume was either floating or fixed, and thus reverted back to the default mode of floating. Contact your storage control support to determine if further analysis is needed if this situation is detected. This return code might be seen for a utility volume as well as all the primary volumes associated with the utility volume's storage control session. If the utility volume needs to be changed to a floating utility device, issue the XDELPAIR command to delete the volume from the session, and re-add the volume using the XADDPAIR command. Otherwise, issue the XRC XSET command specifying the UTILITY(FIX) option to change the type of utility volume to be added, and then reissue XADDPAIR command for the utility volume. |
4096 | An XADDPAIR command has been issued for a primary or secondary volume that has more than the maximum number of cylinders supported for XRC. The request is rejected. The reason code will contain the number of cylinders that the volume contains. |
4097 | Message ANTR5102E indicates that an XADVANCE command was issued to a session that encountered an error during XRECOVER processing. If the session is coupled, the XQUERY MASTER report will indicate that it is in an ARV state and that the XADVANCE command failed. The only commands that are allowed in this state are XRECOVER, XSTART, and XCOUPLE with the PURGE option. Determine which command (if any) needs to be executed, and issue the correct command. |
4098 | An XADVANCE or XRECOVER command was issued to a session that has already been recovered by the XRECOVER command. The command failed. XADVANCE and XRECOVER commands are not permitted in this condition. The only commands available for a session in this state are XSTART and XCOUPLE with the PURGE option. Determine which command (if any) needs to be executed, and issue the correct command. |
4099 | An XSUSPEND command has been issued for a utility volume. Utility volumes cannot be suspended because they are used only as a path to the storage control. The command request is failed. |
4100 to 4107 | These are internal errors. |
4104 | An attempt was made to merge an existing enhanced SCSESSION with another session using the XADDPAIR command with a new SCSESSION value for an existing utility volume. The command is rejected. The correct procedure for merging multiple SCSESSIONS into an enhanced session is to change single mode sessions into enhanced mode sessions. For example, if SCSESSION(AA) is enhanced and SCSESSION(BB) is non-enhanced, it is OK to perform XADDPAIR to the volume in SCSESSION(BB) with a new value SCSESSION(AA), but not vice versa. |
4105 | Internal error. While deleting a utility volume, a list of volumes in the SSID came back empty. This is a logical impossibility because it implies a deleting of a volume that doesn’t exist. |
4106 to 4107 | These are internal errors. |
4108 | An XADDPAIR request was issued specifying
the LOGPLUS option, or an XDELPAIR request was specified for a LOGPLUS
utility volume. The request failed. The reason code issued with this
return code indicates the reason the request failed.
|
4109 | An XADDPAIR request was issued specifying the LOGPLUS option. The request failed because the session indicated on the request was started via the XSTART command, which specified the SESSIONTYPE of MIGRATE. A LOGPLUS volume pair cannot be added to a MIGRATE session. |
4110 to 4111 | These are internal errors. |
4112 | The parmlib data set that is being accessed cannot be found. |
4113 | The member in a parmlib data set that is being accessed cannot be found. |
4114 | The parmlib data set that is being accessed caused an ABEND. The reason code shows the abend code. |
4115 | The data set that is being accessed has an invalid data set organization. For example, a parmlib data set must have a partitioned data set organization. |
4116 to 4117 | These are internal errors. |
4118 | Parameter library support was invoked and a syntax error was detected by RMM/TSO. The accompanying ANTI1nnnx messages describe the error and the corrective action. |
4119 | Parameter library support was invoked and a syntax error was detected. The accompanying ANTI1nnnx messages describe the error and the corrective action. |
4120 to 4121 | These are internal errors. |
4122 | The number of auxiliary SCIDs associated with an enhanced SCSESSION could not be increased because the total number of allowed sessions on the SSID would be exceeded. Concurrent Copy and XRC sessions both contribute to the limit on the number of sessions. |
4123 | Internal error. |
4124 | XDELPAIR specified the utility device of the primary storage control session for an enhanced multiple reader session group. The primary session utility volume can only be deleted when there are no other volumes in that storage control session. |
4125 to 4129 | These are internal errors. |
4130 | An attempt was made to add a primary volume to the session with a Write Pacing attribute, but the data mover does not recognize the storage controller as capable of supporting Write Pacing. |
4131 | I/O error occurred while attempting to retrieve write pacing information. |
4132 to 4136 | These are internal errors. |
4137 | The device number of the secondary device in the XADDPAIR command does not fall within any of the device number ranges specified in the SecondaryDeviceRange PARMLIB parameter. |
4138 | The secondary volser in the XADDPAIR command does not match any of the volser patterns in the SecondaryVolserPattern PARMLIB parameter. |
4139 to 4143 | These are internal errors. |
4144 | The volume specified on the XSET DVCBLOCK VOLUME TSO command or the XSET DVCBLOCK PVOLSER API request is not a primary volume in the specified XRC session. If you specified VOLUME(ALL), no volumes were found in the specified logical session. If the error continues, search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM Support Center. When contacting IBM for assistance, provide a copy of the associated SYS1.LOGREC information and a GTF trace, in addition to the data requested by IBM. |
4145 | An I/O error was encountered attempting to change the blocking threshold setting for a volume. The reason code that accompanies this return code indicates the I/O error that occurred when the XSET DVCBLOCK command attempted to change the blocking threshold setting for the volume specified in the message where this return code is issued. |
4146 | During a write to the STATE data set an error was returned indicating that PDSE MLT threshold maximum value has been exceeded. SDM attempted to close and reopen the STATE data set to resolve the problem. If the problem persists, search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM Support Center. |
4147 to 4148 | These are internal errors. |
4149 | XRC session exceeded time limit while waiting for more data movement buffers to become available. Most likely causes are READERPACINGWINDOW, READERPACINGLIMIT, and/or MAXTRACKSREAD parmlib values that are too high relative to the TOTALBUFFERS value and the number of readers in the session. |
4150 | This is an internal error. |
4151 | An attempt was made to XADDPAIR or XSET a volume with the DVCBLOCK(WP0) attribute, however the XRC parmlib value for DfltWritePacingLvl is zero. If a session-level default write pacing level is desired, modify XRC parmlib with an appropriate value for DfltWritePacingLvl and activate the change with the XSET PARMLIB command. Then resubmit the XADDPAIR or XSET command. |
4152 | An I/O error occurred during a query of PPRC status. |
4153 | This is an internal error. |
4154 | During XADDPAIR, the VOLSER of the primary volume could not be determined. |
4155 | During XADDPAIR, the VOLSER of the secondary volume could not be determined. |
4156 | During XADDPAIR, the device number of the ONLINE volume matching the primary VOLSER does not match the specified PDEVNUM parameter. |
4157 | During XADDPAIR, the device number of the ONLINE volume matching the secondary VOLSER does not match the specified SDEVNUM parameter. |
4158 | The System Data Mover attempted to retrieve a list of data mover sessions from a storage subsystem, but received invalid data. This may be due to a Licensed Internal Code error in the storage subsystem, a defect in channel extension hardware, or some other cause external to the System Data Mover. Details about the invalid data can be found in a LOGREC entry containing 'DESCRIPTION OF FUNCTION: XRC ERROR - ANTS5012'. Provide this information to the IBM Support center for problem determination assistance. |
4159 | An XADDPAIR command has been issued
for an existing Utility volume, but the System Data Mover was unable
to locate its associated storage control session. This can occur if
the session was previously terminated via the F ANTAS000, TERMSESS
comand. To recover from this error, the Utility volume must be removed using XDELPAIR, then re-added. if the Utility volume is associated with an Enhanced Reader primary or Single Reader storage control session, all associated volume pairs must first be removed using XDELPAIR, then re-added after the Utility volume is re-established. |
4160 | An XRC XADDPAIR request specified a device that is currently in the process of being re-sized. Devices are restricted from participating in a copy services relationship when being re-sized. Wait until the volume resize is completed and issue the failing request again. |
4300 | The session specified in the XCOUPLE ADD command is already coupled. Specify a different session name to couple to the master session, or use the XCOUPLE DELETE to remove an active session from the specified master session, or use the XCOUPLE PURGE to remove an inactive session from the specified master session. |
4301 | The session specified in the XCOUPLE DELETE command is not coupled. If the session is an active session, issue the XCOUPLE PURGE command to remove the session from the master session. |
4302 | This return code can refer to the cluster data set. |
4303 | This return code can refer to the cluster data set. |
4304 | The master data set that is associated with the specified logical session name contains invalid data. The reason code that accompanies this return code indicates the particular reason that the master data set is invalid and what you need to do to fix the problem. You might need to issue the XQUERY SUMMARY command to determine the master session name for the master data set that contains invalid data. If message ANTQ8246I does not contain the master session name, or the message is not issued, you might need to search the system log for a message that indicates the master session name that is associated with the specified logical session. If this return code occurs during XADVANCE or XRECOVER processing, it is not possible to complete the command in a coupled environment. Issue the XCOUPLE PURGE command and then reissue the XADVANCE or XRECOVER command to process the command. Use only information from this session. The
following are the different reason codes indicated with this return
code:
This return code can refer to the cluster data set. |
4304 |
If none of the above actions fixes the problem, you will need to reallocate the master data set. See the z/OS DFSMS Advanced Copy Services information, "Specifying the Master Data Set," for the attributes needed in reallocating the master data set. If you receive this error
for a cluster session, issue the following MVS console command to clear the the cluster
session, and then restart the cluster session and recouple the XRC
sessions through the cluster session:
Note: After
you issue the console command, you can restart the cluster session
by issuing the CREFRESH console command with the FORCE option.
|
4305 | The catalog entry for the master data set associated with the specified master session name indicates that the data set resides on multiple volumes. Reallocate the master data set on a single volume, and try the command again. This return code can also refer to the cluster data set. |
4306 | The maximum number of coupled sessions for the specified master session has been reached. You can remove one of the sessions in the master session by issuing the XCOUPLE DELETE or XCOUPLE PURGE command. |
4307 | A catalog locate error was detected
for the master data set that is associated with the specified master
session name. The first four numbers of the reason codes are the catalog
return code, and the second four numbers of the reason codes are the
catalog reason code. See the IDC3009I message in the z/OS MVS System Messages, Vol 6 (GOS-IEA),
for an explanation of the catalog return and reason codes, take the
appropriate action, and reissue the command. This return code can also refer to the cluster data set. |
4308 | The master data set that is associated
with the specified master session name has been defined with a user
label. Reallocate the master data set without a user label, and reissue
the command. This return code can also refer to the cluster data set. |
4309 | An error occurred attempting to read
the FORMAT-1 DSCB for the master data set associated with the specified
master session name. The reason code provided indicates the particular
OBTAIN macro return code received for this error. See the z/OS DFSMSdfp Diagnosis for
an explanation of the OBTAIN return code, take the appropriate action,
and reissue the command. You might need to reallocate the master data
set, particularly if the data was allocated with
extended attribute data set control blocks (format 8 and 9 DSCBs). This return code can also refer to the cluster data set. |
4310 | The master data set that is associated
with the specified master session name was allocated with insufficient
space. See the z/OS DFSMS Advanced Copy Services information,
"Specifying the Master Data Set," for the attributes to allocate the
master data set, reallocate the master data set, and reissue the command. This return code can also refer to the cluster data set. |
4311 | An error occurred attempting to conditionally
acquire the SYSDSN resource for the master data set that is associated
with the specified master session name. The indicated reason code
is the return code issued by the ENQ macro. See the z/OS MVS Programming: Assembler Services Reference ABE-HSP information,
the figure for the "Return Codes for the ENQ Macro with the RET=USE
parameter," to determine the specific error that occurred. Correct
the problem, and reissue the command. This return code can also refer to the cluster data set. |
4312 | An error occurred obtaining FORMAT-4
DSCB for the volume containing the master data set associated with
the specified master session name. The provided reason code indicates
the particular OBTAIN macro return code received for this error. See
the z/OS DFSMSdfp Diagnosis information for
an explanation of the OBTAIN return code, take the appropriate action,
and reissue the command. You might need to reallocate the master data
set. This return code can also refer to the cluster data set. |
4313 | The master data set associated with
the specified master session name has been allocated as a physical
sequential extended (PSE) data set. The master data set must be allocated
as a physical sequential (PS) data set. See the z/OS DFSMS Advanced Copy Services information,
"Specifying the Master Data Set," for the attributes in allocating
the master data set, reallocate the master data set, and reissue the
command. This return code can also refer to the cluster data set. |
4314 | The master data set that is associated
with the specified master session name could not be found in a system
catalog. Ensure that the master data set is cataloged and that the
data mover has access to the catalog that contains the master data
set, and reissue the command. This return code can also refer to the cluster data set. |
4315 | The master data set that is associated
with the specified master session name has not been allocated as a
physical sequential (PS) data set. The master data set must be allocated
as a physical sequential (PS) data set. See the z/OS DFSMS Advanced Copy Services information,
"Specifying the Master Data Set," for the attributes to allocate the
master data set, reallocate the master data set, and reissue the command. This return code can also refer to the cluster data set. |
4316 | After several attempts, the indicated
logical session has failed to conditionally acquire the SYSXRCMS resource
for the master data set that is associated with the specified master
session name. The SYSXRCMS resource is required by each logical session
in order to update the master data set. CXRC processing of another
master or local command probably delays the SYSXRCMS resource. Wait
a few minutes before reissuing the command that failed. For customers
using automation functions, this return code might be issued for those
commands that are not first processed by CXRC if master commands are
issued by multiple systems at the same time. For this situation, these
commands fail only because the first command (of the commands issued
at the same time) is busy performing the request. Issue the XQUERY master_session_name MASTER command to determine the status of each session that is associated with the master session. The coupled session status of UNK that is indicated on the XQUERY message of ANTQ8304I indicates that the master session could not communicate with the local session. Issue the XQUERY localsessionid command (at the local session system) to determine if the local session (with the UNK status) is active. If a local session is not active, see "Restarting an inactive XRC coupled session" in z/OS DFSMS Advanced Copy Services for instructions on how to restart an inactive session. If the local session is active, issue the F ANTASnnn, DUMP console command (at the local session system) to collect diagnostic information, and then contact IBM for assistance in determining the cause of the problem. You can then issue the CANCEL ANTASnnn console command, and restart the inactive session (with the instructions referred to previously in this paragraph). This return code can also refer to the cluster data set. |
4317 | The specified logical session name is associated with a different master session. Use the XQUERY command to determine the associated master session, issue the XCOUPLE DELETE or XCOUPLE PURGE command to remove the session from its currently associated master session, and then reissue the command. |
4318 | An XEND or XSUSPEND TIMEOUT command has been issued to a session which is coupled to a master session and identified by message ANTX5404E, which should accompany the message where this return code appeared. For coupled sessions, XEND and XSUSPEND TIMEOUT commands are only allowed when all volumes are suspended.If the intended result is the ending or suspension of all coupled sessions at the same consistency time, issue the XEND or XSUSPEND TIMEOUT command using the master session name. If it is not possible to use the master session name on the command (for example when at least one coupled session is non-interlocked or has all volumes suspended), first suspend all volumes in this logical session by issuing the XSUSPEND session_id VOLUME(ALL) command, and then reissue the command that failed. |
4319 | A command specifying a master session name was issued, and no coupled sessions were found to be associated with this master session name. This condition is not necessarily an error if you have not added any sessions to the master session via the XCOUPLE ADD command, or you have purged all coupled sessions from the master session via the XCOUPLE PURGE command. You can issue the XQUERY command for each of the individual sessions to determine the status of these sessions. This code can occur when the master data set cannot be accessed. The reason code will specify the cause. |
4320 | An error has been encountered while
accessing the master data set during XCOUPLE DELETE, XCOUPLE RELEASE,
or XEND/XSUSPEND master session command processing. One of the following
conditions applies:
|
4321 | A master session command was issued. A local session, indicated in the master data set as being coupled to the master session, did not acknowledge the request to process the command. Issue the XQUERY mastersessionid MASTER command to determine which local session could not process the command. The local session status of UNK that is indicated on the XQUERY message of ANTQ8304I indicates that the master session could not communicate with the local session. Issue the XQUERY localsessionid command (at the local session system) to determine if the local session (with the UNK status) is not active. If a local session is not active, see the "Restarting an inactive XRC coupled session" topic in z/OS DFSMS Advanced Copy Services for instructions on how to restart an inactive session. If the local session is active, issue the F ANTASnnn, DUMP console command (at the local session system) to collect diagnostic information, and then contact IBM for assistance in determining the cause of the problem. You can then issue the CANCEL ANTASnnn console command, and then restart the inactive session (with the instructions that are referred to previously in this paragraph). |
4322 | The control data set was determined to not have a record format of physical sequential (PS). The XCOUPLE ADD command fails. If you are running XRC coupled sessions, the control data set must be a physical sequential data set. |
4323 | During processing of an XCOUPLE PURGE command, information for the coupled session could not be found in the STATE data set associated with the session, and the associated master data set was not found. The XCOUPLE PURGE command fails. This condition is not an error if you previously issued the XCOUPLE DELETE or XCOUPLE PURGE command for this session. |
4324 | The indicated logical session was unable to complete the specified command in the allotted time; therefore, the command failed. Review the system log where the command was initially issued for other ANT error messages related to the indicated logical session and master session. Issue the XQUERY MASTER command to determine the status of all of the coupled sessions associated with the indicated master session. You can have to reissue the command after making the necessary corrections, as indicated by these other error messages.Return code 4324 can also be generated in conjunction with return code 4321, in which case, one or more of the coupled sessions will show UNK state in the XQUERY MASTER report. In this case, the problem is indicated by return code 4321. Return code 4324 is additional confirmation that the command failed. |
4325 | During processing of the indicated command, the attempt to enqueue the qname of SYSXRCLS and the rname of the logical session name failed. The logical session can be active on another system. Each logical session must have a unique name, and can only be active on one system at a time within the same global resource serialization ring. If you are running CXRC, issue the XQUERY MASTER command for each master session that is active in your complex to determine status of the logical session name. |
4326 | The XCOUPLE PURGE command failed because neither the state data set for the specified logical session name nor the master data set for the specified master session was found. Reissue the command specifying a logical session name that is currently associated with a master session. |
4327 | The XCOUPLE PURGE command was issued specifying a master session name or high-level qualifier to which the logical session is not associated. Issue the XQUERY SUMMARY report to determine the master session name and high-level qualifier with which the specified logical session is associated, and reissue the command. |
4328 | During XCOUPLE ADD processing during
either session restart or command invocation, the indicated logical
session's state data set indicated that the session was previously
coupled to a master session. The associated master data set currently
does not indicate that the logical session is coupled to the master
session (this could be due to an XCOUPLE PURGE command having been
issued while the logical session was inactive). Either issue the XCOUPLE
ADD command to recouple the session to the master session, or issue
the XCOUPLE DELETE command to remove the indication from the session's
state data set that the session is coupled. Note: SDM can issue the XCOUPLE DELETE command during XCOUPLE ADD processing if a failure is detected attempting to add a session back into a master session. During XCOUPLE ADD for recoupling (either internally
as a result of session restart processing, or by executing the command
while in a COUPLE FAILED state), the indicated logical session's state
data set indicated that the session was previously coupled to a master
session. The associated master data set currently does not indicate
that the logical session is coupled to the master session (this could
be due to an XCOUPLE PURGE command having been issued while the logical
session was inactive). Either issue the XCOUPLE ADD to recouple the
session to the master session, or issue the XCOUPLE DELETE command
to remove the indication from the session's state data set that the
session is coupled.
Note: An XCOUPLE DELETE operation can have been
processed internally as part of the XCOUPLE ADD command, which failed.
|
4330 | While processing an XADDPAIR command,
or while attempting to update the master data set during XRC couple
processing, the indicated coupled session was found to be in COUPLE_FAILED
status. The XADDPAIR command fails or the update to the master data
set fails, appropriately. A previous error occurred for the session
which put the session in this state. See the return code issued by
a previous message (ANTC54xxE) to determine the error that
occurred and the action to take. If the previous error that occurred was due to an error for the cluster session to which the XRC session was coupled, and it has been determined that restarting mirroring using XRC is the correct recovery technique, after re-starting the cluster session, issue the XCOUPLE command with the ADD parameter to re-add each session that was previously in the cluster session (after the cluster session is re-started, issue the XSTATUS CLUSTER command to determine the sessions that were previously coupled via the cluster session). You can then issue the XCOUPLE command with the RELEASE parameter to release the master session from the HOLD status, and then re-add the volumes to the sessions . |
4331 | A command has been specified with an ATTIME value for a coupled session. The time specified has already passed the time that represents the last processed consistency time for the master session with which the coupled session is associated. Reissue the command specifying a future time. |
4332 | A command was issued specifying a master session name. The command is failed. At least one coupled session in this master session was found to not have a consistency time. After a logical session is started, an update to a primary volume in the session must be made before a consistency time can be established for the session. Issue the XQUERY MASTER command to determine which session indicates no JOURNAL DELTA time value, or the VOL status for the session is NOV indicating that there are no volumes in the session. As soon as an update has been processed for the session, reissue the command. |
4333 | A command was issued specifying a master session name and requesting that a pending master session command be canceled. The command fails. At least one coupled session in this master session has already processed or begun to process the pending command. The pending command must complete on all coupled sessions associated with the master session. |
4335 | A master session command was issued. The command fails. The command cannot be processed because another master session command is currently pending or is being processed by at least one of the coupled sessions in the master session. Issue the XQUERY MASTER command to determine if the current master command has completed, and then reissue the command which was failed. If a specific consistency time is required for all coupled sessions, you might need to restart all sessions and issue a master command with the specified ATTIME value. |
4336 | An XCOUPLE ADD command was issued
to add a session to a master session. The command fails because the
master session has a master session command that is pending or has
not completed. Issue the XQUERY MASTER command to determine the status
of each coupled session that is associated with the master session.
|
4337 | A master session command was issued,
and at least one of the coupled sessions that is associated with the
master session is not interlocked. In order for a session to become
interlocked, all of the following conditions must be met (issue the
XQUERY MASTER command to determine these conditions):
To interlock a session, you might need to issue the XCOUPLE DELETE or XCOUPLE PURGE command to first remove a coupled session from the master session, and then issue the XCOUPLE ADD command to recouple the session. If the master session is in HOLD status, issue the XCOUPLE RELEASE command to remove this HOLD status. |
4338 | XCOUPLE ADD was issued, and the existing sessions are in a suspended or ended state. (This state occurs when any session's address space is not active for primary processing.) Adding a new session while in this state would have the potential to disrupt the ability to recover all volumes to a common consistency time. The XCOUPLE ADD command fails. |
4339 | The XCOUPLE DELETE was issued for a coupled session, but a least one coupled session in the same master session has begun processing a master command. The command fails. Issue the XQUERY MASTER command to determine when all sessions in the master session have completed processing the master command, and then reissue the XCOUPLE DELETE command. |
4340 | An XRECOVER command was issued for a coupled session, but at least one coupled session in the same master session is still active. The command failed. All coupled sessions in the master session must be in an inactive state before you can issue the XRECOVER command. To determine the state of each coupled session in the master session, issue the XQUERY MASTER command, and then issue the XEND or XSUSPEND command for each session that is still active, before reissuing the XRECOVER command.Return code 4340 can also be generated when the message is issued indicating that the XSUSPEND or XEND command processing is complete, but the ANTAS00n address space has not terminated for that session. To determine whether the ANTAS00n address space is active for the session, issue the D GRS,RES=(SYSXRCLS,*) command. |
4341 | An XCOUPLE ADD command has been issued to add a new session to a master session, and at least one coupled session in the master session is in a state of recovery (the session status as shown on message ANTQ8304I indicates either RCV or ARV). Issue the XQUERY MASTER command to determine the status of each coupled session. You must issue the XRECOVER command for each coupled session and allow the recovery to complete before issuing the XCOUPLE ADD to add a new session to the master session. If you do not wish to recover a coupled session in the master session, issue the XCOUPLE DELETE or XCOUPLE PURGE command to remove the session from the master session. |
4342 | An XCOUPLE ADD command has been issued to add a logical session to a master session. The command fails because the logical session was started using the SESSIONTYPE(MIGRATE) option. Issue the XEND or XSUSPEND command for the logical session, and then restart the logical session using the SESSIONTYPE(XRC) option on the XSTART command. You can then reissue the XCOUPLE ADD command to add the logical session to the master session. |
4343 | This is an internal error. |
4344 | An XCOUPLE PURGE command was issued for a currently active session. The command failed. Issue the XCOUPLE DELETE command to remove an active coupled session from a master session.Return code 4344 can also be generated when the message indicating that the XSUSPEND or XEND command processing is complete is issued, but the ANTAS00n address space has not terminated for that session. To determine whether the ANTAS00n address space is active for the session, issue the D GRS,RES=(SYSXRCLS,*) command. |
4345 | A master session command was issued, and one or more active coupled sessions, associated with this master session, have the volume status of AVS, ERR, or SYM as indicated on message ANTQ8304I. All coupled sessions that are associated with the master session must have a session status of ACT and a blank volume status when you issue a master session command. The command fails. Issue the XQUERY MASTER command to determine the status of the sessions that are associated with the master session. |
4346 | An XRC command was issued which can
potentially disrupt the ability to recover coupled XRC sessions in
the associated master session to a consistent time. The command fails.
The master session is in a HOLD state. Before the command can be processed,
you must ensure that all of the coupled sessions in the master session
can be recovered to a consistent time by performing at least one of
the following actions:
Once the appropriate actions have been taken to ensure that the coupled sessions associated with the master session can be recovered to a consistent time, issue the XCOUPLE RELEASE command to remove the HOLD status of the master session. IBM recommends that you make backup copies of secondary volumes and journals for all coupled sessions before you use this command. |
4347 | A master session command was issued, and one or more coupled sessions, associated with this master session, have no volume pairs in the session. All coupled sessions that are associated with the master session must have at least one volume pair, and at least one primary volume update must have been journaled and written to the secondary volume before you can issue the master session command. The command fails. Issue the XQUERY MASTER command to determine the status of the sessions associated with the master session. |
4348 | This is an internal error. |
4349 | An XCOUPLE ADD command has been issued to add a logical session to a master session. The command fails because the logical session has a pending XRC command. Issue the XQUERY SUMMARY command for the logical session. Message ANTQ8234I will indicate the command that is pending. Either issue the appropriate command with the CANCEL option to cancel the pending command, or wait for the pending command to complete. |
4350 | An XADVANCE command was issued for
an active session whose volumes are not all suspended. The command
fails. All volumes in the session must be suspended before you can
issue the XADVANCE command. You can issue the XQUERY VOLUME command
to determine the volume status of volume pairs in the session. Issue
the XSUSPEND VOLUME(ALL) command with either the IMMEDIATE, ATTIME,
or DRAIN options to suspend all volumes in the session. Then you can
reissue the XADVANCE command. Note: If the session is an active coupled
session, and after you suspend the volumes in the session, the session
will become non-interlocked with the other coupled sessions that are
associated with the master session.
|
4352 | An XCOUPLE PURGE command was issued specifying a logical session name which is not associated with the specified master session name (the master data set does not indicate that this session is a coupled session in this master session). The COUPLE member has been removed from the session's state data set. The session is no longer a coupled session. No further action is required. |
4353 | The logical session for an XCOUPLE PURGE command was not found in the master data set for a session for which a state data set was not found. |
4354 | An XSUSPEND VOLUME(ALL) CANCEL command was issued specifying a master session name. The command is rejected. You must issue the XSUSPEND VOLUME(ALL) CANCEL command against each individual session in the master session. Issue the XQUERY MASTER command to determine the names of all the sessions associated with the master session. |
4355 | A command has been issued with the CANCEL option for a logical session that is currently coupled. The command is failed. The command must be issued with the session's associated master session name. You cannot CANCEL a pending command for an individual coupled session. |
4356 | The master data set associated with the indicated master session name is not on a cylinder boundary. The master data set must be allocated with the primary allocation specified as CYL. See the z/OS DFSMS Advanced Copy Services for the attributes required to allocate the master data set, and reallocate the master data set. |
4357 | A master session command was issued specifying the CANCEL option. No master command is currently pending. The command fails. Issue the XQUERY MASTER command to determine if any master command is currently pending. |
4358 | A master session command was issued specifying the CANCEL option. The current pending master command does not match the command issued with the CANCEL option. The command fails. Issue the XQUERY MASTER command to determine the master command which is currently pending, and reissue the appropriate command with the CANCEL option. |
4359 | The XQUERY ALL MASTER command was issued. The session ID of ALL is not allowed on the XQUERY MASTER command. You need to specify a particular master session name, and reissue the command. |
4360 | A master session command was issued, and one or more coupled sessions, associated with this master session, are in an ended or suspended state. The command fails. Before ending or suspending the remaining active coupled sessions, all volumes in these sessions must be suspended. You can suspend the volumes in the active sessions by issuing the XSUSPEND VOLUME(ALL) command for each active coupled session (which will change the session's coupled status to NON-INTERLOCKED), and then by issuing the XEND or XSUSPEND command for each of these sessions. Do not use the master session name on these commands. If you wish to have a session remain in an interlocked status, see z/OS DFSMS Advanced Copy Services for the steps to take. |
4361 | An active XRC session or Cluster is already using the Cluster Identifier for this LPAR. Note: The
reason code associated with this return code is typically the one
that the ENQ system call returns.
|
4362 | The Master Control Data Set cannot be located or has unusable attributes. |
4363 | The Cluster Control Data Set cannot be located or has unusable attributes. This error can appear if the Cluster Control data set is allocated with extended attribute data set control blocks (format 8 and 9 DSCBs). |
4364 | Unable to acquire common storage for Cluster Manager. |
4365 | Commands using a Cluster Identifier as session_id are not allowed. |
4366 | Cannot explicitly couple an individual XRC session to a Cluster. |
4367 | An XRC couple function required the use of the cluster session, but the cluster session was found to be inactive. Ensure that the ClusterMSession and ClusterName parameters of the XRC parmlib member are specified correctly, and issue the MVS MODIFY operation of CREFRESH to start the cluster session. If XRC sessions were coupled through the cluster session, after the cluster session is restarted, issue the XCOUPLE command with the ADD parameter to re-add each session that was previously in the cluster session (after the cluster session is restarted, issue the XSTATUS CLUSTER command to determine the sessions that were previously coupled via the cluster session). You can then issue the XCOUPLE command with the RELEASE parameter to release the master session from the HOLD status, and then re-add the volumes to the sessions. |
4368 | Clustering is disabled on this system. |
4369 | Cluster Monitor Data Set cannot be located or has unusable attributes. |
4370 | Cannot couple to a master session other than the one associated with this system's Cluster. |
4371 | Maximum number of coupled session per cluster exceeded. |
4372 | An I/O error occurred attempting to access the Cluster Control Data Set. |
4373 | One or more sessions are coupled to the master session to be associated with the cluster. |
4374 | One or more coupled sessions are currently active on the LPAR. |
4375 | One or more sessions are currently coupled through the cluster. |
4376 | A problem occurred while attempting to terminate clustering. |
4377 | Internal error. |
4378 | XRC was unable to obtain common storage area (CSA) to process cluster monitor data. If the cluster session was being started, XRC did not start the cluster session because of the shortage of CSA. If the cluster session was already active, and the XRC MVS console command of CREFRESH was issued to enable cluster monitoring, XRC was unable to enable cluster monitoring because of the shortage of CSA. It is recommended that you increase the amount of CSA allotted to the system in which XRC is running. |
4379 | XRC was unable to obtain a serialization resource to perform cluster session processing. The cluster session is not started or the cluster session is ended. Issue the MVS console command of CREFRESH to start the cluster session. |
4380 | This is an internal SDM error. |
4381 | The XRC command XCOUPLE ADD for a session failed to be coupled to a master session through a cluster session, because XRC determined that the session was already coupled to the master session. Issue the XCOUPLE command with the DELETE or PURGE parameter to uncouple the active or inactive XRC session from the master session respectively, and then reissue the XCOUPLE ADD command. |
4382 | During restarting of an XRC session, XRC determined that the session was previously coupled to a cluster session, but the cluster session is currently disabled. The XRC session is not restarted. Issue the XCOUPLE PURGE command to uncouple the session, or enable the cluster session before restarting the XRC session. |
4383 | This is an internal SDM error. |
4384 | The XRC parmlib parameter value for MonitorWakeup for the indicated XRC session is different than the MonitorWakeup value for the indicated cluster session. The value used for the XRC session will be the value used by the cluster to ensure that the XRC session gathers monitor data using the same MonitorWakeup interval. The MonitorWakeup value for XRC session will be ignored. |
4385 | The indicated cluster session was unable to contact the indicated XRC session to request monitor data from the XRC session. The cluster session will no longer accumulate cluster monitor data using monitor data from this XRC session. In most cases, the cause of this error is that the XRC session is no longer active. Restarting the XRC session and recoupling the XRC session through the cluster session will reactivate cluster monitoring for the XRC session. |
4386 | The indicated XRC session was unable to provide monitor data to the indicated cluster session within an allotted time. This condition will be indicated in the cluster accumulated monitor data indicating that not all XRC sessions coupled through the cluster session have provided individual XRC session monitor data for the monitor interval. The message associated with this return code will be issued on the first occurrence within an hour's worth of cluster monitor intervals, and will then be issued again at the end of the hour's worth of cluster monitor intervals where the reason code will indicate the number of times this condition occurred for the XRC session for the hour's worth of cluster monitor interval. The associated message can be suppressed by specifying the NoMonitorMessage parmlib parameter value of NO. |
4387 | XRC attempts to start or restart a cluster session,
but is unable to start the session. XRC determines that the master
session name found in the parmlib member ANTXIN00 does not match the
master session name found in the cluster data set, and sessions are
currently coupled to the master session found in the cluster data
set through the cluster session. If you want to change the master
session associated with a cluster session that currently has sessions
coupled through the cluster session, take the following steps to uncouple
these sessions from the master session first:
|
4399 | An attempt to XCOUPLE ADD a session to a cluster failed because of excessive time spent waiting to obtain serialization. The reason code in the
message provides additional information:
Check SYSLOG for XRC error messages related to coupling or clustering. Check for abnormal termination of either the Cluster or data mover address spaces (ANTASnnn or ANTCLnnn). Correct error conditions and restart Cluster if necessary. For reason codes 1 and 3, dump the Cluster address space (ANTCLnnn) for subsequent problem determination. Remove any remaining sessions from the Cluster with XCOUPLE DELETE. Disable the cluster and restart it. If the Cluster address space is not responsive, cancel and restart it. For reason code 2, determine which data mover address space (ANTASnnnn) is associated with the XCOUPLE ADD that did not complete. Dump the address space for subsequent problem determination, and then cancel it. The data mover might then be restarted and coupled. |
4500 | XSTART failed because
of a transition from MODE(HYPER-PPRC) to MODE(NORMAL) using the
default value for MODE. This happens when a session was previously
started in the HYPER-PPRC mode, and then XSTART is entered without
the MODE parameter. This might be a result of entering the XSTART
command through TSO. This mode is only
supported in sessions controlled by GDPS®.
If the desired result is to disable the HYPER-PPRC mode, the mode must be disabled through GDPS as specified in GDPS Metro/zGlobal Mirror: Planning and Implementation Guide, order number ZG24-1757. If the desired result is to have HYPER-PPRC mode enabled, then GDPS must be used to manage the session, and the mode must be configured as specified in GDPS/XRC VvRr Installation and Customization Guide, order number ZG24-6704. |
4501 | The XRC session is in MODE(HYPER-PPRC) and the
primary volume specified on the XADDPAIR command is not a PPRC primary
volume. Establish a PPRC relationship from the XRC primary volume to its associated HA volume, or a FAILOVER mode PPRC relationship, and reissue the XADDPAIR command. |
4502 | The XRC session is in MODE(HYPER-PPRC) and the
PPRC relationship found on the XRC primary volume does not match the
relationship previously recorded for this volume. Repair the PPRC relationship to match the previously recorded one, or use XDELPAIR to remove the XRC pair followed by XADDPAIR to permit the new PPRC relationship to be used. |
4503 | The swap volume storage control session id is
different from the primary volume’s
SCID. Determine if the swap volume is the correct volume according to the configuration, and if its reported XRC session is active. If it is an incorrect volume then correct the PPRC relationships ,so that the primary volume is associated with the desired swap volume. If the PPRC relationship is correct, remove the swap volume from any existing XRC sessions, and/or terminate the incorrect XRC controller session. In either case, reissue the XADDPAIR command once the existing relationship(s) have been corrected or terminated. |
4504 | The swap volume has an existing SCID that is
not in a state where this XRC session can attach to it. The volume
is (was) in use by XRC on a different z/OS instance. If there is an existing XRC session in which the swap volume is a primary device, suspend or end the session. If there is no active XRC session use the SUSSESS or TERMSESS command to condition the session so it can be picked up by this system, or terminate it. Then reissue the XADDPAIR command. |
4505 | During an XDELPAIR operation, the XRC session
for the associated swap volume could not be removed. XRC functions
might still be activated on this swap device. Since the swap sessions will not be cleaned up automatically, the F ANTAS000,TERMSESS command(s) will need to be issued for each of the affected sessions. In addition, if this warning was issued as a result of an XEND after an unsuccessful transition from mode normal to mode HYPER-PPRC, all of the sessions in an ER group (as observed with an F ANTAS000,LISTSESS command) may need to be manually terminated on the swap device even though only a subset of swap utilities were added. |
4506 | The primary storage control is not enabled for the PPRC+XRC HyperSwap® function. |
4507 | The command or command option requested is only supported in a session that has MODE(HYPER-PPRC) active. The session is not in the required mode. |
4508 | The swap volume cannot be incrementally resynchronized to the remote volume after a HyperSwap, because the XRC volume pair has never reached full DUPLEX. |
4509 | The swap volume cannot be incrementally resynchronized to the remote volume after a HyperSwap, because the resynchronization bitmaps have not been switched enough times to reduce the number of tracks to copy. Check the value of ChangedTracks and/or DelayTime specified for the BITMAP section of XRC Parmlib support, and reduce the values if necessary. |
4510 | A previous bitmap switch operation at the host volume was not successfully replicated on the swap volume. Refer to preceding message ANTX5132W. |
4512 | During XSWAP PERFORM processing, a SCSESSION was found not to be suspended. All volumes and SCSESSIONS in the XRC session must be suspended to process XSWAP PERFORM. This function is called from GDPS. For problem solution, see GDPS/XRC VvRr Installation and Customization Guide, order number ZG24-6704. |
4513 | An attempt was made to modify
the configuration of XRC Enhanced (Multiple) readers. The change requires
certain volumes in the session to be suspended, but they were not.
This includes:
|
4516 | The maximum number of storage control session IDs on the LSS would be exceeded. This return code might have resulted from XADDPAIR of a utility volume (XRCUTL), or from activation of a PARMLIB with too high a value for NumberReaderTasks. The utility volume is not added, or the number of reader tasks is not increased. Correct the configuration and if necessary, reissue the failing command. |
4517 | An attempt was made to convert an existing single mode utility volume to Enhanced Reader using an XADDPAIR command that specified a new SCSESSION value that did not already exist in the utility volume's SSID. The command is rejected. The correct procedure for converting a single mode utility to the Enhanced Reader is to specify an existing SCSESSION name for the first converted reader in the SSID and then specify that same SCSESSION name for all other utility volumes in that SSID. |
4519 | The SWAP volume is not the same volume as the PRIMARY volume's PPRC target. For problem solution, see GDPS/XRC VvRr Installation and Customization Guide, order number ZG24-6704. |
4520 | The PPRC pair state between the PRIMARY and SWAP volumes is incorrect. For problem solution, see GDPS/XRC VvRr Installation and Customization Guide, order number ZG24-6704. |
4521 | The SWAP volume CCA is different from the PRIMARY volume CCA. A 1 to 1 correspondence between PRIMARY and SWAP volume CCA's is required. This is likely to be a GDPS configuration error. For problem solution, see GDPS/XRC VvRr Installation and Customization Guide, order number ZG24-6704. |
4522 | The SWAP volume SSID is different from the SWAP volume SSID of other volumes in the same primary SSID. A 1 to 1 correspondence between PRIMARY and SWAP volume SSID's is required. This is likely to be a GDPS configuration error. For problem solution, see GDPS/XRC VvRr Installation and Customization Guide, order number ZG24-6704. |
4523 | A SWAP device was specified on the XADDPAIR command but the XRC session is not in MODE(HYPER_PPRC). SWAP devices are not allowed in this mode. This is likely to be a GDPS configuration error. For problem solution, see GDPS/XRC VvRr Installation and Customization Guide, order number ZG24-6704. |
4524 | A SWAP device was not specified on the XADDPAIR command but the XRC session is in MODE(HYPER_PPRC). SWAP devices are required in this mode. This is likely to be a GDPS configuration error. This is likely to be a GDPS configuration error. For problem solution, see GDPS/XRC VvRr Installation and Customization Guide, order number ZG24-6704. |
4525 | The XSWAP command was issued for a session that is not in MODE(HYPER_PPRC). This is likely to be a GDPS configuration error. For problem solution, see GDPS/XRC VvRr Installation and Customization Guide, order number ZG24-6704. |
4526 | The NumberReaderTasks value is nonzero but the enhanced function is not available on this control unit. |
4527 | An XADDPAIR command with a new SCSESSION value was attempted for a volume which is not a utility volume. Changing the SCSESSION of a non-utility volume is not allowed. Instead, change the SCSESSION of a utility volume, which will then merge all volumes in that SCSESSION on that SSID into an enhanced session. |
4528 | The XADDPAIR command failed to create a new auxiliary SCID because the maximum supported number of SCIDs is already active for the enhanced session. |
4529 | The value of NumberReaderTasks has been decreased. To reduce the number of auxiliary sessions, follow the reduction procedure in z/OS DFSMS Advanced Copy Services. |
4530 | The current value of AllowEnhancedReader is
NO, and at least one storage control session is in enhanced mode.
If this return code is received in response to an XSET command to
apply a PARMLIB change, the parameter value is not changed. When received
in response to an XADDPAIR command, the XADDPAIR command fails. If the change of AllowEnhancedReader from YES to NO is correct, follow the enhanced multiple reader disablement procedure in z/OS DFSMS Advanced Copy Services before continuing with volume resynchronization through the XADDPAIR command. If the parameter change is incorrect, issue the XSUSPEND command with TIMEOUT parameter, update the PARMLIB, and issue the XSTART command again. |
4531 | An XADDPAIR command did not specify the PDEVNUM parameter, which is required for MODE(HYPER_PPRC). This is likely to be a GDPS configuration error. For problem solution, see GDPS/XRC VvRr Installation and Customization Guide, order number ZG24-6704. |
4532 | The number of the storage control sessions (the total of primary and auxiliary) is less than the NumberReaderTasks parameter for the SSID and SCSN containing the volume pair. Either add utility volumes (with secondary volser of XRCUTL) or configure additional alias devices on the utility devices to equal or exceed the NumberReaderTasks parameter; or reduce the NumberReaderTasks if the number of utility plus alias devices is correct. If the RequireUtility parameter is not desired, remove it, activate the new parmlib setting, and issue the XADDPAIR command again. |
4533 | XDELPAIR of a utility volume will reduce the number of the available read devices below the value of NumberReaderTasks for the SCSN. The XDELPAIR command is rejected. To reduce the number of auxiliary volumes in the enhanced multiple reader group, the NumberReaderTasks value must be reduced before issuing the XDELPAIR command again. |
4534 | During XSTART or XSET PARMLIB, the value of MaxTotalReaderTasks was less than the number of storage control sessions already in the XRC session. Determine the value needed from prior XQUERY STORAGECONTROL reports and update PARMLIB, then reissue the command. |
4535 | Processing of XADDPAIR with the SUSPENDED option was rejected, because some utility devices are on enhanced multi-reader capable control units, and have not been converted to enhanced mode. Use the XADDPAIR command for the utility volumes to convert them to enhanced mode according to the procedure of converting to enhanced mode in z/OS DFSMS Advanced Copy Services and issue the XADDPAIR SUSPENDED command again. |
The following SDM Return Codes have been annotated to add the hexadecimal notation next to the numerical equivalent. | |
4536 | The XSWAP PERFORM command was issued but not all volumes are in a suspended state. For problem solution, see GDPS/XRC VvRr Installation and Customization Guide, order number ZG24-6704. |
4537 | Internal error. |
4538 | The XADDPAIR command detected that a utility volume is the primary of a PPRC relationship in MODE(HYPER_PPRC). Utility volumes might not be in a PPRC relationship. This is likely to be a GDPS configuration error. For problem solution, see GDPS/XRC VvRr Installation and Customization Guide, order number ZG24-6704. |
4539 | An XADDPAIR of a utility was specified with a SWAPDEV whose VOLSER could not be read. This error can be caused by an I/O error in trying to read the VOLSER or that the SWAPDEV does not have a VOLSER associated with it. If an I/O error is suspected, make sure the device is available for I/O. If there is no VOLSER, use ICKDSF to initialize the volume. |
4540 | The SWAP device does not support the MzGM Incremental Resync function. |
4541 | This return code indicates that pseudo-error processing has been entered as a result of an XSWAP PREPARE command. This is a normal part of PERFORM and is not considered an error unless PREPARE also fails to complete. |
4542 | The XSWAP PREPARE command did not complete in the expected amount of time. |
4543 | The XSWAP PERFORM command encountered errors with the SWAP volumes. The return code reported with message ANTX5134E identifies the specific error. |
4544 | The XSWAP PERFORM command did not complete in the expected amount of time. |
4545 | The XSWAP PERFORM command encountered an internal error that prevented XRC operations from continuing. Suspend the session with XSUSPEND TIMEOUT and restart it with XSTART. |
4546 | Internal error. |
4547 | When looking for a swap device by using its SSID and CCA, it could not be found in system control blocks. Check the swap device number to ensure that it is configured for the system. |
4548 | When looking for a device by using its SSID and CCA, it could not be found in system control blocks. Check the device number to ensure that it is configured for the system. |
4549 | The AllowEnhancedReader parameter changed from NO to YES but there are not enough utility devices available to satisfy the NumberReaderTasks parameter. |
4550 | The AllowEnhancedReader(YES) parameter was specified for a session with MODE(HYPER_PPRC). These two functions are not currently supported in the same XRC session. |
4552 | The XSTART command to restart a session in enhanced reader mode found that the NumberReaderTasks value had previously been specified and is not currently present in PARMLIB. The XSTART command does not restart the session. If the NumberReaderTasks parameter should be nonzero, update the PARMLIB with the correct value. If a zero value for NumberReaderTasks is desired, it must be explicitly specified in the PARMLIB. After the value is corrected, reissue the XSTART command to restart the XRC session. |
4560 | XADDPAIR was issued to a Utility (XRCUTL) volume that is, or will become associated with an Enhanced Reader (ER) Auxiliary session. However, the corresponding ER Primary session is not active. If the Utility volume for the Primary session is suspended, issue XADDPAIR for it, then reissue an XADDPAIR for the Auxiliary session Utility volume. |
4561 | An XADDPAIR or XSET command failed for an XRC
session with both enhanced multi reader and MzGM-IR active. A problem
was encountered with configuring the SWAP volume. The NumberReaderTasks
parameter for the storage control session name is nonzero and requires
alias devices for the swap device utility volumes. Insufficient alias
devices are configured for the swap utility device to meet the number
required by the NumberReaderTasks parameter. This problem might be
corrected using one of the following methods:
|
4562 | The XADDPAIR command specified a new swap volume that is in the same SSID as another swap volume that is already in the XRC session. That existing swap volume is associated with a different primary SSID other than the primary volume specified on the XADDPAIR command. The XADDPAIR command is unsuccessful. A swap SSID can only be associated with one primary SSID. |
4563 | The XSWAP SUSSWAP command found a control unit session that was already suspended. This is not usually an error and is only reported for possible problem determination if another error occurs subsequently. |
4564 | XADDPAIR processing for a utility device was unable to access the SWAP utility device, and needed to change the controller session configuration. This might be because of the re-establishment of a session that had been terminated, or changing the enhanced multi reader configuration. Reprocess the XADDPAIR command after the SWAP utility device is available. |
4565 | An XSWAP SUSSWAP command has been issued for
a session in MODE(HYPER-PPRC,) but the System Data Mover was unable
to locate the storage control session associated with the SWAP. This
can occur if the session was previously terminated with a F ANTAS000,TERMSESS
command. Ensure that the SWAP utility devices that are associated with the SWAP SSID are ONLINE to the SDM system. If not, vary the devices online and reissue the XSWAP SUSSWAP command. If a large number of SSIDs are associated with this error, and the SWAP sessions are verified to be terminated, correct the problem by issuing the XSUSPEND TIMEOUT, XSTART MODE(NORMAL), and XADD SUSPENDED commands, and waiting for message ANTX8170W or ANTX8169I for all of the SWAP SSIDs or waiting for message ANTA8124I. Then issue the XSUSPEND TIMEOUT and XSTART MODE(HYPER-PPRC) commands followed by an XADDPAIR for the SWAP volume triplets. To recover from a small number of SSIDs with this error, each associated Utility volume must be removed using XDELPAIR, and then re-added with XADDPAIR. If the Utility volume is associated with an Enhanced Reader primary storage control session or Single Reader session, all associated volume pairs must first be removed using XDELPAIR, then re-added after the Utility volume is re-established. |
4571 | An XADDPAIR for a non-xrcutl volume was attempted and there was a primary utility defined that does not have an associated swap utility defined. To correct this error, use GDPS to issue an XADDPAIR command to XRCUTL volume(s) for the specified (or default) scsession. You can also XDELPAIR the primary utility if there is no matching swap utility or fewer utilities are required. When successful, reissue XADDPAIR for the non-xrcutl volume. |
4573 | Indicates that the specified device is in the configuration but is not connected. |
4600 | This is an internal SDM return code. |
4601 | An error occurred while attempting to allocate a 64-bit common area for the system data mover device table. The reason code displayed in this message is the IARV64 return code. See the IARV64 return codes in the z/OS MVS Programming: Authorized Assembler Services Reference EDT-IXG. |
4602 - 4603 | This is an internal SDM return code. |
4604 | An incompatible change has been made to the XRC device table that requires an IPL to fix. |
4605 - 4616 | This is an internal SDM return code. |
4622 | This is an internal SDM return code. |
4623 | FIXDTABLE was unable to attain the system enqueue required to prevent dynamic I/O configuration changes. Wait until dynamic I/O configuration changes are completed, and reissue FIXDTABLE. If there are no concurrent dynamic I/O configuration changes, contact IBM support for help. |
4624 | FIXDTABLE was unable to attain the system enqueue required. Wait until XSTART processing has completed, and then reissue FIXDTABLE. If there are no XSTARTs in process of coming up, contact IBM support for help. |
4625 | This is an internal SDM return code. |
6000 (X'1770') | Insufficient storage is available in ANTMAIN address space. This is probably because an installation exit function has limited the storage below the minimum required for the ANTMAIN functions. See z/OS DFSMS Advanced Copy Services for the ANTMAIN storage requirements, and ensure that the installation exit allows the required storage to be allocated. |
6001, 6002 (X'1771' to X'1772') | These are internal SDM errors. |
6003 (X'1773') | IXFP is not at the correct level for DFSMSdss or SDM support of the Snapshot function. Install the required level of IXFP maintenance. After maintenance is installed, issue CANCEL ANTMAIN when no Snapshot or concurrent copy jobs are running. |
6004 (X'1774') | A VCC operation has
been requested for a device that does not support either FlashCopy or SnapShot, or the available
working space data sets (WSDSs) are on the wrong device type for the
data being processed. This return code also appears when the available WSDSs are full and the remaining cataloged WSDSs are on volumes that are offline. All volumes that contain working space data sets must be varied online. |
6005 to 6007 (X'1775' to X'1777') | These are internal SDM errors. |
6008 (X'1778') | An error has occurred when communicating with IXFP. This could be an internal SDM error, an internal IXFP error, or a mismatch between the service levels of SDM and IXFP. The reason code associated with this error is found in SDM reason codes from IXFP errors. |
6009, 6010 (X'1779' to X'177A') | Insufficient storage is available in ANTMAIN address space. This is probably because an installation exit function has limited the storage below the minimum required for the ANTMAIN functions. See z/OS DFSMS Advanced Copy Services for the ANTMAIN storage requirements, and ensure that the installation exit allows the required storage to be allocated. |
6011 to 6017 (X'177B' to X'1781') | These are internal SDM errors. |
6018 (X'1782') | For an XRC session, an OPEN error occurred while obtaining the format-1 DSCB for the journal, control, or state data set because of an error reading the VTOC for the volume. The data set can be cataloged but either does not exist on the volume indicated by the catalog, or an I/O error occurred while attempting to read the VTOC. This error can also appear if the control dataset is allocated in the Extended Address Space of an Extended Address Volume (EAV). Determine why the error has occurred, correct the error, and reissue the XSTART, XRECOVER, or XADVANCE command to restart the session. For a Snapshot function, an error occurred while obtaining format-1 DSCB for a working space data set. |
6019 (X'1783') | An error has occurred while loading module ANTUGOAD. Verify that the module exits in SYS1.LINKLIB and that it is available to the data mover. |
6020 (X'1784') | An error has occurred while loading module ANTUGOFR. Verify that the module exits in SYS1.LINKLIB and that it is available to the data mover. |
6021 (X'1785') | For an XRC session, an OPEN error occurred while obtaining the format-3 DSCB for the journal, control, or state data set because of an error reading the VTOC for the volume. The data set can be cataloged but either does not exist on the volume indicated by the catalog, or an I/O error occurred while XRC attempted to read the VTOC. Determine why the error has occurred, correct the error, and reissue the XSTART, XRECOVER, or XADVANCE command to restart the session. For a Snapshot function, an error occurred while obtaining format-3 DSCB for a working space data set. |
6022 (X'1786') | An error has occurred while obtaining format-4 DSCB for a working space data set. The reason code is set to the return code from the OBTAIN macro. |
6023 to 6032 (X'1787' to X'1790') | These are internal SDM errors. |
6033 (X'1791') | A Snapshot operation failed. See SDM reason codes from IXFP errors for an explanation of the associated reason code. This can be a DFSMSdss internal error, an SDM internal error, an IXFP internal error, or a configuration error. |
6034 (X'1792') | This is an internal SDM error. |
6035 (X'1793') | A QUERY DEVICE operation failed. The reason code is described in SDM reason codes from IXFP errors. This can be a DFSMSdss internal error, an SDM internal error, an IXFP internal error, or a configuration error. |
6036 to 6143 (X'1794' to X'17FF') | These are internal SDM errors. |
6144 (X'1800') | All working space data set space on the RVA subsystem that contains the source data set is currently in use by other Snapshot requests. Allocate one or more additional working space data sets on the RVA subsystem according to the allocation guidelines for working space data sets and then resubmit the failing job. |
6145 (X'1801') | Insufficient working space data set space was available on the RVA subsystem that contains the source data set to satisfy the Snapshot request. Either resubmit the failing job after another DFSMSdss job using concurrent copy on the source RVA releases the working space data set space, or increase the working space data set space, and resubmit the failing job. |
6146 (X'1802') | The Snapshot operation failed because not enough working space was available to the ANTMAIN system data mover address space. The space was not available because of an allocation or ENQUEUE conflict with the working space data sets (WSDS) within SYS1.ANTMAIN.Ssystem.SNAPnnnn. This problem can occur when a WSDS is allocated during the time that the DFSMSdss job is attempting to use it. To prevent this condition, preallocate the WSDS or allocate it during a different job. |
6147 (X'1803') | There is no working space data set cataloged in this system. Follow the procedure in z/OS DFSMSdss Storage Administration to determine what problem or problems exist when accessing the working space data set. Repair or reallocate the working space data set and resubmit the failing job. |
6148 (X'1804') | No usable working space data set was found associated with the system. No working space data set was found on the RVA subsystem that matches the source data set attributes. The working space data set must be on the same partition, or be on a device type which is write-enabled and able to process Snapshot functions. Follow the procedure in z/OS DFSMSdss Storage Administration to properly allocate a working space data set, then resubmit the failing job. |
6149 (X'1805') | A virtual concurrent copy request has timed out when attempting to find available tracks in working space data sets. The problem can occur if virtual concurrent copy is used to process a master catalog or a user catalog containing working space data sets. If this is the cause and the data sets reside on storage subsystems that support cache-based concurrent copy, modify the backup copy technique for the catalogs to specify CACHEPREFERRED or CACHEREQUIRED. Otherwise, search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM Support Center, after first obtaining a dump of the ANTMAIN address space, by issuing system command F ANTMAIN,DUMPTRC. |
6150 to 6199 (X'1806' to X'1837') | These are internal errors. |
6200, 6201 | An error has occurred while loading FlashCopy support. Verify that the FlashCopy support is installed on the software system. If an I/O error has occurred when loading the function from SYS1.LINKLIB, correct the error before you retry the function. |
6202 | An error has occurred while verifying the device address. Ensure that the device address is properly specified, and then reissue the function. |
6207 | There is an internal error. |
6208 | There is an internal error. |
6209 | When attempting to validate usability of a working space data set, a catalog entry was found, but the volume that is indicated as containing the data set is not available on the system. If the catalog entry is correct, make the volume available. If the catalog entry is not correct, delete it to prevent SDM from attempting to use it and repeatedly reporting this error. |
6210 | A non-VSAM working space data set was found to not meet the allocation requirements described in the Advanced Copy Services reference section on allocating WSDS. Correct the data set allocation and refresh the WSDS list through F ANTMAIN,REFRESHWS. |
6211 | A VSAM working space data set was found to not meet the allocation requirements described in the Advanced Copy Services reference section on allocating WSDS. Correct the data set allocation and refresh the WSDS list via through ANTMAIN,REFRESHWS. |
6212 | An error was encountered obtaining a SYSDSN enqueue on the working space data set. |
6213 | An error was encountered allocating the device containing a WSDS. |
6214 | The WSDS has an associated user label. Correct the data set allocation to meet the allocation requirements described in the Advanced Copy Services reference section on allocating WSDS and refresh the WSDS list via through ANTMAIN,REFRESHWS. |
6215 | The WSDS has no space allocated to it. Correct the data set allocation to meet the allocation requirements described in the Advanced Copy Services reference section on allocating WSDS and refresh the WSDS list via through ANTMAIN,REFRESHWS. |
6216 | There is an internal error. |
6217 | There is an internal error. |
6218 | There is an internal error. |
6219 | There is an internal error. |
6220 | Device information could not be determined for the VOLSER specified on input to the COMPATIBLE parameter of the LISTWS request. If the VOLSER is correct, this might be caused by the device being offline. Either correct the VOLSER or vary the device online, and reissue the command. |
6300 to 6316 (X'189C' to X'18AC') | These are SDM internal errors related to pause/release processing. |
6309 (X'18A5') | The SDM pause element token table is full. This condition can arise from a large number of simultaneous invocations of ANTRQST, concurrent copy, or DFSMSdss processing of fast replication or extended-format data sets. To clear the condition, cancel the ANTMAIN address space, which should automatically restart. Note that any currently active requests are terminated. See z/OS DFSMS Advanced Copy Services for instructions on modifying PET table size. |
6315 (X'18AB') | An SDM pause element was released because of the reinitialization of the pause element token table, or because of the ANTMAIN address space termination and restart. |
6400 (X'1900') | Concurrent copy processing encountered
the situation where an auxiliary storage percentage was exceeded.
If this return code is part of the diagnostic information for message
ADR735W, concurrent copy will not be used to copy the data set. If
this return code is part of the diagnostic information for message
ADR736W, the concurrent copy job is terminated. This return code is issued when the number of concurrent copy jobs exceeds the auxiliary storage percentage in the system in which the system data mover (SDM) is running. |
6401 (X'1901') | A critical SQA shortage exists. |
6402 (X'1902') | CSA storage could not be obtained. |
7000 to 7999 | These are return codes from the System Data Mover Application Programming Interface invoked by the ANTRQST macro. For a detailed description of these return codes, see Table 1. |
9000 to 9012 | These are internal errors that are
associated with an abend dump generated by the data mover. The error
can be the result of an error detected by one of the system functions
used by the data mover. In this case, there can be an associated system
message describing the reason that the system function detected the
error. Correcting the error will resolve this type of problem. If
there is no associated system message, the problem can be due to an
internal data mover error. For these return codes, cancel ANTAS000 and ANTASnnn and restart the session. When you contact IBM for assistance, provide associated SYS1.LOGREC information in addition to the data requested in the beginning of this section. |
9013 | If this is issued as a reason code associated with a 4010 return code, the control data set has not been properly defined with the correct record format or DSORG. Correct the error and reissue the XSTART command. |
9014 | XRC has encountered an error. The reason code for the error is specified in register 15. Many of these errors can indicate an LIC failure. Diagnostic information for this abend is available in SYS1.LOGREC, a dump initiated by the data mover (if useful), and an LIC state save (if SCTRAP is ON and the storage control supports the state save function). When contacting IBM for assistance, provide this information in addition to the data requested at the beginning of this section. |
9017 to 9059 | These are internal errors. |
9060 | This is an internal use return code
associated with the X'DC2' system abend code for an IARV64
request. See abend code X'DC2' in z/OS MVS System Codes for
an explanation and programmer response. Note that the reason code
associated with this error is theX'DC2' reason code. Search
problem reporting databases for a fix for the problem. If no fix exists,
contact the IBM Support Center
and provide the following information:
|
9061 to 9399 | These are internal errors. |
9400 | This is an internal error. First
issue MODIFY ANTASnnn,RESTART. If this fails, cancel
ANTAS000 and ANTASnnn and restart the session. When you contact IBM for assistance, provide the SVC dump taken at the time of the abend, and any associated SYS1.LOGREC information in addition to the data requested in the beginning of this section. |
9401 to 9899 | These are internal errors. |
9900 | This is an internal error. First
issue MODIFY ANTASnnn,RESTART. If this fails, cancel
ANTAS000 and ANTASnnn and restart the session. When you contact IBM for assistance, provide the SVC dump taken at the time of the abend, and any associated SYS1.LOGREC information in addition to the data requested in the beginning of this section. |
9901 to 9999 | These are internal errors. |