Chapter 113 TAPE Messages
| | |
| ||
| ||
Table of Contents
The messages in this chapter are sent by the TAPE subsystem. The subsystem ID displayed by these messages includes TAPE as the subsystem name. In this chapter, the term TERMSTAT refers to the termination status. TAPE subsystem messages include both tape-process and labeled-tape server event messages.
| |
| |
| |
 | NOTE: Negative-numbered messages are common to most subsystems. If you receive a negative-numbered message that is not described in this chapter, see Chapter 15. |
| |
| |
| |
Negative numbered messages and messages through number 410 are generated by the TAPE subsystem monitor process.
| -1000 $tapenn Sense Key: Recovered Error, LDEV $nn |
| -1001 $tapenn Sense Key: Not Ready, LDEV $nn |
| -1002 $tapenn Sense Key: Medium Error, LDEV $nn |
| -1003 $tapenn Sense Key: Hardware Error, LDEV $nn |
| -1005 $tapenn Sense Key: Unit Attention, LDEV $nn |
| -1006 $tapenn Sense Key: Data Protect, LDEV $nn |
| -1007 $tapenn Sense Key: Blank Check, LDEV $nn |
| -1008 $tapenn Sense Key: Vendor Specific, LDEV $nn |
| -1009 $tapenn Sense Key: Copy Aborted, LDEV $nn |
| -1010 $tapenn Sense Key: Aborted Command, LDEV $nn |
| -1011 $tapenn Sense Key: Equal, LDEV $nn |
| -1012 $tapenn Sense Key: Overflow, LDEV $nn |
| -1013 $tapenn Sense Key: Miscompare, LDEV $nn |
| -1014 $tapenn Sense Key: Recovered Error, LDEV $nn |
| -1015 $dev-name CPU SWITCH, LDEV $ldev, SAC: sac-name, OLD CPU cpu-old, change-initiator, msg-text |
Cause A processor switch (backup takes over as primary) occurred. This message is for G-series RVUs only. Recovery If the processor switch occurred as a result of a command (for example, the Subsystem Control Facility (SCF) PRIMARY DISK command), no corrective action is needed. If the processor switch occurred because of a hardware problem, contact your service provider and provide all relevant information:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| -1016 $dev-name PATH STATE CHANGE, LDEV $ldev, SAC: sac-name, NEW STATE state-old, change-initiator, msg-text |
| -1017 $tapenn Path switch, LDEV $nn |
| -1018 $tapenn Timeouts exceeded, LDEV $nn |
| -1019 $tapenn ERROR INJECTION, LDEV $nn | ||||
Cause An error was injected by an external program. This message is for G-series RVUs only. Effect The Module Driver has injected an error to comply with the request. Recovery Informational message only; no corrective action is needed. |
| -1020 $dev-name PON INTERRUPT OCCURRED, LDEV $ldev, SAC: sac-name, TARGET ID scsi-target-id, LUN scsi-lun, FABRIC fabric |
Cause A power on (PON) interrupt (indicating a power failure) occurred. The state of the hardware can be changed by a power failure and a subsequent power on. This message is for G-series RVUs only. Effect Microcode is reloaded for all downloadable ServerNet addressable primary controllers in the processor where the power failed. Recovery Informational message only; no corrective action is needed. |
| -1021 $dev-name INTERRUPT TIMED OUT, LDEV $ldev, ON COMMAND %Hcommand, SAC: sac-name, TARGET ID scsi-target-id, LUN scsi-lun, FABRIC fabric |
Cause An execute I/O (EIO) was issued, but no interrupt was received for the EIO; a timeout on the EIO did not occur. The interrupt from the controller never occurred, or the interrogate I/O (IIO) processing the interrupt failed. A problem exists with the channel or the controller. This message is for G-series RVUs only. Effect The tape operation aborts. Recovery Contact your a service provider and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| -1022 $dev-name UNEXPECTED INTERRUPT, LDEV $ldev, SAC: sac-name, TARGET ID scsi-target-id, LUN scsi-lun, FABRIC fabric |
Cause An unexpected interrupt for a device occurred. The ServerNet addressable controller should not be randomly interrupting. This message is for G-series RVUs only. Effect A problem might exist with the controller because it should not be randomly interrupting. Recovery If this error occurs repeatedly, contact your service provider and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| -1023 $tapenn Sector checksum error, LDEV $nn |
| -1024 $tapenn Structured checksum error, LDEV $nn |
| -1025 $dev-name LOAD MICROCODE EXECUTED, LDEV $ldev, SAC: sac-name, TARGET ID scsi-target-id, LUN scsi-lun, FABRIC fabric |
Cause The loadable control store (LCS) of a downloadable ServerNet addressable controller is loaded. (A series of LOAD LOCS execute I/Os [EIOs] was executed.) This message is for G-series RVUs only. Effect This EIO changes the microcode in the LCS of the controller. Recovery During normal operations, the controller should not become unloaded. Frequent use of this EIO might indicate a problem. Note the occurrence of this EIO to track the state of the subsystem. |
| -1026 $tapenn Device select timeout, LDEV $nn | ||||
Cause There is a tape drive or tape-drive controller problem. This message is for G‑series RVUs only. Effect The drive cannot be selected. Recovery Reinsert the controller board or power off and then power on the tape drive. If the error continues to occur, contact your service provider and provide all relevant information:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| -1027 $tapenn Device command timeout, LDEV $nn | ||||
Cause A timeout value is too short, or there is a tape drive problem. This message is for G-series RVUs only. Recovery Reset the tape drive. If the error continues to occur, contact your service provider and provide all relevant information:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| -1028 $tapenn Device command incomplete, LDEV $nn | ||||
Cause An incomplete command was received by a tape drive. This message is for G‑series RVUs only. Recovery Reset the tape drive. If the error continues to occur, contact your service provider and provide all relevant information:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| -1029 $tapenn Device busy, LDEV $nn | ||||
Cause A command was not completed by the tape drive. This message is for G‑series RVUs only. Recovery Reset the tape drive and reissue the command. If the error continues to occur, contact your service provider and provide all relevant information:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| -1030 $tapenn Device SCSI status, LDEV $nn |
| -1031 $tapenn Device interface error, LDEV $nn | ||||
Cause A controller or SCSI bus error occurred when a command was sent from the controller to the tape drive. This message is for G-series RVUs only. Recovery Reinsert the controller board. If the error continues to occur, contact your service provider and provide all relevant information:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| -1032 $tapenn Device reset, LDEV $nn | ||||
Cause The tape drive was reset by a controller because a command from the controller to the tape drive aborted. This message is for G-series RVUs only. Recovery The reset causes the command to be retried. If the error continues to occur, contact your service provider and provide all relevant information:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 32 $tapenn SMD sector checksum err, LDEV $nn |
| 33 $tapenn SMD block checksum err, LDEV $nn |
| 64 $tapenn MDR function code invalid, LDEV $nn | ||||
Cause There is a software code error. This message is for G-series RVUs only. Effect A command operation fails. Recovery If the error continues to occur, contact your service provider and provide all relevant information:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 65 $tapenn SMD MDR field field content error, LDEV $nn | ||||
Cause There is a software code error. This message is for G-series RVUs only. Effect A command operation fails. Recovery If the error continues to occur, contact your service provider and provide all relevant information:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 66 $tapenn SMD controller lock required, LDEV $nn | ||||
Cause A lock for a controller was required and could not be obtained. This message is for G-series RVUs only. Effect A command operation fails. Recovery If the error continues to occur, contact your service provider and provide all relevant information:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 96 $tapenn SMD MD interface err, LDEV $nn | ||||
Cause A module driver interface error occurred. This message is for G-series RVUs only. Effect A command operation fails. Recovery If the error continues to occur, contact your service provider and provide all relevant information:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 97 $tapenn SMD MD struct err, LDEV $nn | ||||
Cause There is a coding error in the module driver. This message is for G-series RVUs only. Effect A command operation fails. Recovery If the error continues to occur, contact your service provider and provide all relevant information:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 98 $tapenn SMD MD BM SM err, LDEV $nn | ||||
Cause There is a coding error in the module driver. This message is for G-series RVUs only. Effect A command operation fails. Recovery If the error continues to occur, contact your service provider and provide all relevant information:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 99 $tapenn SMD config err, LDEV $nn | ||||
Cause There is a module driver configuration error. This message is for G-series RVUs only. Effect A command operation fails. Recovery If the error continues to occur, contact your service provider and provide all relevant information:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 100 $dev-name WRITE RETRIED, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr}, NUMBER OF RETRIES retry-cnt, NUMBER OF EIOs CORRECTED num-eios |
Cause An execute I/O (EIO) was issued, and the returned TERMSTAT value indicates that the write to the tape was retried. Depending on the particular device status and retry count, this error might indicate a problem with the tape or the tape drive. This message is for D-series RVUs only. Effect If the retry is successful, the WRITE operation completes. Recovery Check the tape media or tape drive. If there are a large number of these errors, contact your service provider and provide all relevant information:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 101 $dev-name READ RETRIED, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr}, NUMBER OF RETRIES retry-cnt, NUMBER OF EIOs CORRECTED num-eios |
Cause An execute I/O (EIO) was issued, and the TERMSTAT value returned indicates that the read to the tape was retried. Depending on the particular device status and retry count, this error might indicate a problem with the tape media or the tape drive. This message is for D-series RVUs only. Recovery Check the tape media. Try the tape on a different drive. If there a large number of these messages for one drive, contact your service provider and provide all relevant information:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 102 $dev-name WRITE RETRIED, LDEV $ldev, SUBCHANNEL ADDRESS %unit-addr, NUMBER OF RETRIES retry-cnt, |
Cause A 3202 controller successfully retired a tape write operation. This message is for D-series RVUs only. The write is retried until either it is successful, a nonretryable error occurs, or 40 retries have been attempted. If the retry is successful, this message is generated; if not, some other message is generated. The retryable error conditions are overrun, parity error, and cyclic redundancy check (CRC) error. The event message contains information explaining the reason for the retry operation. This message could indicate an intermittent problem with the channel, controller, drive, or tape media. Recovery If a large number of these messages occur for one device, contact your service provider. |
| 103 $dev-name READ RETRIED, LDEV $ldev, SUBCHANNEL ADDRESS %unit-addr, NUMBER OF RETRIES retry-cnt, |
Cause A 3202 controller successfully retried a tape read operation. This message is for D-series RVUs only. The tape media or tape drive failed. The read is retried up to 40 times until either it is successful, a nonretryable error occurs, or no more retries are left. If the retry is successful, this message is generated; if not, some other message is generated. The retryable error conditions are overrun, parity error, and cyclic redundancy check (CRC) error. This message could indicate an intermittent problem with the channel, controller, drive, or tape media. Recovery If a large number of these messages occur for one device, contact your service provider. |
| 104 $dev-name WFM RETRIED, LDEV $ldev, SUBCHANNEL ADDRESS %unit-addr, NUMBER OF RETRIES retry-cnt, |
Cause A 3202 controller successfully retried a tape write-file-mark operation. This message is for D-series RVUs only. The tape media or tape drive failed. The write-file-mark operation is retried up to 40 times until either it is successful, a nonretryable error occurs, or no more retries are left. If the retry is successful, this message is generated; if not, some other message is generated. The retryable error conditions are overrun, parity error, and cyclic redundancy check (CRC) error. The event message contains information concerning the reason for the retry operation. This event message could indicate an intermittent problem with the channel, controller, drive, or tape media. Recovery If a large number of these messages occur for one device, contact your service provider. |
| 128 $tapenn SMD tnet svc interface err, LDEV $nn | ||||
Cause A ServerNet services interface error occurred. This message is for G-series RVUs only. Effect A command operation fails. Recovery If the error continues to occur, contact your service provider and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 129 $tapenn SMD tnet cpu timeout, LDEV $nn | ||||
Cause A ServerNet services CPU timeout error occurred. This message is for G-series RVUs only. Effect A command operation fails. Recovery If the error continues to occur, contact your service provider and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 130 $tapenn SMD tnet no avt, LDEV $nn | ||||
Cause A ServerNet services AVT error occurred. This message is for G-series RVUs only. Effect A command operation fails. Recovery If the error continues to occur, contact your service provider and provide all relevant information:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 131 $tapenn SMD tnet cpu rcv err, LDEV $nn | ||||
Cause A ServerNet services CPU receive operation error occurred. This message is for G-series RVUs only. Effect A command operation fails. Recovery If the error continues to occur, contact your service provider and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 132 $tapenn SMD tnet controller hardware err, LDEV $nn | ||||
Cause A ServerNet services controller hardware error occurred. This message is for G-series RVUs only. Effect A command operation fails. Recovery If the error continues to occur, contact your service provider and provide all relevant information:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 133 $tapenn SMD tnet controller had err, LDEV $nn | ||||
Cause A ServerNet services controller HAD error occurred. This message is for G‑series RVUs only. Effect A command operation fails. Recovery If the error continues to occur, contact your service provider and provide all relevant information:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 134 $tapenn SMD tnet path down, LDEV $nn | ||||
Cause A ServerNet services path error occurred. This message is for G-series RVUs only. Effect A command operation fails. Recovery If the error continues to occur, contact your service provider and provide all relevant information:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 135 $tapenn SMD tnet power fail, LDEV $nn |
| 136 $tapenn SMD tnet buffer invalid, LDEV $nn | ||||
Cause A memory or code error occurred. This message is for G-series RVUs only. Effect A command operation fails. Recovery If the error continues to occur, contact your service provider and provide all relevant information:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 137 $tapenn SMD tnet controller avt err, LDEV $nn | ||||
Cause A ServerNet services code error occurred. This message is for G-series RVUs only. Effect A command operation fails. Recovery If the error continues to occur, contact your service provider and provide all relevant information:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 192 $tapenn SMD device selection timeout, LDEV $nn | ||||
Cause A tape device controller or a tape device error occurred. This message is for G-series RVUs only. Effect A command operation fails. Recovery Reinsert the controller board or power off and then power on the tape drive. If the error continues to occur, contact your service provider and provide all relevant information:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 193 $tapenn SMD device command timeout, LDEV $nn |
| 194 $tapenn SMD device command incomp, LDEV $nn |
| 195 $tapenn SMD device busy, LDEV $nn |
| 196 $tapenn SMD device scsi status, LDEV $nn |
| 197 $tapenn SMD device if err, LDEV $nn | ||||
Cause A SCSI or controller error occurred. This message is for G-series RVUs only. Effect The command operation fails. Recovery Reinsert the controller board. If the error continues to occur, contact your service provider and provide all relevant information:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 198 $tapenn SMD device reset, LDEV $nn |
| 199 $tapenn SMD device data overrun, LDEV $nn |
| 200 $dev-name DEV MOD BEB ERR, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr}, ucode-err, msg-text |
Cause An execute I/O (EIO) was issued and the value of the TERMSTAT returned indicates that the microcode is bad. This error might indicate a problem with the controller or the channel. This message is for D-series RVUs only. Effect The tape drives connected to the controller are inoperative. Recovery Contact your service provider and provide all relevant information:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 201 $dev-name DEV ENV REPORT, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
Cause An EIO was issued, and the returned TERMSTAT value indicates a channel or direct memory access (DMA) error. This error might indicate a problem with the controller’s DMA chip, the controller board, or the channel. This message is for D‑series RVUs only. Effect The tape operation aborts. Recovery Contact your service provider and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 202 $dev-name DEV PORT LOGOUT, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
Cause An execute I/O (EIO) was issued, and the returned TERMSTAT value indicates that a channel error occurred. A problem might exist with the channel or the controller. This message is for D-series RVUs only. Effect The tape operation aborts. Recovery Contact your service provider and provide all relevant information:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 203 $dev-name PORT UNAVAILABLE, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
Cause An execute I/O (EIO) was issued, and the returned TERMSTAT value indicates that the formatter is powered off. Depending on the particular drive status value, this error might indicate a problem with the drive or the formatter. This message is for D-series RVUs only. Effect The tape operation aborts. Recovery Power on the tape drive or the formatter. If the drive and the formatter are already powered on, contact your service provider and provide all relevant information:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 204 $dev-name PORT LOGIN REQD, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
Cause An execute I/O (EIO) was issued, and the returned TERMSTAT value indicates that a hard controller error occurred. Depending on the particular TERMSTAT value, this error might indicate a problem with the controller. This message is for D-series RVUs only. Effect The tape operation aborts. Recovery Contact your service provider and provide all relevant information:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 256 $tapenn SMD module disabled, LDEV $nn | ||||
Cause The controller is not available or has caused too many interrupts. This message is for D-series RVUs only. Effect The path to the tape device is lost. Recovery Check the controller hardware. If the error continues to occur, contact your service provider and provide all relevant information:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 257 $tapenn SMD controller access not established, LDEV $nn |
| 258 $tapenn SMD controller unloaded, LDEV $nn |
| 259 $tapenn SMD controller queue active, LDEV $nn |
| 260 $tapenn SMD controller queue error, LDEV $nn | ||||
Cause Either a ServerNet services error occurred during a write operation to a controller request queue, or a controller request abort failure occurred. This message is for G‑series systems only. Recovery The I/O process reestablishes access to the controller. |
| 261 $tapenn SMD controller shut down, LDEV $nn |
| 288 $tapenn SMD scsi bus reset, LDEV $nn |
| 289 $tapenn SMD scsi bus reset in, LDEV $nn |
| 300 $dev-name DATA CORRECTED, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
Cause An execute I/O (EIO) involving data transfer was issued, and the RIC returned shows that the TERMSTAT indicates a correctable data error. A soft error on the media occurred, or the tape media or read/write heads might be bad. This message is for D‑series systems only. Recovery Check the tape media. If there are a large number of these errors for one drive, contact your service provider and provide all relevant information:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 301 $dev-name UNCORRECTED DATA ERROR, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
Cause An execute I/O (EIO) was issued, and the returned TERMSTAT value indicates that an uncorrectable data error occurred. This error might indicate a problem with the media, the drive, the controller, or the channel. This message is for D‑series systems only. Effect The tape operation aborts. Recovery Check the tape media, then try the media on another drive. If there are a large number of these messages for one drive, contact your service provider and provide all relevant information:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 302 $dev-name DATA PATH PARITY ERROR, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
Cause An execute I/O (EIO) was issued, and the returned TERMSTAT value indicates that a data-path parity error occurred. This error might indicate a problem with the drive, the formatter, the controller, or the channel. This message is for D‑series systems only. Effect The tape operation aborts. Recovery Contact your service provider and provide all relevant information:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 303 $dev-name DRIVE POWERED OFF, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
Cause An execute I/O (EIO) was issued, and the returned TERMSTAT value indicates that the tape drive is powered off. There might be a problem with the drive or the formatter. This message is for D‑series systems only. Effect The tape operation aborts. Recovery Make sure that the tape drive and the formatter are powered on. If they are powered on, contact your service provider and provide all relevant information:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 304 $dev-name ERASE FAILED, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
Cause An erase execute I/O (EIO) was issued to a 3207, 3208, or 3209 controller, and the returned TERMSTAT value indicates that the erase command failed. This message is for D‑series systems only. Effect The tape operation aborts. Recovery This is a hardware problem. Contact your service provider and provide all relevant information:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 305 $dev-name FORMATTER REJECT, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
Cause An execute I/O (EIO) was issued to a 3206 controller, and the TERMSTAT value returned indicates that the formatter rejected the command. This error might indicate a problem with the drive, the formatter, or the controller. This message is for D‑series systems only. Effect The tape operation aborts. Recovery Contact your service provider and provide all relevant information:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 306 $dev-name FORMATTER OR DMA ERROR, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
Cause An execute I/O (EIO) was issued, and the TERMSTAT value returned indicates that an error occurred in the formatter (formatter module for 3207) or in the direct memory access (DMA). This error might indicate a problem with the drive, the formatter, or the controller. This message is for D‑series systems only. Effect The tape operation aborts. Recovery Contact your service provider and provide all relevant information:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 307 $dev-name FORMATTER MODULE ERROR, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
Cause An execute I/O (EIO) was issued, and the TERMSTAT value returned indicates that an error occurred in the formatter (or formatter module for 3207). This error might indicate a problem with the drive, the formatter, or the controller. This message is for D‑series systems only. Effect The tape operation aborts. Recovery Contact your service provider and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 308 $dev-name ILLEGAL DRIVE STATUS, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
Cause An execute I/O (EIO) was issued, and the TERMSTAT value returned indicates that an illegal drive status was detected. This error might indicate a problem with the drive, the formatter, or the controller. This message is for D‑series systems only. Effect The tape operation aborts. Recovery Contact your service provider and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 309 $dev-name READ TOO LARGE FOR FORMATTER, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
Cause A read execute I/O (EIO) was issued, and the TERMSTAT value returned indicates that the data on the tape was too large for the formatter’s buffer. This error might indicate a problem with the drive, the formatter, or data on the tape. This message is for D‑series systems only. Effect The tape operation aborts. Recovery Contact your service provider and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 310 $dev-name OPERATION FAILED, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
Cause An execute I/O (EIO) was issued, and the TERMSTAT value returned indicates that the operation failed. This error might indicate a problem with the drive, the formatter, the controller, or the channel. This message is for D‑series systems only. Effect The tape operation aborts. Recovery Contact your service provider and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 311 $dev-name RUNAWAY TAPE, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
Cause An execute I/O (EIO) was issued, and the TERMSTAT value returned indicates that a runaway tape occurred. This error might indicate a problem with the drive, the controller, or the channel. This message is for D‑series systems only. The problem could be one of the following:
Effect The tape operation aborts. Recovery Make sure that the tape is not blank. If it is not blank and it can be read on other drives, contact your service provider and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 312 $dev-name SHORT WRITE, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
Cause An execute I/O (EIO) was issued, and the TERMSTAT value returned indicates that either a write less than 24 bytes occurred or there might be a problem with the controller or the channel. This message is for D‑series systems only. Effect The tape operation aborts. Recovery Contact your service provider and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 313 $dev-name SOFT FORMATTER ERROR, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
Cause An execute I/O (EIO) was issued, and the TERMSTAT value returned indicates that a soft formatter error occurred. This error might indicate a problem with the drive, the formatter, or the controller. This message is for D‑series systems only. Effect The tape operation aborts. Recovery Contact your service provider and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 314 $dev-name UNKNOWN RIC TERMSTAT, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
Cause An execute I/O (EIO) was issued, and the TERMSTAT value returned has a nonzero value greater than 39. This error might indicate a wrong tape-process version or a problem with the drive, the formatter, the controller, or the channel. This message is for D‑series systems only. Effect The tape operation aborts. Recovery Contact your service provider and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 315 $dev-name WRITE FAILED, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
Cause A write execute I/O (EIO) was issued, and the TERMSTAT value returned indicates that the write operation failed. The tape or drive might be write protected, or the drive, the controller, or the channel might be malfunctioning. This message is for D‑series systems only. Effect The tape operation aborts or waits until the problem is resolved. Recovery First, make sure that the write ring is on the tape. If the write still fails, contact your service provider and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 316 $dev-name CABLE LINE OPEN, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
Cause An execute I/O (EIO) was issued, and the TERMSTAT value returned indicates that the cable is not connected or is broken. This error might indicate a problem with the drive, the controller, or the cable. This message is for D‑series systems only. Effect The tape operation aborts. Recovery Make sure that the cable between the tape drive and the controller is connected. If the cable is connected, contact your service provider and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 317 $dev-name CONTROLLER DATA ERROR, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
Cause An execute I/O (EIO) was issued, and the TERMSTAT value returned indicates that a controller data error occurred. This error might indicate a problem with the controller. This message is for D‑series systems only. The sender of this operator message is the I/O process. Effect The tape operation aborts. Recovery Contact your service provider and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 318 $dev-name PHYSICAL END OF TAPE, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
Cause An execute I/O (EIO) was issued, and the TERMSTAT value returned indicates that the physical end of tape was encountered on a 5120 or 5180 drive. This error usually indicates a software error; however, the error may also indicate a problem with the drive. This message is for D‑series systems only. Effect The tape operation aborts. Recovery Make sure that the attempted operation does not try to write beyond the end-of-tape marker. If the error is not a software error, contact your service provider and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 319 $dev-name DEVICE INTERFACE ERROR, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
Cause An execute I/O (EIO) was issued, and the TERMSTAT value returned indicates a communication problem between the 3209 controller and the 5120 tape drive. This error usually indicates a problem with the drive. This message is for D‑series systems only. Effect The tape operation aborts. Recovery Contact your service provider and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 320 $dev-name INVALID STATUS, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
| 321 $dev-name RUNAWAY TAPE, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
Cause The RIC word for an I/O completion on a 3202 controller indicated a runaway tape. This message is for D‑series systems only. The 3202 controller sets this condition when any of the following occur:
For PE tape, when writing the PE ID burst from the beginning of tape (BOT), the read head fails to detect the ID burst after 1.28 inches of the burst has been written. This event could indicate a problem with the application (such as reading beyond the end-of-file mark where no data was written). It could also indicate a problem with the drive or controller. |
| 322 $dev-name UNUSUAL END, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
| 323 $dev-name COMMAND REJECT, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
Cause The RIC word from an I/O operation on a 3202 controller has the command reject flag set. This message is for D‑series systems only.The controller sets this flag if any of the following occur:
An error occurred on a previous command when command chaining. (The tape process does not use command chaining, so this event should never occur.) |
| 324 $dev-name OVERRUN ERROR, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
Cause The RIC word from an I/O operation on a 3202 controller has the overrun flag set. A read, write, or write-file-mark operation that receives this error is retried up to 40 times. The controller sets this flag when the channel fails to respond to a reconnect-in before the controller buffer either empties on a write or overflows on a read. This message is for D‑series systems only. This event might indicate a problem with the controller or the channel. |
| 325 $dev-name PARITY ERROR, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
Cause The RIC word from an I/O operation on a 3202 controller has the data parity error flag set. A read, write, or write-file-mark operation that receives this error is retried up to 40 times. The controller sets this flag when it detects a vertical or longitudinal parity error during a read or during the readback check of a write operation. This message is for D‑series systems only. This event indicates a problem with the drive or the tape media. |
| 326 $dev-name CRC ERROR, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
Cause The RIC word from an I/O operation on a 3202 controller has the CRC/multi-track error flag set. A read, write, or write-file-mark operation that receives this error is retried up to 40 times. This message is for D‑series systems only. The controller sets this flag when any of the following occur:
No file mark was detected by the read head when writing a file mark. |
| 327 $dev-name COVER OPEN, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
Cause An execute I/O (EIO) was issued, and the TERMSTAT value returned indicates that the tape unit’s cover is open or broken. This message is for D‑series systems only. Effect Depending on the application, the tape operation either aborts or waits until the problem is resolved. Recovery Close the tape unit’s cover. If the cover is closed, contact your service provider and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 329 $dev-name DOES NOT RESPOND, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
| 330 $dev-name NEEDS TO BE CHECKED, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
Cause The TERMSTAT value indicates a communication problem between the controller and the tape drive. The specific error condition could not be decoded or identified. Possibly the tape device is faulty. This message is for D‑series systems only. Effect The tape operation aborts. Recovery First try powering the unit off and on, then restart the application. Next, check the cable connections between the controller and the device. If the problem still exists, run the TMDS tape diagnostics to determine whether a component is faulty. See the TMDS Reference Manual for diagnostic procedures. If you cannot remedy the problem, contact your service provider and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 331 $dev-name ID BURST ERROR, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
Cause The TERMSTAT value indicates a problem accessing the tape unit. Typically, this error is caused by the use of a blank tape, an incorrectly formatted tape, or a faulty drive. This message is for D‑series systems only. Effect Depending on the cause of the error, the tape operation aborts or the tape is rewound and unloaded. Recovery First, make sure that the tape is labeled. Then check the drive to make sure that it is set at the density recorded on the tape volume. If you don’t know the tape volume density, try switching to the other density setting. If the problem is a faulty drive, first clean the drive heads and tape guides and retry. If this does not work, run the TMDS tape diagnostics to determine whether a component is faulty. See the TMDS Reference Manual for diagnostic procedures. If you cannot remedy the problem, contact your service provider and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 332 $dev-name SOFT CONTROLLER ERROR, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
Cause The controller and the tape unit are not communicating; the problem is probably on the controller side. This message is for D‑series systems only. Effect The tape operation aborts. Recovery First check the cabling between the controller and the device. Next, power the device off and on and retry the application. If the error still exists, look at the TMDS log for error messages that may help identify the problem. If you cannot remedy the problem, contact your service provider and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 333 $dev-name UNKNOWN ERROR, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
Cause The TERMSTAT value indicates a problem that cannot be identified. This message is for D‑series systems only. Effect The tape operation aborts. Recovery Run the TMDS tape diagnostics to determine the problem. See the TMDS Reference Manual for diagnostic procedures. If you cannot remedy the problem, contact your service provider and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 334 $dev-name DRIVE OR MOUNTED MEDIA IS WRITE PROTECTED |
Cause Write access was not enabled on a drive or mounted media. This message is for D‑series systems only. Effect The application is unable to write to a drive or mounted media. Recovery If the media on the drive is write protected, take the appropriate action to remove the write protection. If there is a write-protect switch on the drive and it is set, turn it off. |
| 335 $tapenn drive is assigned to another host, LDEV $nn |
| 336 $tapenn drive unloaded due to unrecoverable error, LDEV $nn |
| 337 $tapenn mounted media is incompatible with drive, LDEV $nn |
| 400 $dev-name CPU SWITCH, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr}, OLD CPU cpu-old, change-initiator, msg-text |
Cause A processor switch (backup takes over as primary) occurred. This message is for D‑series systems only. Recovery If the processor switch occurred as a result of a command (for example, the PUP PRIMARY command), then no corrective action is needed. If the processor switch occurred because of a hardware problem, contact your service provider and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 401 $dev-name BAD STATUS FROM EIO, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr}, LAC %lac, LPRM %lprm, RDST %rdst, CHANNEL STATUS WORD %status |
Cause An execute I/O (EIO) was issued, and the read status (RDST) or the channel status returned contained an error condition. The EIO did not properly execute because a problem exists within the controller or the channel. This message is for D‑series systems only. Effect The tape operation aborts. Recovery Contact your service provider and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 402 $dev-name BAD STATUS FROM IIO, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} RIC %ric, RIST %rist, CHANNEL STATUS WORD %status |
Cause An interrogate I/O (IIO) was issued, and the read interrupt status (RIST) or the channel status returned contained an error condition. The execute I/O (EIO) executed properly, but the IIO failed. A problem exists in the controller or the channel. This message is for D‑series systems only. Effect The tape operation aborts. Recovery Contact your service provider and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 403 $dev-name INTERRUPT OVERRUN, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
Cause A unit interrupted while a previous interrupt (from that unit) was being processed. The problem might in the controller because a unit should not interrupt more than once per execute I/O (EIO). This message is for D‑series systems only. Effect The tape operation aborts. Recovery Contact your service provider and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 404 $dev-name INTERRUPT TIMED OUT, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
Cause An execute I/O (EIO) was issued, but no interrupt was received for the EIO; a timeout on the EIO did not occur. The interrupt from the controller never occurred, or the interrogate I/O (IIO) processing the interrupt failed. A problem exists with the channel or the controller. This message is for D‑series systems only. Effect The tape operation aborts. Recovery Contact your service provider and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 405 $dev-name LOAD MICROCODE EXECUTED, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
Cause The loadable control store (LCS) of a downloadable controller is loaded. (A series of LOAD LOCS execute I/Os (EIOs) was executed.) This message is for D‑series systems only. Effect This EIO changes the microcode in the LCS of the controller. Recovery During normal operations, the controller should not become unloaded. Frequent use of this EIO may indicate a problem. Note the occurrence of this EIO to track the state of the subsystem. |
| 406 $dev-name PATH STATE CHANGE, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
| 407 $dev-name PON INTERRUPT OCCURRED, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
Cause A power on (PON) interrupt (indicating a power failure) occurred. The state of the hardware can be changed by a power failure and a subsequent power on. This message is for D‑series systems only. Effect Microcode is reloaded for all downloadable controllers primaried in the processor where the power failed. Recovery Informational message only; no corrective action is needed. |
| 408 $dev-name SET BURST EIO EXECUTED, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
| 409 $dev-name SET HOLDOFF EIO EXECUTED, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
| 410 $dev-name UNEXPECTED INTERRUPT, LDEV $ldev, {cpu,chan,%ctlr,%unit | SUBCHANNEL ADDRESS %unit-addr} |
Cause An unexpected interrupt for a device occurred. The controller should not be randomly interrupting. This message is for D‑series systems only. Effect A problem might exist with the controller because it should not be randomly interrupting. Recovery If this error occurs repeatedly, contact your service provider and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 511 $tapenn tape process information, LDEV $nn |
Messages 600 and above are operator messages generated by the labeled-tape server ($ZSVR).
| 600 $ZSVR: seq MOUNT vid [ REEL num ] [ DENSITY density ] [ ON $dev ] WITH RING [ comment ] | ||||||||||
Cause A tape file was opened for output with standard ANSI label processing, but the tape was not mounted. Effect The operation waits for the tape to be mounted. Recovery If you want to mount the tape, make sure that it is write-enabled. If “ON $dev” appears in the message, mount the tape on the specified device. Otherwise, mount the tape on any available tape device. If DENSITY density appears in the message, the device must support the specified density; also, set the density switch (if the device has a density switch). If you do not want to mount the tape, reject the mount request with the TAPECOM REJECT command. |
| 601 $ZSVR: seq MOUNT vid [ REEL num ] [ DENSITY density ] [ ON $dev ] NO RING [ comment ] | ||||||||||
Cause A tape file was opened for input with ANSI-standard label processing, but the tape was not mounted. Effect The operation waits for the tape to be mounted. Recovery If you want to mount the tape, make sure that it is not write-enabled. If “ON $dev” appears in the message, mount the ANSI tape on the specified device. Otherwise, mount the tape on any available tape device. If DENSITY density appears in the message, the device must support the specified density; also, set the density switch (if the device has a density switch). If you do not want to mount the tape, reject the mount request with the TAPECOM REJECT command. |
| 602 $ZSVR: seq MOUNT SCRATCH TAPE [ REEL num ] [ DENSITY density ] [ ON $dev ] WITH RING [ comment ] | ||||||||||
Cause An output operation needs a scratch tape, or an output file requires more than one volume, but not enough volume serial numbers have been specified in the DEFINE entry. The requesting application is suspended until a scratch tape is mounted. Effect The operation waits for the tape to be mounted. Recovery Mount an ANSI scratch tape. A scratch tape is a labeled tape with an expired date. Make sure that the tape is write-enabled. If “ON $dev” appears in the message, mount the tape on the specified device. Otherwise, mount the tape on any available tape device. If DENSITY density appears in the message, the device must support the specified density; also, set the density switch (if the device has a density switch). If you do not want to mount the tape, reject the mount request with the TAPECOM REJECT command. |
| 603 $ZSVR: seq MOUNT IBM vid [ REEL num ] [ DENSITY density ] [ ON $dev ] WITH RING | ||||||||||
Cause A tape file was opened for output with standard IBM label processing, but the tape was not mounted. Effect The operation waits for the tape to be mounted. Recovery If you want to mount the tape, make sure that it is write-enabled. If “ON $dev” appears in the message, mount the tape on the specified device. Otherwise, mount the tape on any available tape device. If DENSITY density appears in the message, the device must support the specified density; also, set the density switch (if the device has a density switch). If you do not want to mount the tape, reject the mount request with the TAPECOM REJECT command. |
| 604 $ZSVR: seq MOUNT IBM vid [ REEL num ] [ DENSITY density ] [ ON $dev ] NO RING [ comment ] | ||||||||||
Cause A tape file was opened for input with standard IBM label processing, but the tape was not mounted. Effect The operation waits for the tape to be mounted. Recovery If you want to mount the tape, make sure that it is not write-protected. If “ON $dev” appears in the message, mount the tape on the specified device. Otherwise, mount the tape on any available tape device. If DENSITY density appears in the message, the device must support the specified density; also, set the density switch (if the device has a density switch). If you do not want to mount the tape, reject the mount request with the TAPECOM REJECT command. |
| 605 $ZSVR: seq MOUNT IBM SCRATCH TAPE [ REEL num ] [ DENSITY density ] [ ON $dev ] WITH RING | ||||||||||
Cause An output operation requested an IBM-labeled scratch tape, or an output file requires more than one volume, but not enough volume serial numbers were specified in the DEFINE entry. Effect The operation waits for the tape to be mounted. Recovery Mount an IBM scratch tape. (A scratch tape is a labeled tape with an expired date.) Make sure that the tape is write-enabled. If “ON $dev” appears in the message, mount the tape on the specified device. Otherwise, mount the tape on any available tape device. If DENSITY density appears in the message, the device must support the specified density; also, set the density switch (if the device has a density switch). If you do not want to mount the tape, reject the mount request with the TAPECOM REJECT command. |
| 606 $ZSVR: seq REQUEST TO USE $dev UNLABELED [ comment ] | ||||
Cause An application requested to use an unlabeled tape on $dev. Effect The requesting application is suspended until you accept or reject the request. Recovery Accept or reject the request by issuing the TAPECOM ACCEPT or the TAPECOM REJECT command. |
| 607 $ZSVR: seq REQUEST TO USE $dev WITH NO LABEL PROTECTION [ comment ] | ||||
Cause A BLP (bypass label processing) request was made for a specific device. Effect The requesting application is suspended until you accept or reject the request. Recovery Accept or reject the request with TAPECOM by issuing the TAPECOM ACCEPT or the TAPECOM REJECT command. Do not mount a labeled tape required by another application on $dev once this request is accepted. |
| 608 $ZSVR: seq UNKNOWN TAPE ON $dev, ACCEPT OR MOUNT CORRECT TAPE TO PROCEED | ||||
Cause A tape is mounted on a device that is opened for no label processing (NL mode). For some reason, perhaps the tape is blank or the wrong density, the system can’t use automatic volume recognition (AVR) to determine if the tape is unlabeled or not. Effect The system waits for a response. The tape remains online. Recovery If the density setting is wrong, correct it and press the ONLINE button twice to enable AVR. If the tape is the wrong tape, mount the correct tape. If the tape is blank, accept the tape by issuing the TAPECOM ACCEPT command. |
| 609 $ZSVR: seq MOUNT TMF vid [ REEL num ] [ DENSITY density ] [ ON $dev ] WITH RING | ||||||||||
Cause A tape file was opened for output with standard TMF-label processing, but the tape was not mounted. The operation waits for the tape to be mounted. Effect The operation waits for the tape to be mounted. Recovery If you want to mount the tape, make sure that it is write-enabled. If “ON $dev” appears in the message, mount the tape on the specified device. Otherwise, mount the tape on any available tape device. If DENSITY density appears in the message, the device must support the specified density; also, set the density switch (if the device has a density switch). If you do not want to mount the tape, use TAPECOM to reject the request. |
| 610 $ZSVR: seq MOUNT TMF vid [ REEL num ] [ DENSITY density ] [ ON $dev ] NO RING | ||||||||||
Cause A tape file was opened for input with standard Transaction Management Facility (TMF)-label processing, but the tape was not mounted. Effect The operation waits for the tape to be mounted. Recovery If you want to mount the tape, make sure that it is not write-enabled. If “ON $dev” appears in the message, mount the tape on the specified device. Otherwise, mount the tape on any available tape device. If DENSITY density appears in the message, the device must support the specified density; also, set the density switch (if the device has a density switch). If you do not want to mount the tape, reject the request with the TAPECOM REJECT command. |
| 611 $ZSVR: seq REQUEST TO STOP [\system.]cpu,pin DUE TO DEVICE ERROR ON $dev | ||||
Cause A device error occurred when a labeled-tape operation was running. The tape process wants to force the application process to abend. This error may occur after a power failure, after a mount request for a continuation volume is rejected, or after a device goes offline. Effect The message appears as an outstanding request to the TAPECOM MOUNTS command because it requires operator attention. It cannot be accepted or rejected through TAPECOM. |
| 612 $tape-device: ERROR 1 - CANNOT PERFORM VOLUME RECOGNITION. ERROR errnum |
Cause An exception occurred while the specified tape device was doing volume recognition. There may also be a density problem. Effect The tape is rewound and unloaded. Recovery See Appendix B, for corrective action for the file‑system error errnum. If you are using a 5101, 5103, 5105, or 5107 tape drive, check the drive to make sure that it is set at the density recorded on the tape volume. If you don’t know the tape volume density, try the other density setting. A tape volume recorded at 6250 bpi causes an error if you mount it on a 5101, 5103, 5105, or 5107 drive. If you want to use the tape, reinitialize the tape for the device by issuing the command TAPECOM UNLABEL! or TAPECOM LABEL! |
| 613 $tape-device: ERROR 2 - PROTECTION VIOLATION, VOLUME vid NOT EXPIRED | ||
Cause There was an attempt to open a tape for output or for use as a scratch tape, but the tape’s expiration date is still in effect. Effect The mounted volume cannot be used. The tape is rewound and unloaded. If the volume was specifically requested by a user in the DEFINE field, the open request is rejected. Recovery If want to use the tape, run TAPECOM SCRATCH to make the volume a scratch tape; then repeat the operation that caused the error. |
| 614 $tape-device: ERROR 3 - WRONG TAPE, vid1 MOUNTED, SHOULD BE vid2 | ||
Cause A specific tape device was expecting a continuation volume. Effect The mounted volume cannot be used. The tape is rewound and unloaded. The previous mount message is displayed again. All outstanding requests are still pending. Recovery Either mount the correct volume, or if the volume requested by the program is not available, abort the operation by rejecting the mount request. |
| 615 $tape-device: ERROR 4 - WRONG TAPE, NOT LABELED, SHOULD BE vid |
| 616 $tape-device: ERROR 5 - WRONG TAPE, vid MOUNTED, USE UNLABELED TAPE |
Cause A standard-labeled tape was mounted after the user program had opened the tape process without standard-label processing. Effect The request is rejected with a TAPE NOT READY error. The standard-labeled tape is unloaded and rewound. Recovery The application program should handle the TAPE NOT READY error and put out messages as if tape label processing did not exist. Do not use a labeled tape. |
| 617 $tape-device: ERROR 6 - VOLUME vid IS ANSI TAPE, NOT IBM TAPE AS REQUIRED | ||
Cause The correct volume tape was mounted, but the tape label is different from that specified in the DEFINE attribute LABELS. The attribute was IBM and the tape was ANSI. Effect The tape is rewound and unloaded, and the application is suspended until the correct tape is mounted. Recovery If you want to mount an ANSI tape, abend the application by rejecting the mount request for an IBM tape. Then change the DEFINE attribute to indicate an ANSI tape. Finally, retry the operation. If you want to use an IBM tape, mount an IBM tape. If the operation was supposed to start output to scratch tape and volume is a scratch tape, either use the TAPECOM RELABELIBM command to change the tape to IBM format, or use the TAPECOM LABELIBM command to make the tape an IBM tape. |
| 618 $tape-device: ERROR 7 - VOLUME vid IS IBM TAPE, NOT ANSI TAPE AS REQUIRED | ||
Cause A specific tape device expected a continuation volume; however, the correct volume serial-number tape was mounted with an IBM-label type, but the DEFINE attribute LABELS was specified as ANSI. Effect The tape is rewound and unloaded. The application is suspended until the correct tape is mounted. Recovery If you want to mount an IBM tape, abend the application by rejecting the mount request for an ANSI tape. Then change the DEFINE attribute to indicate an IBM tape. Finally, retry the operation. If you want to use an ANSI tape, mount an ANSI tape. If the operation was supposed to start output to scratch tape and volume is a scratch tape, either use the TAPECOM RELABEL command to change the tape to ANSI format, or use the TAPECOM LABEL command to make the tape an ANSI tape. |
| 619 $tape-device: ERROR 8 - VOLUME vid IS WRITE PROTECTED |
| 620 $tape-device: ERROR 9 - VOLUME vid IS TMF TAPE, CANNOT BE USED | ||
Cause The mounted volume is dedicated to Transaction Management Facility (TMF) use as indicated by the label. Effect The tape is rewound and unloaded. The application is suspended until the correct tape is mounted. Recovery Mount a tape that is not a TMF tape or change the DEFINE, then retry the operation. |
| 621 $tape-device: ERROR 10 - INPUT FILE filename INCOMPLETE |
Cause The file did not end on the last volume specified in the DEFINE attribute. The system does not know which volume serial number to request. Effect The input file may not have been processed to its end-of-file. Recovery Locate all tape reels that contain the specified file, include all volume serial numbers in the DEFINE attribute, then rerun the application. |
| 622 $tape-device: ERROR 11 - VOLUME vid IS IBM TAPE, NOT BACKUP TAPE AS REQUESTED | ||
Cause A volume was mounted to satisfy a BACKUP request, but the volume had an IBM label. (The serial number was correct.) Effect The tape is rewound and unloaded. The application is suspended until the correct tape is mounted. Recovery If the operation was for output, label a new tape with the correct type. An ANSI tape can be used for BACKUP. |
| 623 $tape-device: ERROR 12 - VOLUME vid IS ANSI TAPE, NOT TMF TAPE AS REQUESTED | ||
Cause A tape device expected a Transaction Management Facility (TMF) tape. The correct volume serial-number tape was mounted, but the label type was ANSI. Effect The tape is rewound and unloaded. The application is suspended until the correct tape is mounted. Recovery Use TMFCOM to create a TMF tape of the volume or TMF catalog, or add media, and retry the operation. |
| 624 $tape-device: ERROR 13 - VOLUME vid IS IBM TAPE, NOT TMF TAPE AS REQUESTED | ||
Cause A tape device expected a TMF tape. The correct volume serial-number tape was mounted, but the label type was IBM. Effect The tape is rewound and unloaded. The application is suspended until the correct tape is mounted. Recovery Use TMFCOM to create a TMF tape of the volume or TMF catalog, or add media, then retry the operation. |
| 625 $tape-device: ERROR 14 - VOLUME vid IS BACKUP TAPE, NOT TMF TAPE AS REQUESTED | ||
Cause A tape device expected a TMF tape. The correct volume serial-number tape was mounted, but the label type was BACKUP. Effect The tape is rewound and unloaded. The application is suspended until the correct tape is mounted. Recovery Use TMFCOM to create a TMF tape of the volume or TMF catalog, or add media, then retry the operation. |
| 626 $tape-device: ERROR 15 - BAD TRAILER LABELS vid. { file-id | file-seq-number } | ||
Cause An error occurred during CLOSE processing that prevented trailer labels from being correctly written to tape. Effect CLOSE does not return an error, and the application that used the labeled tape continues. The fact that the file does not have a valid trailer label may or may not present a problem in the future. Recovery Rerun the application if trailer labels are relevant. |
| 627 $tape-device: ERROR 16 - DEVICE ERROR, STOP [\system.]cpu.pin BEFORE ANY TAPE MOUNT |
Cause An error occurred that must be cleared before another tape can be mounted. The tape process unloads the tape and returns file-system error 100 to requests from application process cpu.pin. An operator may have rejected the mount request, or there may have been a hardware failure. Effect The tape process does not accept additional tapes or any request except CLOSE. The application process cpu.pin may or may not stop itself after receiving the error. Recovery Stop the application process if it has not already stopped. Restart the application if desired. |
| 628 $tape-device: ERROR 17 - TAPE PROCESS INTERNAL ERROR, BAD NUMBER: num |
Cause The tape process detected an internal error in the labels attribute of the DEFINE while processing an OPEN request. Effect The OPEN request is rejected. Recovery Note the bad number, then contact your service provider and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 629 $tape-device: ERROR 18 - WRONG TAPE, NOT LABELED, USE SCRATCH TAPE |
| 630 $ZSVR: ERROR 1001 - FATAL ERROR, FAILED TO OPEN $RECEIVE: errnum |
Cause An internal error occurred: $ZSVR could not open $RECEIVE. Recovery See Appendix B, for corrective action for error errnum. |
| 631 $ZSVR: ERROR 1002 - FATAL ERROR, FAILED TO READ $RECEIVE: errnum |
Cause An internal error occurred while $ZSVR was reading from $RECEIVE. Recovery See Appendix B, for corrective action for error errnum. |
| 632 $ZSVR: ERROR 1003 - FATAL ERROR, NO MEMORY FOR $ZSVR |
| 633 $ZSVR: ERROR 1004 - INCORRECT DATA LENGTH FROM TAPECOM: errnum |
Cause An internal error occurred during communication between TAPECOM and $ZSVR. Effect $ZSVR does not act on the command. Recovery Repeat the TAPECOM command. See Appendix B, for corrective action for error errnum. If this message reappears, contact your service provider and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 634 $tape device: STATUS 502 - VOLUME vid REJECTED | ||
Cause An operator rejected a mount request for a continuation volume in a multireel operation. Effect The requesting application receives file-system error 194. TAPE message 636 is displayed. Recovery If the mount request was for a continuation volume for a multiple reel operation, you must stop the requesting application. |
| 635 $ZSVR: STATUS 1501 - $ZSVR UP |
| 636 $ZSVR: STATUS 1502 - EXECUTED TAPECOM REJECT seq | ||
Cause $ZSVR executed the TAPECOM request to reject the mount or device request seq on a device. Effect The application fails with open error 194. Recovery If the mount request was for a continuation volume in a multiple reel operation, you must stop the requesting application. |
| 637 $ZSVR: STATUS 1503 - EXECUTED TAPECOM ACCEPT seq |
| 638 $ZSVR: STATUS 1504 - vid TAPE OPENED ON $tape-device |
| 639 $ZSVR: STATUS 1505 - UNREQUESTED NL TAPE ONLINE ON $dev | ||
Cause An unlabeled tape is mounted, but there was no request for it. This message may appear if you mount a tape before running an unlabeled tape operation and this tape does not satisfy an outstanding request. Effect The tape is used for subsequent nonlabeled (NL) requests for this device. Recovery Informational message only; no corrective action is needed. |
| 640 $ZSVR: STATUS 1506 - UNREQUESTED ANSI TAPE vid ONLINE ON $dev | ||||
Cause An ANSI-standard labeled tape is mounted, but there was no request for it. This message may appear if you mount a tape before running a labeled tape operation and this tape does not satisfy an outstanding request. Effect The tape is used to satisfy subsequent mount requests. Recovery Informational message only; no corrective action is needed. |
| 641 $ZSVR: STATUS 1507 - UNREQUESTED IBM TAPE vid ONLINE ON $dev | ||||
Cause An IBM-labeled tape is mounted, but there was no request for it. This message may appear if you mount a tape before running a labeled tape operation and this tape does not satisfy an outstanding request. Effect The tape is used to satisfy subsequent request for the volume. Recovery Informational message only; no corrective action is needed. |
| 642 $ZSVR: STATUS 1508 - UNREQUESTED OLD TMF TAPE vid ONLINE ON $dev | ||||
Cause An old-format, Transaction Management Facility (TMF)-labeled tape is mounted, but there was no request for it. This message may appear if you mount a tape before TMF requires it. This tape does not satisfy any outstanding request. Effect The tape is used to satisfy subsequent TMF requests. Recovery Informational message only; no corrective action is needed. |
| 643 $ZSVR: STATUS 1509 - UNREQUESTED format FORMAT BACKUP TAPE vid ONLINE ON $dev | ||||||
Cause A BACKUP labeled tape is mounted, but there was no request for it. This message may appear if you mount a tape before entering BACKUP and this tape does not satisfy any outstanding request. Effect The tape is used to satisfy subsequent BACKUP requests. Recovery Informational message only; no corrective action is needed. |
| 644 $ZSVR: STATUS 1510 - UNREQUESTED NEW TMF TAPE vid ONLINE ON $dev | ||||
Cause A new-format, Transaction Monitoring Facility (TMF)-labeled tape is mounted, but there was no request for it. This message may appear if you mount a tape before TMF requests it and this tape does not satisfy any outstanding request. Effect The tape is used to satisfy subsequent requests. Recovery Informational message only; no corrective action is needed. |
| 645 $tape device: WARNING 901 - FILE filename TRAILER LABELS IN ERROR |
Cause An error was returned while $ZSVR was reading the trailer labels that followed input data. Recovery Informational message only; no corrective action is needed. This warning indicates that the input data was handled without error; only the trailer labels had an error. However, inform the owner of the tape about this warning message. |
| 646 $tape device: WARNING 902 - BLOCK COUNTS MISMATCH IN FILE filename |
| 647 $tape device: WARNING 903 - INPUT FILE filename ENDS ON VOLUME vid |
| 648 $ZSVR: seq VOLUME vid MOUNTED |
| 649 $ZSVR: seq REQUEST FOR VOLUME vid CANCELED | ||||
Cause The mount request was canceled. The requestor’s processor may have gone down. Recovery Informational message only; no corrective action is needed. |
| 650 $ZSVR: seq REQUEST FOR DEVICE $dev CANCELED | ||||
Cause The request for device $dev was canceled. The requestor’s processor may have gone down. Recovery Informational message only; no corrective action is needed. |
| 651 $ZSVR: seq REQUEST FOR VOLUME vid REJECTED BY OPERATOR | ||||
Cause An operator rejected request seq. Effect The OPEN request receives file-system error 194. Recovery Informational message only; no corrective action is needed. See Appendix B, for information on the specified error. |
| 652 $ZSVR: seq REQUEST FOR DEVICE $dev ACCEPTED BY OPERATOR | ||||
Cause An operator accepted request seq from device $dev. Recovery Informational message only; no corrective action is needed. |
| 653 $ZSVR: seq REQUEST FOR DEVICE $dev REJECTED BY OPERATOR | ||||
Cause An operator rejected request seq from device $dev. Effect The requester receives file-system error 194. Recovery Informational message only; no corrective action is needed. See Appendix B, for information on the specified error. |
| 654 WARNING 904 - VOLUME vid DENSITY CHANGED TO val1 FROM val2 | ||||||
Cause The user specified a value of val1 in the DEFINE for a labeled tape on a tape device where the tape density can be set programmatically (5130, 5106, or 5107). The user is accessing the tape for output and is writing the first file on the volume. This message informs the operator of the change in the volume’s density. Valid values for val1 and val2 are 800, 1600, and 6250. Effect Volume is written at density val1. Recovery Informational message only; no corrective action is needed. |
| 655 WARNING 905 - VOLUME vid CHANGED TO mode1 FROM mode2 | ||||||
Cause The user specified a tape mode of mode1 in the DEFINE for a labeled tape on a 5120 cartridge tape drive. The user is accessing the volume for output and is writing the first file on the volume. This message informs the operator of the change in the volume’s tape mode. Valid values for mode1 and mode2 are STREAM and STARTSTOP. Effect Volume is written with tape mode mode1. Recovery Informational message only; no corrective action is needed. |
| 656 WARNING 906 - VOLUME vid IS DENSITY val1 INSTEAD OF val2 | ||||||
Cause The user specified a density of val2 in the DEFINE for a labeled tape on a tape device where density can be set programmatically (5130, 5106 or 5107). The user’s requested density is not used for one of two reasons:
Valid values for val1 and val2 are 800, 1600, or 6250. Effect The tape volume’s existing density is used. Recovery Informational message only; no corrective action is needed. |
| 657 WARNING 907 - VOLUME vid IS mode1 INSTEAD OF mode2 | ||||||
Cause The user specified a tape mode of mode2 in the tape DEFINE for a labeled tape on a 5120 cartridge tape device. The user’s requested tape mode is not used for one of two reasons:
Valid values for mode1 and mode2 are STREAM and STARTSTOP. Effect The tape volume’s existing tape mode is used. Recovery Informational message only; no corrective action is needed. |
| 658 $ZSVR : WARNING 908 - TAPE vid ON device IS NOT EXPIRED | ||
Cause The mounted tape has the correct volume identification, but the expiration date is still in effect. Effect The mounted volume can not be used and the application is suspended until the correct tape is mounted. Recovery If you want to use the tape, use TAPECOM SCRATCH to make the volume a scratch tape and repeat the operation. |
| 659 vid dismounted from device | ||||
Cause The tape named vid was dismounted from a tape drive device. If the tape was an unlabeled tape, vid is blank filled. Effect The tape drive is available for another tape to be mounted. Recovery Informational message only; no corrective action is needed. |
| 660 $ZSVR: Status 1511 - SQUEALER STATUS:TYPE = squealer-type; ERROR = file-system-error | ||||
Cause Depends on squealer-type. Effect Depends on squealer-type. Recovery Determine and correct the source of the problem, depending on squealer-type. |
| 661 Error 1005 - Error creating DSM/TC: errornum |
| 662 Error 1006 - DSM/TC WRITEREAD error: errornum |
| 663 Error 1007 - DSM/TC REPLY error: error | ||
Cause MEDIADBM was unable to process the $ZSVR request because of the DSM/TC error reported in the message. Effect If $ZSVR is servicing a mount request, the application process making the request fails with file-system error 594. (In all cases, a DSM/TC error is returned to $ZSVR. See the EMS log for detailed information.) |
| 664 Error 1008 - Error creating DSM/TC expiration process: errornum | ||
Cause $ZSVR could not create the MEDDEM process because of a file-system error. Effect No Distributed Systems Management/Tape Catalog (DSM/TC) cleanup can be done. No tape volumes expire automatically. Recovery Correct the error and $ZSVR automatically creates the MEDDEM process tomorrow. If cleanup is needed now, use the MEDIACOM command, EXPIRE TAPEFILE. |
| 665 STATUS 1513 - AUTO TAPE EXPIRATION INITIATED |
Cause The Distributed Systems Management/Tape Catalog (DSM/TC) catalog manager has finished cleanup processing. This process is automatically invoked once per day by $ZSVR, and when a new $ZSVR is started. Effect The DSM/TC database has been checked, and its SQL statistics have been updated to optimize performance. Recovery Informational message only; no corrective action is needed. |
| 666 Wrong tape, volser mounted, mount correct tape |
| 667 Error 1009 - Error creating SSI: errornum | ||
Cause $ZSVR cannot create the storage server interface (SSI) process. Effect No SSI process is created. This error is generated each time $ZSVR attempts to create an SSI process and fails. Recovery Analyze the error and take the appropriate action. See Appendix B, for information on the specified error. |
| 668 Error 1010 - SSI WRITEREAD error: errornum | ||
Cause $ZSVR sent a message to the storage server interface (SSI) process, but a file-system error was returned. Effect $ZSVR automatically tries to restart the SSI process and retries the request three times. Recovery If the retry attempt is successful, no corrective action is needed. If the retry fails, file-system error 595 is returned to the tape request. See Appendix B, for information on the specified error. For more information on this error, see the DSM/Tape Catalog Management Programming Manual. |
| 669 Error 1011 - SSI retryable error: ssi-errornum | ||
Cause $ZSVR has received a nonfatal error from the SSI process. Effect The tape request is retried automatically. Recovery Use the MEDIACOM command, REJECT TAPEMOUNT, if you do not want to retry the request. See Appendix B, for information on the specified error. |
| 670 Error 1012 - SSI non-retryable error: ssi-errornum | ||
Cause $ZSVR has received a fatal error from the SSI process. Effect The tape request that was being processed fails with file-system error 595. See Appendix B, for information on the specified error. For more information on this error, see the DSM/Tape Catalog Management Programming Manual. |
| 671 Error 1013 - All tape drives busy, queuing ACS request |
| 672 Error 1014 - Ejecting mismatched tape, internal: volser1, external volser2 | ||
Cause $ZSVR detected a mismatched tape mounted by the tape cartridge. Effect The application receives a file-system error 595, and the tape volume is ejected from the tape cartridge. See Appendix B, for information on the specified error. For more information on this error, see the DSM/Tape Catalog Management Programming Manual. Recovery Either label the tape correctly, or use a different tape volume and retry the application. |
| 673 Error 1015 - Dismount of ACS tape, volser, failed |
| 674 Error 1016 - ACS tape mounted on drive, drive, wrong label type | ||
Cause $ZSVR detected a mismatched tape type mounted by the tape cartridge. Effect The application receives a file-system error 595, and the tape volume is dismounted from the tape cartridge. (The name of the tape was correct, but the label attribute was mismatched.) See Appendix B, for information on the specified error. For more information on this error, see the DSM/Tape Catalog Management Programming Manual. Recovery Either label the tape correctly or use a different tape volume and retry the application. |
| 675 Error 1017 - Excluded pool requests need to specify device in the DEFINE |
Cause An application requested a tape volume residing in an excluded pool and did not specify a device in the TAPECATALOG DEFINE attribute. Effect The application requests fails with file-system error 594. See Appendix B, for information on the specified error. For more information on this error, see the DSM/Tape Catalog Management Programming Manual. Recovery Specify a device in the TAPECATALOG DEFINE attribute and retry the application. |
| 676 Error 1018 - Pool pool is out of scratch tapes, will retry | ||
Cause The pool specified in the TAPECATALOG DEFINE attribute is out of scratch tape volumes that match the appropriate type. Effect The request cannot continue until more scratch tapes are made available. Recovery Either add more scratch tapes of the correct type, or use the MEDIACOM command, DELETE TAPEFILE, to free some tape volumes. $ZSVR automatically retries the operation. The request continues automatically when more scratch tapes are made available. |
| 677 Error 1019 - FILESECT specified is incorrect |
Cause The FILESECT attribute specified in the TAPECATALOG DEFINE attribute is incorrect. Effect The application request fails with file-system error 594. Recovery Correct the FILESECT attribute and retry the operation. See Appendix B, for information on the specified error. For more information on this error, see the DSM/Tape Catalog Management Programming Manual. |
| 678 Error 1020 - Volume volser not used for FILEID fileid | ||||
Cause The volume name specified in the TAPECATALOG DEFINE attribute was not used for the specified FILEID. Effect The application read request fails with file-system error 594. Recovery Either correct the volume name of the TAPECATALOG DEFINE attribute or let Distributed Systems Management/Tape Catalog (DSM/TC) automatically choose an appropriate tape volume. See Appendix B, for information on the specified error. For more information on this error, see the DSM/Tape Catalog Management Programming Manual. |
| 679 Error 1021 - Volume volser cannot be used, selecting alternate | ||
Cause The volume name specified in the DEFINE attribute cannot be used. Distributed Systems Management/Tape Catalog (DSM/TC) automatically selects an alternate tape volume. If multiple volumes were specified in the DEFINE attribute, the next name is tried first. Effect The operation continues automatically. Recovery If no alternate should be used, reject the request. Otherwise, informational message only; no corrective action is needed. |
| 680 Error 1022 - Volume volser is not assigned, selecting alternate | ||
Cause The volume name specified in the DEFINE attribute cannot be used. Distributed Systems Management/Tape Catalog (DSM/TC) automatically selects an alternate tape volume. Effect The operation continues automatically. Recovery If no alternate should be used, reject the request. Otherwise, this is an informational message only; no corrective action is needed. |
| 681 Error 1023 - Need volume specified if writing multi-file sets |
Cause The volume name must be specified in the TAPECATALOG DEFINE attribute when writing multifile volume sets (FILESEQ > 1). Effect The application request fails with file-system error 594. Recovery The volume name must be specified and the volume specified must be either the first volume in the volume set, or include the last volume used in the volume set. Retry the request with the corrected DEFINE attribute. See Appendix B, for information on the specified error. For more information on this error, see the DSM/Tape Catalog Management Programming Manual. |
| 682 Error 1024 - FILESEQ for FILEID fileid is incorrect | ||
Cause The FILESEQ attribute specified in the TAPECATALOG DEFINE attribute for the file identification is incorrect. Effect The application request fails with file-system error 594. Recovery Correct the FILESEQ attribute and retry the operation, or let Distributed Systems Management/Tape Catalog (DSM/TC) automatically determine the correct FILESEQ attribute by not specifying it in the TAPECATALOG DEFINE attribute. See Appendix B, for information on the specified error. For more information on this error, see the DSM/Tape Catalog Management Programming Manual. |
| 683 Error 1025 - No copy available for FILEID fileid | ||
Cause A MEDIACOM command, ALTER TAPEMOUNT, was attempted and no alternate copy is available. Effect The application continues to request that the original tape volume be mounted. Recovery Mount the originally requested tape volume, or reject the request and start the request over with a different physical copy. |
| 684 Error 1026 - No mount seen for volser on device | ||||
Cause A tape successfully mounted by the tape cartridge is not being detected by the tape drive. The possible reasons for this error are:
Effect The OPEN operation fails and file-system error 595 is returned. Recovery Correct the problem with the tape drive and retry the operation. If the problem cannot be corrected, use the Subsystem Control Facility (SCF) STOP TAPE command (for G-series RVUs) or PUP DOWN (for D-series RVUs) the tape drive to stop the NonStop system from using the tape drive for automated cartridge system tapes. See Appendix B, for information on the specified error. For more information on this error, see the DSM/Tape Catalog Management Programming Manual. |
| 685 Error 1027 - Error num on DSM/TC console device | ||||
Cause An error occurred while trying to send a message to the Distributed Systems Management/Tape Catalog (DSM/TC) console (using the MEDIACOM ALTER CONSOLE command). Effect The DSM/TC console is automatically closed. Recovery To reopen the DSM/TC console, use the MEDIACOM ALTER CONSOLE command.See Appendix B, for information on the specified error. |
| 686 Error 1028 - Connection to device failed with error num | ||||
Cause An error occurred while trying to communicate with a tape drive. Effect The tape drive is unavailable for labeled tape use. If a MEDIACOM STATUS TAPEDRIVE command is performed, it shows the tape drive as being unavailable. Recovery See Appendix B, for information on the specified error. Connection to the tape drive is retried automatically as follows:
If the error persists, contact your service provider and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 687 Connection to device completed successfully |
| 688 Error 1029 - Tapefile tapefile terminated abnormally | ||
Cause An application using a tape drive terminated without calling CLOSE. This message occurs only when processing Distributed Systems Management/Tape Catalog (DSM/TC) controlled tape volumes. Effect ABENDRETENTION is used instead of the normal retention. Recovery To change the retention from the ABENDRETENTION value, use the MEDIACOM ALTER TAPEFILE command. |
| 689 ERROR 1515 - CONNECTION TO TPTM COMPLETED SUCCESSFULLY |
| 690 ERROR 1030 - CONNECTION TO TPTM FAILED WITH ERROR error | ||
Cause The connection to the Third Party Tapes Manager (TPTM) failed with file‑system error error. Effect The TPTM is not configured. If the Distributed Systems Management/Tape Catalog (DSM/TC) level is integrated, all labeled tape requests fail until the TPTM is successfully configured. Recovery Correct the problem and restart the TPTM interface. If the problem cannot be immediately corrected and labeled tape processing must continue, set the DSM/TC level to MEDIACAT and follow the TPTM instructions for handling catalog synchronization. |
| 691 ERROR 1031 - SEVERING CONNECTION TO TPTM |
| 692 ERROR 1032 - TPTM REJECTED REQUEST WITH ERROR error |
| 693 ERROR 1033 - TPTM REJECTED LABELING REQUEST WITH ERROR error |
| 694 ERROR 1034 - TPTM RETURNED ERROR error, CONTINUING REQUEST |
| 695 WARNING 909 - volser ON ERROR device DOES NOT ALLOW REQUESTED DENSITY/TAPEMODE | ||||
Cause The requested and actual tape density or tape mode did not match. The requested tape volume is mounted on the tape drive that does not support the requested DENSITY/TAPEMODE. $ZSVR selects only tape drives that support the requested DENSITY/TAPEMODE. Effect The mount request is unsatisfied. Recovery Correct the DEFINE to either specify DENSITY/TAPEMODE or specify the correct DENSITY/TAPEMODE, and retry the operation. Note that if DSM/TAPE CATALOG is not being used (via CLASS TAPECATALOG DEFINEs), the tape volumes are automatically selected to match the specified DENSITY or TAPEMODE. |
| 696 ERROR 1035 - NO TAPE FOUND IN CORRECT ACS FOR device, WILL RETRY | ||
Cause After the Transaction Management Facility (TMF) catalog was queried 20 times, no tape was found in the appropriate ACS for this request. Effect In three minutes, the request will retry automatically. Recovery An operator can either use the MEDIACOM ALTER TAPEMOUNT mount‑sequence command to force a retry before the three minutes are up or issue a MEDIACOM REJECT TAPEMOUNT mount-sequence command to reject the request. No action is needed to allow the request to retry automatically. |
| 697 ERROR 1036 - ALTER TAPEMOUNT mount-sequence FAILED WITH ERROR error-num | ||||
Cause An error was returned from the Transaction Management Facility (TMF) catalog when a MEDIACOM ALTER TAPEMOUNT mount-sequence command was attempted. Error-num contains the error number returned from the TMF catalog. The possible values are:
Effect The ALTER TAPEMOUNT command did not succeed. Recovery Correct the problem indicated by the Error-num field and retry the ALTER TAPEMOUNT command. |
| 698 ERROR 1037 - TAPE AUTO SUBSTITUTE FOR define-name, FAILED WITH ERROR error-num | ||||
Cause An error was returned from the TMF catalog while $ZSVR was automatically attempting to find a TMF in the appropriate ACS. Error-num contains the error returned from the TMF catalog. The possible values are:
Effect In three minutes, the request will retry automatically. Recovery Correct the problem indicated by error-num error field. An operator can either use the MEDIACOM ALTER TAPEMOUNT mount-sequence command to force a retry before the three minutes are up or issue a MEDIACOM REJECT TAPEMOUNT mount-sequence command to reject the request. No action is needed to allow the request to retry automatically. |
| 699 STATUS 1516 - volser TAPE ON DRIVE device USED BY node.process |
| 700 STATUS 1517 - TAKEOVER BY BACKUP $ZSVR PROCESS STATUS: status | ||
Cause The primary $ZSVR process has stopped and the backup $ZSVR process has successfully taken over. Effect The backup $ZSVR process is now the primary $ZSVR process, and it will create a new backup $ZSVR process. Recovery This is an informative message only; no corrective action is needed. |
| 701 ERROR 1038 - ACCESS DENIED TO ACS TAPE VOLUME volser | ||
Cause The requested ACS tape volume is security protected through the StorageTek server so that this NonStop system is denied access to the tape. Effect The application requesting the tape receives file-system error 48 on the open request. Recovery Restart the application specifying a different ACS tape volume. |
| 702 ERROR 1039 - LOCAL MEDIADBM VERSION IS INCOMPATIBLE WITH $ZSERVER |
| 703 STATUS 1518 - TAPE volser2 USED INSTEAD OF TAPE volser1 | ||
Cause $ZSVR matched a request for volser1to volser2 since volser2 is currently mounted on a tape drive, and is an earlier volume in the volume set than the requested file. Effect The application is about to open the tape drive where volser2 is mounted. Recovery Informational message only; no corrective action is needed. |
| 704 STATUS 1519 - UNREQUESTED ESM TAPE volser ONLINE ON device ALIAS = alias | ||||||
Cause An ESM tape that was not requested is mounted because either:
Effect The tape may be used to satisfy subsequent mount requests. Recovery Make sure the correct tape is mounted and that a mount request is issued. |
| 705 MOUNT ESM volser [REEL reel] [DENSITY density] [ON device] WITH RING ALIAS = alias | ||||||
Cause A tape file was opened for output for ESM processing, but the tape was not mounted. Effect The operation waits for the tape with the requested ESM volser to be mounted (on drive, if specified). Recovery Either mount the specified tape (on drive, if specified) with no write protection or reject the request using the MEDIACOM REJECT TAPEMOUNT command. |
| 706 MOUNT ESM volser [REEL reel] [DENSITY density] [ON drive] NO RING ALIAS = alias | ||||||
Cause A tape file was opened for input for ESM processing, but the tape was not mounted. Effect The operation waits for the tape with the requested ESM volser to be mounted (on drive, if specified). Recovery Either mount the specified tape (on drive, if specified) with write protection or reject the request using the MEDIACOM REJECT TAPEMOUNT command. |
| 707 ERROR 1040 - TPTM WRITEREAD ERROR: error |
| 708 ERROR 1041 - TPTM REQUEST TIMED OUT: drive |
| 709 ERROR 1042 - TPTM IS NOT CONFIGURED, REQUEST ABORTED |
Cause One or more of the following can be the cause of this error:
Effect The application's request for TPTM services is aborted and file-system error 751 is returned to the application. Recovery If a third-party tape manager is to be used:
If a third-party tape manager is not to be used:
|
| 713 STATUS 1520 - ACS DRIVE device is busy, will retry the continuation | ||
Cause When DEVICE is specified in DEFINE, during a tape switch, BACKUP may reopen the DEFINE internally before the previous dismount operation is completed. Effect After a tape switch, BACKUP does not proceed until the drive completes the previously initiated dismount operation. After the drive is free, the BACKUP operation completes. Recovery This is an informational message only; no corrective action is needed. |
| 992 $device-name smd command abort on request, LDEV $logical‑device-number |
| 993 $device-name smd command abort on request, LDEV $logical‑device-number |
| 1008 $device-name error-injection, LDEV $logical-device-number |
| 5101 $device-name I/O EXCEPTION ERROR, LDEV $logical‑device‑number, SAC: sac-name, SYNDROME %hexadecimal-value syndrome ON SCSI COMMAND SCSI-command. | ||||||||||
Cause An XIO I/O operation was terminated after it was issued. |