SLS messages (including SLS6684I, SLS5079E, SLS5080E, and SLS6751I) contain ECAM completion codes (CC) and return codes (RC). The following table describes these codes:
SLS messages (including SLS6684I, SLS5079E, SLS5080E, and SLS6751I) contain ECAM completion codes (CC) and return codes (RC). The following table describes these codes:
Table 7-1 ECAM Completion Codes, Return Codes, and Descriptions
| Completion Code | Return Code | Description |
|---|---|---|
|
00 |
00 |
Successful completion |
|
00 |
02 |
Request accepted for asynchronous process |
|
00 |
100 |
Successful, end of inventory |
|
00 |
101 |
Successful, Request in process |
|
00 |
103 |
Successful, completed with data loss. Warning: Could be a bad recall from an MVC! |
|
02 |
01 |
No match found for key parameter |
|
03 |
00 |
One or more errors in parameters |
|
03 |
03 |
Vector field in error |
|
03 |
08 |
Invalid check sum |
|
03 |
09 |
Duplicate value in vector field |
|
04 |
02 |
Required parameter count incorrect |
|
04 |
03 |
No alter values supplied |
|
04 |
04 |
Key parameter count incorrect |
|
05 |
106 |
RTD is inaccessible due to IUP fencing |
|
05 |
107 |
RTD request was cancelled |
|
05 |
108 |
RTD reported error. For user response, see "CC5 RC108." |
|
05 |
109 |
RTD communications error. For user response, see "CC5 RC109." |
|
05 |
111 |
RTC VOLSER does not match RTCID. For user response, see "CC5 RC111." |
|
05 |
112 |
RTC request timeout. For user response, see"CC5 RC112." |
|
05 |
113 |
No RTC mounted. For user response, see "CC5 RC113." |
|
05 |
114 |
RTC is not an MVC. For user response, see "CC5 RC114." |
|
05 |
115 |
End-of-Tape encountered. For user response, see "CC5 RC115." |
|
05 |
116 |
Bad MVC position was specified. For user response, see "CC5 RC116." |
|
05 |
117 |
RTC is read only. For user response, see "CC5 RC117." |
|
05 |
118 |
Data check on lbl rec - VTV not determined. For user response, see "CC5 RC118." |
|
05 |
150 |
Synchronous Replicate failed due to a timeout |
|
05 |
158 |
Actual block ID does not match expected Block ID |
|
05 |
167 |
Blocks transferred (bytecnt) does not match mediasiz. For user response, see "CC5 RC167." |
|
05 |
169 |
Multiple paths to an RTD report FCSN mismatch. |
|
05 |
172 |
Bad data block detected by the primary VTSS |
|
05 |
173 |
Bad data block detected by the secondary VTSS |
|
05 |
174 |
Enhanced Synchronous Replication MIH value exceeded |
|
07 |
00 |
This parameter conflicts with another parameter. |
|
08 |
19 or 119 |
VTV inventory full |
|
08 |
120 |
Out of Back-end capacity |
|
08 |
180 |
Replication failed because of insufficient resource on the primary VTSS. |
|
08 |
181 |
Replication failed because of insufficient resource on the secondary VTSS. |
|
09 |
00 |
Prerequisite value not equal to value in subsystem |
|
09 |
30 |
A Cache Reinit has interrupted the operation and caused it to fail. |
|
09 |
121 |
VTV is busy |
|
09 |
122 |
VTV exists - VTV is in buffer but not in CDS. Run VTSS audit to correct. |
|
09 |
123 |
VTV does not exist |
|
09 |
124 |
VTD is busy |
|
09 |
125 |
VTV inventory is not available. |
|
09 |
126 |
VTV is corrupt |
|
09 |
127 |
RTD is busy. For user response, see "CC9 RC127." |
|
09 |
128 |
RTD, CLINK, RLINK is offline or inoperable. RLINK is offline_fail, offline_pending or online_pending. For user response, see "CC9 RC128." |
|
09 |
129 |
RTD, CLINK, RLINK is unconfigured. For user response, see "CC9 RC129." |
|
09 |
131 |
No request present for RTD. VTCS is doing cleanup after a VTSS warm boot. Informational only. |
|
09 |
132 |
Interface is already assigned to another RTD. For user response, see "CC9 RC132." |
|
09 |
133 |
Unable to service request - interface is configured in control unit mode. For user response, see "CC9 RC133." |
|
09 |
135 |
RTD is online, configuration cannot be changed. For user response, see "CC9 RC135." |
|
09 |
139 |
VTV is being recovered by the VTSS |
|
09 |
140 |
Reserved for use by VTCS, not generated by the VTSS. This reason code indicates that the VTCS detected an Interface Control Check (IFCC) during the ECAM-T request. Warm start recovery for the specific request should be performed. |
|
09 |
141 |
RTD port is connected to a Secondary VTSS and not a Real Tape Drive |
|
09 |
142 |
RTD port is not attached to a Clustered VTSS |
|
09 |
143 |
Specified subsystem name does not match the actual subsystem name of the secondary VTSS |
|
09 |
144 |
RTD "Buddy" is Busy. The RTD Buddy is the RTD that shares the same link. The return is only valid for VSM4. For User Response, see "CC9 RC144." |
|
09 |
145 |
ECART is not supported. |
|
09 |
146 |
No logical path established to the VDID |
|
09 |
147 |
No support for 62K page VTVs |
|
09 |
148 |
No support for 2GB or 4GB virtual cartridge type |
|
09 |
149 |
Request is not supported on an ESCON interface |
|
09 |
150 |
A Synchronous Replicate failed due to a timeout. |
|
09 |
151 |
CLINK VDID is already in use by another CLINK |
|
09 |
152 |
CLINK VDID does not match already assigned VDID |
|
09 |
153 |
MVC Lost Position |
|
09 |
154 |
Stacked Migrate queue is full |
|
09 |
155 |
Migrate, Duplicate VTVID |
|
09 |
157 |
ICE cards only support RTD paths 0 and 1 |
|
09 |
159 |
RTD does not support ALP |
|
09 |
160 |
T10KC drive does not support request |
|
09 |
161 |
RTD is ALP |
|
09 |
162 |
TTFB VTD is already mounted |
|
09 |
163 |
Invalid parameter for T10KB drive type |
|
09 |
164 |
Invalid parameter for T10KC drive type |
|
09 |
165 |
RTD Name not defined on VSM6 |
|
09 |
166 |
VTD is active |
|
09 |
168 |
RTD does not support the verify option |
|
09 |
170 |
The VTSS is performing an internal recovery action and should be considered unavailable. This recovery may take a long time. |
|
09 |
171 |
Secondary VTSS does not support the requested parameter or option |
|
09 |
175 |
RLINK is busy |
|
09 |
176 |
32 GB Virtual Cartridge Type not supported |
|
09 |
177 |
VTVID does not match |
|
09 |
178 |
Internal logic error |
|
09 |
179 |
VDID specifies a VTD greater than supported by the VTSS (VTDMAX). |
|
09 |
182 |
VTV cartridge type is not supported by 3490E VTD. |
|
09 |
183 |
VCART virtual cartridge type is not supported. |
|
10 |
00 |
Prerequisite value not equal to value in Subsystem |
|
97 |
137 |
VTV has an error. Waning: Could be a bad recall from an MVC with a Data Check |
|
98 |
01 |
Undefined message |
|
98 |
02 |
Invalid self-defining information |
|
98 |
03 |
Unexpected parameter for this message |
|
98 |
04 |
Invalid message type in message header |
|
98 |
05 |
Reserved field nonzero in Request Message header |
|
98 |
06 |
Duplicate parameter in message |
|
98 |
156 |
VDID parameter is required |
|
99 |
03 |
Unable to service request - Support Facility not functional |
|
254 |
N/A |
VTCS to VTSS communicate failure. No VTDs available for VTCS to send ECAM-T messages to. Action: Verify VTSS is online to the host, subsystem name is OK, bounce HSC. |
|
255 |
N/A |
VTCS to VTSS communication failure. Possible causes:
Action: Verify everything is OK and bounce HSC. |
|
255 |
12 |
The EXCP to the VTD reported in message SLS6698I failed with an error other than an Interface Control Check. |
|
255 |
16 |
The EXCP to the VTD reported in message SLS6698I failed with an Interface Control Check. |
|
255 |
20 |
VTCS was unable to issue an EXCP to the VTD reported in message SLS6698I because there is no path to the device. |
|
255 |
24 |
VTCS was unable to issue an EXCP to the VTD reported in message SLS6698I because the UCBLOCK macro returned a non-zero return code. |
|
255 |
28 |
VTCS was unable to issue an EXCP to the VTD reported in message SLS6698I because the IOSCAPU macro returned a non-zero return code. |
RTD DDDDDD ON VTSS XXXXXXXX RETURNED ECAM ERROR CC=5 RC=108
Explanation: An attempt was made to enter a command (CCCCCCCC) that was not a valid subsystem command.
System Action: The VTCS software interprets the ERPA code returned to determine the appropriate system actions. The following message appears after message SLS6684I:
SLS6625E RTD DDDDDD REPORTED RRRRRRRR:XXXXXXXXXX
where RRRRRRRR is the message text of the problem, for example:
WRITE DATA CHECK
PATH EQU CHK
DRIVE EQU CHK
and XXXXXXXXXX is the sense bytes containing ERPA code in byte 3. From byte 3, VTCS determines appropriate actions to take, for example:
Initiating a swap of the MVC to another RTD
Putting the RTD into Maintenance Mode.
If a swap was initiated, the following message appears after message SLS6625E indicating a swap was issued and identifying the MVC being swapped:
SLS6605I INITIATING SWAP OF MVC VVVVVV FROM RTD DDDDDD
User Response:
If the swap was successful, do not contact StorageTek Hardware Support.
If the swap failed and the following messages appear, contact StorageTek Software Support and provide the contents of message SLS6625E:
SLS6628E RTD DDDDDD ON VTSS XXXXXXXX FAILED TO MOUNT MVC VVVVVV SLS6629E RTD DDDDDD ON VTSS XXXXXXXX FAILED TO DISMOUNT MVC VVVVVV SLS6662E RTD DDDDDD PUT IN MAINTENANCE MODE BECAUSE OF ERROR
If a swap was not initiated and the following messages appear directly after message SLS6625E, contact StorageTek Hardware Support and send them the contents of the SLS6625E message:
SLS6628E RTD DDDDDD ON VTSS XXXXXXXX FAILED TO MOUNT MVC VVVVVV SLS6629E RTD DDDDDD ON VTSS XXXXXXXX FAILED TO DISMOUNT MVC VVVVVV SLS6662E RTD DDDDDD PUT IN MAINTENANCE MODE BECAUSE OF ERROR
In addition, have your site's support services do the following:
Run an MVC report to check the status of the MVC.
If the status shows either B (broken) or D (data check), or both, drain the MVC with eject.
WARNING:
If the error occurred on a VOLSAFE (WORM) tape, do not drain the MVC without the recommendation of Oracle/StorageTek Support. Once a WORM tape is drained, it can no longer be used for migration and must be replaced.
After all VTVs are drained from the MVC, examine the cartridge with a tape analysis utility to determine whether there is a problem with the cartridge or not.
If the cartridge is to be returned to service as an MVC, issue a second MVCDRAIN without eject.
WARNING:
If the error occurred on a VOLSAFE (WORM) tape, do not drain the MVC without the recommendation of Oracle/StorageTek Support. Once a WORM tape is drained, it can no longer be used for migration and must be replaced.
If the drain process fails to drain all VTVs from the MVC and if a duplexed copy of those VTVs does not exist, the cartridge should be sent to StorageTek Hardware Support for recovery.
RTD DDDDDD ON VTSS XXXXXXXX RETURNED ECAM ERROR CC=5 RC=109
Explanation: There is a communications error between the VTSS and the RTD. Possible cause of this condition could be that an MVC is mounted on an RTD, and the RTD drops ready due to a drive or cable problem.
System Action: The request fails.
User Response: Query the MVC to display it in SYSLOG for possible diagnostic purposes and then vary the RTD offline using the following commands:
.VT Q MVC(volser)
to determine the status of MVC
.VT Q RTD(rtd-id)
to see if MVC is mounted on RTD
If the previous display indicates the MVC is not mounted on an RTD, then vary the RTD offline by issuing the following command:
.VT V RTD (rtd-id) OFFline
If the MVC is mounted on the RTD, vary the RTD online first and then offline to unload the MVC from the RTD. Issue the following commands:
.VT V RTD (rtd-id) ONline
.VT V RTD (rtd-id) OFFline
Contact StorageTek Hardware Support and supply the RTD address and MVC.
RTD DDDDDD ON VTSS XXXXXXXX RETURNED ECAM ERROR CC=5 RC=111
Explanation: The RTD is reporting a problem with the drive or there is a problem with the MVC currently mounted on it.
System Action: The mount request fails.
User Response: Do the following:
Query the RTD with the following command and note the MVC volser:
.VT Q RTD (rtd-id)
View the RTD and verify that the external label matches the expected volser of the MVC using the HSC View command:
(HSC prefix) VIEW DR ADDRESS(rtd-id)
If the external label matches the MVC volser, an RTD cabling problem may exist.
Check the internal label to ensure it matches the MVC volser.
If it does match, contact StorageTek Hardware Support and supply the RTD address and MVC volser from the Query command.
If the external label does not match, eject the cartridge and analyze it.
RTD DDDDDD ON VTSS XXXXXXXX RETURNED ECAM ERROR CC=5 RC=112
Explanation: The RTD did not mount the MVC within an internal VTCS timer of 15 minutes and as a result there is a cartridge request timeout. This timeout could indicate one of the following conditions or some other reason for the timeout:
An MVC is in use on another RTD.
An outstanding message is on the console.
A PTP is blocked due to an LSM in path offline.
A drive targeting the problem or a bad cable may exist in an LSM.
An LSM door is open.
The HSC COMMPATH is CDS rather than LMU or VTAM.
The request is re-driven.
User Response: A service call is usually not necessary for a timeout if the mount does occur and there are no other reported errors. Have your site's support services investigate possible problem conditions such as an LMU error(s) or mount failure by reviewing the SYSLOGs to determine whether you should contact StorageTek Hardware Support.
RTD DDDDDD ON VTSS XXXXXXXX RETURNED ECAM ERROR CC=5 RC=113
Explanation: No real tape cartridge was mounted. When the command was initially sent to the RTD, the RTD was online and ready; but before the mount could be satisfied, the RTD drive dropped ready.
System Action: The request fails.
User Response: Eject the MVC cartridge and examine it for any visual defect that may be preventing it from mounting. If you find a problem with the physical cartridge, have your site's support services examine it for further diagnosis, or contact StorageTek Hardware Support.
RTD DDDDDD ON VTSS XXXXXXXX RETURNED ECAM ERROR CC=5 RC=114
Explanation: The real tape cartridge is not an MVC, which could indicate that the MVC has somehow been erroneously re-initialized by another job. If the mount resulted from a migration request, a new volume will be selected and the request will be re-tried. If the mount resulted from a recall request and the MVC had been previously used and known to be valid, the request will be re-tried from another copy of the VTV. An ECAM CC5 RC114 is issued only when all re-tries fail.
System Action: The request fails.
User Response: Contact your site's support services to investigate the following:
If the MVC was never used before, verify to see if it was properly initialized.
Verify there is not an overlapping MVC range.
Check to see if any tape initialization jobs were run against the tape cartridge.
If the investigation does not reveal any of these problems with the MVC, contact StorageTek Hardware Support.
RTD DDDDDD ON VTSS XXXXXXXX RETURNED ECAM ERROR CC=5 RC=115
Explanation: An End-of-Tape condition was encountered during a recall request.
System Action: The request fails.
User Response: Contact your site's support services to audit the MVC. The audit will update the CDS with a valid End-of-Tape condition. Then retry the request. Do one of the following:
If the request fails again, contact StorageTek Hardware Support.
If the audit failed, drain the MVC with an eject.
RTD DDDDDD ON VTSS XXXXXXXX RETURNED ECAM ERROR CC=5 RC=116
Explanation: The MVC position is invalid.
System Action: The request fails.
User Response: Issue the following to determine if the MVC has an invalid MIR:
.VT Q MVC (volser)
If the MIR is invalid, then the MVC should be drained with eject. If all VTVs are successfully drained off the MVC, run MVCMAINT to set INVLDMIR OFF for the MVC and the cartridge analyzed by the customer's tape analysis utility (e.g., FATAR). Then, if the cartridge is to be returned for service as an MVC, issue a second MVCDRAIN without eject.
WARNING:
If the error occurred on a VOLSAFE (WORM) tape, do not drain the MVC without the recommendation of Oracle/StorageTek Support. Once a WORM tape is drained, it can no longer be used for migration and must be replaced.
If you are unable to drain all VTVs off the MVC, and if a duplexed copy of those VTVs does not exist, send the cartridge to StorageTek Hardware Support for recovery
RTD DDDDDD ON VTSS XXXXXXXX RETURNED ECAM ERROR CC=5 RC=117
Explanation: The real tape cartridge is read only.
System Action: The system issues message SLS6687I indicating an MVC was mounted for a migrate request and the cartridge was in a read only state. A new volume is selected and the migrate request(s) is re-tried.
User Response: Eject the cartridge and examine the external write protect mechanism. If the write protect mechanism is set to write protect, position it so it is no longer in write protect mode and re-enter the cartridge into the library.If the write protect mechanism is properly set and therefore not the cause of the read only problem, contact your site's support services to do the following:
Determine whether the customer's security software is protecting the cartridge and proper authorization has not been defined for the HSC started task to write to the MVC.
Query the MVC to check the Read Only status:
.VT Q MVC (volser)
If the status indicates Read Only, use MVCMAINT to turn READONLY off. The problem could also be the result of an MVC that was IMPORTED into the CDS by this utility. These MVCs will be in Read Only until MVCMAINT is used to turn this status off.
No service call should be placed for this ECAM message.
RTD DDDDDD ON VTSS XXXXXXXX RETURNED ECAM ERROR CC=5 RC=118
Explanation: The data check is reading an internal label of a VTV on an MVC.
System Action: If a duplexed copy of the VTV exists, VTCS will recover the VTV from the second copy; otherwise, the request fails.
User Response: This is probably a media problem. Query the MVC to determine if the MVC encountered a data check:
.VT Q MVC(volser)
Contact your site's support services. If the MVC encountered a data check, drain the MVC with eject. When all VTVs are successfully drained off the MVC, examine and analyze the cartridge using the your tape analysis utility e.g., (FATAR) to determine if there is a problem with the cartridge. Then, if the cartridge is to be returned to service as an MVC, issue a second MVCDRAIN without eject. If the drain process fails to drain all VTVs off the MVC, and if a duplexed copy of those VTVs does not exist, then send the cartridge to StorageTek Hardware Support for recovery.
WARNING:
If the error occurred on a VOLSAFE (WORM) tape, do not drain the MVC without the recommendation of Oracle/StorageTek Support. Once a WORM tape is drained, it can no longer be used for migration and must be replaced.
If your site's support services determines that the CC5 RC118 was not caused by a media problem, contact StorageTek Hardware Support.
RTD DDDDDD ON VTSS XXXXXXXX RETURNED ECAM ERROR CC=5 RC=117
Explanation: Blocks transferred (bytecnt) does not match mediasiz.
RTD DDDDDD ON VTSS XXXXXXXX RETURNED ECAM ERROR CC=9 RC=127
Explanation: The RTD is busy, which means another request is in process.
System Action: The request fails.
User Response: Query the VTCS locks to determine if a lock is being held by a host that is currently down:
.VT Q LOCKS
If you determine that a host holding a lock is currently down, contact your site's support services. They should issue an HSC Recover command:
(HSC Prefix) RECOVER host-id
If a held lock is not the problem, or if the HSC Recover command does not resolve the problem, contact StorageTek Software Support.
RTD DDDDDD ON VTSS XXXXXXXX RETURNED ECAM ERROR CC=9 RC=128
Explanation: VTCS attempts to mount to an RTD that is offline or inoperable to VTSS. This is an indication of an out-of-sync condition between VTSS and VTCS regarding an RTD whereby a VTSS has taken an RTD offline to itself internally and VTCS didn't know about it.
System Action: The request fails.
User Response: Vary the RTD offline using the following command:
.VT VRTD (rtd-id) OFFline
Then contact StorageTek Hardware Support.
RTD DDDDDD ON VTSS XXXXXXXX RETURNED ECAM ERROR CC=9 RC=129
Explanation: The RTD is unconfigured. This usually occurs at VTSS implementation and indicates there is a configuration mismatch between the VTSS hardware configuration and the VTCS software configuration or the HSC LIBGEN and VTCS CONFIG.
System Action: None.
User Response: Contact your site's support services to determine whether recent changes were made to RTDs in LIBGEN, and to ensure VTCS CONFIG with Reset was done. If all software configurations are verified to be correct, then contact StorageTek Hardware Support. They should verify that the VTSS Op Panel matches the customer's VTCS configuration prior to running hardware diagnostics.
RTD DDDDDD ON VTSS XXXXXXXX RETURNED ECAM ERROR CC=9 RC=132
Explanation: The Interface is already assigned to another RTD. This indicates a hardware configuration mismatch between the VTSS hardware configuration and the VTCS software configuration, or a possible RTD cabling problem.
System Action: None.
User Response: Contact your site's support services If recent changes were made to the RTDs, ensure VTCS CONFIG with RESET was done. Verify the VTCS Configuration for accuracy. If it looks correct, contact StorageTek Hardware Support. They should verify that the VTSS Op Panel matches your VTCS configuration prior to running hardware diagnostics.
RTD DDDDDD ON VTSS XXXXXXXX RETURNED ECAM ERROR CC=9 RC=133
Explanation: VTCS is unable to service the request because the interface is configured in Control Unit mode. This error would be encountered at VTSS installation time. It indicates that VTCS believes the interface is a Nearlink interface, but VTSS believes it is a host interface. The error message is not an indication of a bad ICE card; however, that ICE card is unavailable until it is fixed by a CSE. It is disruptive to fix.
System Action: None.
User Response: Contact StorageTek Hardware Support.
RTD DDDDDD ON VTSS XXXXXXXX RETURNED ECAM ERROR CC=9 RC=135
Explanation: The RTD is online. Configuration cannot be changed from the Op Panel. This condition would only be experienced during a VSM reconfiguration while an Oracle CSE is attempting to remove an RTD definition. To remove an RTD from the VTSS, do the following actions:
Issue a VTCS CONFIG with RESET.
Bring VTCS down and back up to (bounce) release the RTD from the internal VTSS table.
Bring down VTCS again to allow removal of the RTD from the VTSS.
System Action: None.
User Response: Your site's support services has probably initiated this as a planned activity. The Oracle CSE should already be on site and therefore no service call is necessary.
RTD DDDDDD ON VTSS XXXXXXXX RETURNED ECAM ERROR CC=9 RC=144
Explanation: This message relates to VSM4 only. A Channel Processor was busy with an RTD on the other port that this CIP is controlling. (Paired RTDs on a CIP are controlled by VTCS software.) This ECAM message is an indication of a VTCS Configuration done without a Reset, or it indicates a possible VTCS software problem.
System Action: None.
User Response: Contact your site's support services to verify that PTF L1H11I6 is on the host issuing the message. If so, then review VTCS Configuration for accuracy. If the configuration is accurate, contact StorageTek Hardware Support to verify that the VTSS Op Panel matches your VTCS Configuration. If the hardware configuration is correct, then the CSE should assign the problem to StorageTek Software Support for further diagnostics.
The following table describes return codes that may be specifically generated by the VLE in response to a UUI command.
Table 7-2 VLE UUI Return Codes
| Return Code | Reason Code | Description |
|---|---|---|
|
5 |
108 |
A general error condition is reported by either the VTSS or VLE. This matches to an ECAM response. |
|
5 |
109 |
There is a communication breakdown. This matches to an ECAM response. |
|
5 |
111 |
Another VMVC is mounted on the device. This matches to an ECAM response. |
|
5 |
113 |
There is no VMVC mounted on the DEVICEID connection. This matches to an ECAM response. |
|
5 |
115 |
The VMVC file system is nearly full. This matches to an ECAM response. |
|
5 |
116 |
Reported under either of the following conditions:
|
|
8 |
119 |
The VTSS inventory is full. This matches to an ECAM response. |
|
8 |
120 |
The VTSS runs out of space to store the VTV. This matches to an ECAM response. |
|
9 |
121 |
The VTSS reports the target VTV as busy. This matches to an ECAM response. |
|
9 |
122 |
The VTSS reports the target VTV as already being present. This matches to an ECAM response. |
|
9 |
123 |
The VTSS reports the target VTV as absent or missing. This matches to an ECAM response. |
|
9 |
125 |
The source VTSS reports that its inventory is unavailable. |
|
9 |
126 |
The VTSS reports the target VTV as corrupt. This matches to an ECAM response. |
|
9 |
128 |
The VTSS has reported to the VLE that the device required for the operation is offline or inoperable. |
|
9 |
132 |
A mismatch has been detected between the RTDNO= parameter and the device that initiated the connection from the VTSS to the VLE. |
|
9 |
139 |
The VTSS reports the target VTV as being recovered. This matches to an ECAM response. |
|
9 |
162 |
MOUNTDEV is already mounted. |
|
10 |
93 |
There was a timeout when performing communication between nodes in the VLE complex. |
|
10 |
96 |
The version of the command is incompatible with the previous MOUNT_VTV command. |
|
10 |
97 |
The node required to service this command is not available or is specifically offline. |
|
10 |
98 |
General problem with the parameters or the |
|
10 |
99 |
General, non-specific failure while executing the Query_Device command. |
|
11 |
3 |
The VMVC is mounted upon a different device. |
|
11 |
93 |
There was a timeout when performing communication between nodes in the VLE complex. |
|
11 |
97 |
The node required to service this command is not available or is specifically offline. |
|
11 |
98 |
General problem with the parameters or the |
|
11 |
99 |
General, non-specific failure while executing the MOUNT_VMVC command. |
|
12 |
6 |
The currently mounted VMVC volser does not match to the VOLUME parameter. |
|
12 |
93 |
There was a timeout when performing communication between nodes in the VLE complex. |
|
12 |
96 |
The version of the command is incompatible with the previous MOUNT_VTV command. |
|
12 |
97 |
The node required to service this command is not available or is specifically offline. |
|
12 |
98 |
General problem with the parameters or the DISMOUNT_VMVC command. |
|
12 |
99 |
General, non-specific failure while executing the DISMOUNT_VMVC command. |
|
13 |
9 |
The TIMESTMP parameter supplied does not match the VTV copy being requested for migration. |
|
13 |
10 |
Unable to obtain a copy of the VTV from any of the COPYFROM= locations |
|
13 |
87 |
The VLE is not authorized to access the target VMVC. |
|
13 |
88 |
Reported in the <component-fail> structure under either of the following conditions:
|
|
13 |
90 |
A migrate of a 32 GB or VCART VTV cannot be completed because a node in the transfer path does not support CARTTYPE. |
|
13 |
91 |
Reported under either of the following conditions:
|
|
13 |
92 |
The source VLE from the selected COPYFROM= parameter location reports the targeted VTV as corrupt. |
|
13 |
93 |
There was a timeout when performing communication between nodes in the VLE complex. Note that failures servicing COPYFROM= locations do not cause this error. |
|
13 |
94 |
COPYFROM VLE name is unknown in the configuration of the source VLE. |
|
13 |
95 |
COPYFROM VLE refused the connection to execute the command or could not be contacted. |
|
13 |
96 |
The version of the command is incompatible with the previous MOUNT_VTV command. |
|
13 |
97 |
The node required to service this command is not available or is specifically offline. Note that failures servicing COPYFROM= locations do not cause this error. |
|
13 |
98 |
General problem with the parameters or the MIGRATE_VTV command. |
|
13 |
99 |
General, non-specific failure while executing the MIGRATE_VTV command. |
|
14 |
9 |
The TIMESTMP parameter supplied does not match the time stamp of the VTV being recalled. |
|
14 |
87 |
The VLE is not authorized to access the target VMVC. |
|
14 |
88 |
The VTV is resident on an Archive Cloud VMVC and the VTV is not restored. |
|
14 |
90 |
A migrate of a 32 GB or VCART VTV cannot be completed because the VTSS or a node in the transfer path does not support CARTTYPE. |
|
14 |
92 |
The source VLE reports the targeted VTV as corrupt. |
|
14 |
93 |
There was a timeout when performing communication between nodes in the VLE complex. |
|
14 |
96 |
The version of the command is incompatible with the previous MOUNT_VTV command. |
|
14 |
97 |
The node required to service this command is not available or is specifically offline. |
|
14 |
98 |
General problem with the parameters or the |
|
14 |
99 |
General, non-specific failure while executing the RECALL_VTV command. |
|
15 |
7 |
The VTV identified by the PREVVTV parameter could not be found. |
|
15 |
87 |
The VLE is not authorized to access the VMVC. |
|
15 |
90 |
The inventory of a 32 GB or VCART VTV cannot be completed because a VLE node does not support CARTTYPE. |
|
15 |
92 |
The inspected VTV is found to be corrupt. Details about the VTV affected are included in the XML <vtv-data> structure in the response. |
|
15 |
93 |
There was a timeout when performing communication between nodes in the VLE complex. |
|
15 |
96 |
The version of the command is incompatible with the previous MOUNT_VTV command. |
|
15 |
97 |
The node required to service this command is not available or is specifically offline. |
|
15 |
98 |
General problem with the parameters or the INVENTORY_VMVC command. |
|
15 |
99 |
General, non-specific failure while executing the INVENTORY_VMVC command. |
|
16 |
8 |
The disk pool is not known to the VLE and the DISKPOOL parameter is specified. |
|
16 |
97 |
The node required to service this command is not available or is specifically offline. |
|
16 |
98 |
General problem with the parameters or the VOLRPT command. |
|
16 |
99 |
General, non-specific failure while executing the VOLRPT command. |
|
17 |
6 |
The VMVC parameter does not match the currently mounted VMVC (V1 only). |
|
17 |
7 |
The VTV copy being deleted does not exist upon the VMVC. |
|
17 |
9 |
The TIMESTMP parameter supplied does not match the VTV copy being requested for deletion. |
|
17 |
87 |
The VLE is not authorized to access the VMVC. |
|
17 |
93 |
There was a timeout when performing communication between nodes in the VLE complex. |
|
17 |
96 |
The version of the command is incompatible with the previous MOUNT_VTV command. |
|
17 |
97 |
The node required to service this command is not available or is specifically offline. |
|
17 |
98 |
General problem with the parameters or the |
|
17 |
99 |
General, non-specific failure while executing the DELETE_VTV command. |
|
18 |
7 |
The VTV copy being restored does not exist upon the VMVC. |
|
18 |
9 |
The TIMESTMP parameter supplied does not match the VTV copy being requested for restore. |
|
18 |
87 |
The VLE is not authorized to access the VMVC. |
|
18 |
89 |
The concurrent restore VTV limit has been exceeded. This is dependent on the Cloud implementation. This error is only returned if the archive cloud has a restore limit and the VLE can determine that this limit has been exceeded. |
|
18 |
97 |
The node required to service this command is not available or is specifically offline. |
|
18 |
98 |
General problem with the parameters or the |
|
18 |
99 |
General, non-specific failure while executing the RESTORE_VTV command. |
|
19 |
7 |
The VTV copy being restored does not exist upon the VMVC. |
|
19 |
9 |
The TIMESTMP parameter supplied does not match the VTV copy being requested for restore. |
|
19 |
87 |
The VLE is not authorized to access the VMVC. |
|
19 |
97 |
The node required to service this command is not available or is specifically offline. |
|
19 |
98 |
General problem with the parameters or the |
|
19 |
99 |
General, non-specific failure while executing the QUERY_RESTORE command. |
|
20 |
97 |
The node required to service this command is not available or is specifically offline. |
|
20 |
98 |
General problem with the parameters or the |
|
20 |
99 |
General, non-specific failure while executing the QUERY_LINK command. |
|
21 |
87 |
The VLE is not authorized to access the VMVC. |
|
21 |
97 |
The node required to service this command is not available or is specifically offline. |
|
21 |
98 |
General problem with the parameters or the RECOVER_VMVC command. |
|
21 |
99 |
General, non-specific failure while executing the RECOVER_VMVC command. |
|
30 |
1 |
The value for the DEVICEID connection is not known. |
|
30 |
2 |
The device is already performing some other kind of operation associated with VMVCs. |
|
30 |
4 |
The VMVC volser is not known to the VLE. |
|
30 |
5 |
The VMVC is connected to a different server to the DEVICEID connection. |