System data mover return and reason codes

2 (X'02')

A request to establish a dual copy session is rejected because the secondary device has a concurrent copy session active.

3 (X'03')

A request to establish a concurrent copy session has failed because the device is in track emulation mode.

4 (X'04')

The requested control unit does not have any concurrent copy sessions available. The number of concurrent copy sessions is model dependent information that can be obtained from the appropriate controller information.

5 (X'05')

This is an internal DFSMSdss/DFSMSdfp error that should be reported to your IBM service center.

6 (X'06')

The concurrent copy session is not active on the device. This be caused by the following:

• The session has been terminated by the storage controller. This be a normal condition if storage controller cache thresholds or session limits have been exceeded.
• The session has been terminated by the System Data Mover in response to an error condition. Look for entries in LOGREC with the string 'CC SESSION TERMINATION'. These records include a termination reason code following the text 'SDM SERVL RSN'.
• The session identifier is invalid. This is an internal DFSMSdss/DFSMSdfp error that should be reported to your IBM service center.

7 (X'07')

This is an internal DFSMSdss/DFSMSdfp error that should be reported to your IBM service center.

8 (X'08')

The concurrent copy session is not active. This be because:

• A concurrent copy session was never started.
• The session have been terminated. This be a normal condition if concurrent copy jobs have been canceled.
• The System Data Mover terminated and was restarted. On termination all existing sessions are terminated.

9 (X'09')

This is an internal DFSMSdss/DFSMSdfp error that should be reported to your IBM service center.

10 (X'0A')

The system data mover has been terminated (by a Cancel ANTMAIN) and has restarted. Active sessions at the time of the cancel receive this error.

11 (X'0B')

The selected device has become unavailable to the system. Check for IOS messages to determine the state of the device.

12 (X'0C')

This is an internal DFSMSdss/DFSMSdfp error that should be reported to your IBM service center.

13 (X'0D')

The device address is not associated with a concurrent copy session. This can occur if the concurrent copy session has been canceled or the device has been removed from the session.

14 (X'0E')

The storage controller does not have the concurrent copy feature installed.

16 (X'10')

The storage controller is not capable of supporting concurrent copy.

18 (X'12')

This is an internal DFSMSdss/DFSMSdfp error that should be reported to your IBM service center.

20 (X'14')

Not all tracks have been processed. This might be caused by one of the following reasons:

• The System Data Mover encountered a critical SQA shortage or pageable storage shortage and stopped retrieving tracks from the storage controller.
• An error occurred in the storage controller or in the DFSMSdss/DFSMSdfp software so that the System Data Mover was unable to retrieve one or more changed tracks within the allotted time. Search problem reporting databases for a fix for the problem. If no fix exists, report the error to your IBM Service Center. If a non-IBM storage controller is involved, also contact the manufacturer for problem determination assistance.

24 (X'18')

SDM retrieved a track from the control unit for a track that had been updated (a data check indication was received). All data up to the point of failure was transferred. The sense data field for the failing track is zeroes.

26 (X'1A')

SDM retrieved a track from the control unit for a track that had been updated (an invalid track format indication was received). All data up to the point of failure was transferred. The sense data field for the failing track is zeroes.

30 (X'1E')

The selected device does not support Extended Count Key Data (ECKD™) architecture (Define Extent and Locate Record channel program commands). The System Data Mover does not support this device.

32 (X'20')

A Concurrent Copy 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.

1 (X'01')

This is an internal DFSMSdss/DFSMSdfp error that should be reported to your IBM service center.

2 (X'02')

Invalid function requested.

3 (X'03')

A translation exception occurred building a channel program

4 (X'04')

Real storage error.

8 (X'08')

Data space error.

20 (X'14')

The System Data Mover is not currently available to process requests. Resubmit the failing request.

cc

is the op code of the CCW that had the problem.

mm

is byte 9 of the sense data returned on a command reject (format 0 message F) on the op code cc specified.

rr

is the return code from AOM.

ss

is the reason code from AOM.

tttt

is the request type.

rrrr

is the return code from the Resource Manager.

tttt

is the request type:

AD

ADD

AP

ADDPASN

DE

DELETE

EX

EXTRACT

SE

SEARCH

EH

EXTRACTH

rrrr

is the return code from ALESERV.

4 (X'04')

A command reject was received from the control unit for the requested operation. The specified concurrent copy session has been terminated because of 128 or more CC track images (updated tracks) remaining in the Control Unit Cache for longer than two (2) minutes without being moved to the host storage.

8 (X'08')

A command reject was received from the control unit for the requested operation. The specified concurrent copy session has been terminated because of the combined CC usage of cache exceeding 60% of the available cache for the control unit.

12 (X'0C')

A command reject was received from the control unit for the requested operation. The concurrent copy session has been terminated because of the control unit cache being reinitialized or terminated.

16X'10'

A command reject was received from the control unit for the requested operation. The Concurrent Copy cache information indicated an error exists on the track.

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.

For an XRC session, an 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 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 data set is allocated with extended attribute data set control blocks (format 8 and 9 DSCBs). 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.

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 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.

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. The reason code that accompanies this return code indicates the concurrent copy value provided by customers to determine the auxiliary storage percentage against which SDM is to measure concurrent copy auxiliary storage usage.

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.

KEYWORDS: CONCOPY/K

A FlashCopy operation failed because of an ESS detected problem. The following diagnostic information contains error reason codes generated by the ESS in response to an internal SDM request. These reason codes are shown and generally displayed in HEX format.

(X'0804fnrs')

• f indicates the first digit (Format) of sense byte 7
• n indicates the second digit (Message) of sense byte 7
• rs represents the reason code from byte 8 of the sense information

If you receive a fnrs code other than what is displayed in the following list, contact the IBM ESS Hardware Support structure for further assistance.

(X'0000')

No sense information is available. The ESS was unable to complete an establish request because of the request being canceled by system Missing Interrupt Handler (MIH) processing. An AOMSSDS record is logged in LOGREC for the timeout condition.

(X'0900')

The ESS was undergoing internal recovery procedures at the time the command was received. Retry the operation.

(X'0F82')

The number of resources (caches) is insufficient for establishing the Flashcopy relationships you need.

(X'0F84')

The FlashCopy volumes specified are not the same size and format.

(X'0F85')

FlashCopy target device in conflict with Copy Services status (XRC or PPRC).

(X'0F86')

FlashCopy establish failed because the required license feature is not installed or enabled on the storage subsystem.

(X'0F87')

FlashCopy target in use by another copy operation.

(X'0F89')

FlashCopy establish specified a preserve mirror operation and there is a condition that prevents the operation from being successful. The ADR message that was issued includes a modifier that explains this condition:

X'01'

The specified source volume is not a PPRC primary.

X'02'

The secondary volume to the specified source volume and the secondary volume to the specified target volume are not in the same storage facility image (SFI).

X'03'

The PPRC relationship for the specified source volume is not full duplex.

X'04'

The PPRC relationship for the specified target volume is not full duplex.

X'05'

The secondary control unit does not have the necessary microcode installed.

X'06'

The inband flashcopy command was not successful at the secondary control unit because a preserve mirror relationship already existed.

X'07'

An error was detected sending a command to the secondary control unit.

X'08'

An attempt to take an increment using preserve mirror and the existing relationship is not a preserve mirror relation.

X'0A'

An attempt to take an incremental FlashCopy using Preserve Mirror operation, but the secondary control unit does not have the microcode installed that supports incremental FlashCopy Version 2.

A FlashCopy operation failed because of an ESS detected problem. The following diagnostic information contains error reason codes generated by the ESS in response to an internal SDM request. These reason codes are shown and generally displayed in HEX format.

(X'0F92')

FlashCopy establish or withdraw specified a target that has other operations in progress that prevent the command from succeeding. The ADR message that was issued includes a modifier that explains this condition:

X'01'

The specified target has a PPRC cascading Failover/Failback operation in progress.

X'02'

The specified target volume’s PPRC relationship has incremental resync change recording active.

(X'0F9C')

FlashCopy establish resource shortage.

(X'0F9D')

FlashCopy establish request would cause a device to have more than the maximum number of FlashCopy relationships.

(X'0FA6')

FlashCopy establish request would cause a source track to have more than the maximum number of targets.

(X'0FA7')

FlashCopy establish source track is an active target track. This is likely because of a conflict with an existing FlashCopy relationship.

(X'0FA8')

FlashCopy withdraw request would cause a device to have more than the maximum number of FlashCopy relationships.

(X'0FAB')

FlashCopy V1 establish is requested on a device with active FlashCopy V2 relationships.

(X'0FAE')

FlashCopy establish target track is an active target track. This be because of a conflict with an existing FlashCopy relationship, or because of the ESS completing an establish request after system Missing Interrupt Handler (MIH) processing is initiated.

(X'0FAF')

FlashCopy establish target track is an active source track. This is likely because of a conflict with an existing FlashCopy relationship. This is a normal condition during DFSMSdss DEFRAG processing.

(X'0FB4')

FlashCopy establish request would reverse the direction of the existing FlashCopy relation. The direction cannot be reversed at this time. This be due to previous physical background copy still in progress.

(X'0FB7')

FlashCopy establish request VM minidisk mode conflict.

(X'0FBB')

FlashCopy withdraw using the DDSW option was requested for a volume containing a full-volume source FlashCopy relationship. The withdraw will be performed without DDSW processing.

(X'F005')

The ESS was undergoing internal recovery procedures at the time the command was received. Retry the operation.