(Subsystem 121)

Only the user-specified length of data was transferred; however, the DEVICE MANAGER attempted to transfer more for some reason.

User requested a data transfer, but the buffer supplied was zero bytes long.

Call your support representative.

UNLOCK Request was received; however, the DEVICE MANAGER was already unlocked.

Diagnostics attempted to UNLOCK the Device Manager unnecessarily.

Call your support representative.

RELEASE is ALLOWED for operator requests; therefore, the disk pack is allowed to be dismounted.

The front panel button used to spin down a disk pack is disabled.

None.

RELEASE will be denied for operator requests; therefore, the disk pack can not be dismounted.

The front panel button used to spin down a disk pack is disabled.

None.

A DEVICE UNLOCK was requested, but the device was not locked.

Device reservation for exclusive access was removed unnecessarily.

None.

DEVICE LOCK was requested, but the device was already locked by this host.

Device reservation for exclusive access attempted, but it was already granted.

None.

A bit in the CS80 Hardware status information field was set for which there is no value defined.

Device returned an undefined Warning/Info status.

Call your support representative.

The device missed a revolution during this transfer.

Occurs normally on occasion.

None.

The bit in the CS80 hardware status was set, which indicates that the logs on the device are full.

Error logs in the device are full.

Call your support representative.

The bit in the CS80 hardware status was set, which indicates that the data in this transfer was corrected by the device.

Data was recovered with little difficulty.

None.

The bit in the CS80 hardware status was set, which indicates that the data was corrected by the device with difficulty.

Data was recovered, but sector should be spared.

Call your support representative.

The bit in the CS80 Hardware status was set, which indicates that the data was corrected in more than one sector during this transfer. The sector number in the error log is of the first corrected one, only.

Data was recovered, but sectors should be spared.

Call your support representative.

The bit in the CS80 hardware status was set, indicating that a defective sector was AUTOMATICALLY SPARED by the device.

Device performed automatic sparing. Data was recovered.

None.

The bit in the CS80 hardware status was set, indicating that a LATENCY in the data transfer occurred.

Additional rotation of spindle needed.

None.

The bit in the CS80 hardware status was set, indicating that only one spare track remains on the disk.

Excessive sparing has been necessary with this media.

Call your support representative.

The bit in the CS80 hardware status was set, indicating that the device is requesting release to perform head alignment. The DEVICE MANAGER will grant.

Automatic head alignment/diagnostics was performed.

None.

The bit in the CS80 Hardware status was set, indicating that the diagnostic frontpanel was manipulated causing a REQUEST for RELEASE.

User activated front panel diagnostics.

Verify by looking at front panel.

The bit in the CS80 hardware status was set, indicating that the operator button was pushed, causing a REQUEST for RELEASE.

User attempted to spin-down disk pack.

Either push button back in, or remove pack.

An error occurred previously which caused the request to be RETRIED by the DEVICE MANAGER. The retry was SUCCESSFUL.

I/O was retried.

None.

The DOBIND was successful. However, the DEVICE ADAPTER MANAGER is of an incorrect revision.

Software versioning problem.

Call your support representative.

The DOBIND was successful. However, the initialization of hardware received a TIMEOUT.

Device did not respond when initialization was attempted.

Depends if device is supposed to be powered on.

The DOBIND was successful. However, the initialization of hardware received a DEVICE ERROR.

Device responded with an initialization error.

Call your support representative.

The subsystem number in the received message was incorrect, usually during configuration.

Configuration problem.

Verify your configuration and call your support representative.

A BIND request was received, but already was bound.

Configuration problem.

Verify your configuration and call your support representative.

Data received from LOOPBACK did not match original data.

Hardware problem during loopback test.

Call your support representative.

A request was received which requires the manager to be locked, but it is not locked.

Diagnostics attempted destructive test on unreserved device.

Call your support representative.

An UNBIND request was received to UNBIND from incorrect HIGHER MANAGER port number.

Unconfiguration process problem.

Call your support representative.

A DO_UNBIND request was received with the incorrect LOWER MANAGER port number.

Unconfiguration process problem.

Call your support representative.

The memory request to RELEASE MEMORY (during Die request processing) failed.

System software response problem.

Take a system dump.

An attempt to UNBIND failed due to pending I/Os from an external requester, or attempt to DO_UNBIND failed due to any pending I/Os for this manager.

Unconfiguration inhibited as device busy.

Try again. If the error persists, call your support representative.

Update of the BAD SECTOR TABLE (which lists all sectors which should be spared because the manager detected recoverable or unrecoverable read errors) failed.

Hardware problem or power failure during Bad Sector Table update.

Call your support representative.

BIND of this manager to the DEVICE ADAPTER MANAGER failed.

Initialization of lower level (Device Adapter, etc.) failed.

Examine configuration file. Call your support representative.

An attempt to acquire memory for auxiliary data area failed.

System software resource exhausted.

Take a system dump.

An attempt to acquire a message frame failed.

System software resource exhausted.

Take a system dump.

Bad parity detected in data transfer.

Fiber-optic connected disk has bad parity over fiber link.

Call your support representative.

User's buffer is incorrect for the request; either not present, nil pointer, or (for LOOPBACK only) not a virtual buffer.

System problem.

Call your support representative.

An attempt to spare a block resulted in unexpected data errors in the new block.

Device verifies new sector during spare. Detected new sector was also bad.

Call your support representative and try sparing block once again.

Request was cancelled by an abort.

May have been caused by a power failure.

None.

A TIMEOUT has occurred, indicating that the drive is not talking to the manager.

Device was not responding.

Check device and cabling; may be due to a power failure.

A request was made of the manager, but the manager is currently LOCKED by another higher manager (usually DIAGNOSTICS).

Device accessed by diagnostics.

Terminate "sysdiag" session; try again.

An internal table entry in this manager was inconsistent; couldn't get or release the table entry desired.

Software problem.

Take a system dump. Call your support representative.

An attempt to release a MESSAGE FRAME failed.

System software problem.

Take a system dump. Call your support representative.

An attempt to SEND a message failed.

System software resource depleted.

Take a system dump. Call your support representative.

An error bit was set in the ACCESS field of the CS80 hardware status that is undefined.

CS80 device status returned invalid information.

Call your support representative.

Either an error bit in the FAULT field of the CS80 hardware status which is undefined was set, OR the DEVICE ADAPTER MANAGER returned LLIO_HW_PROBLEM status, OR Diagnostics previously set the DEVICE MANAGER state to BROKEN.

May be hardware problem.

Call your support representative.

An error bit in the REJECT field of the CS80 hardware status was set which is undefined.

CS80 device status returned invalid information.

Call your support representative.

An invalid unit number was returned in the CS80 hardware status.

CS80 device status returned invalid information.

Call your support representative.

An invalid QSTAT was returned in CS80 hardware status.

The QSTAT from device was not defined.

Call your support representative.

The DEVICE ADAPTER MANAGER returned a bad status in the status field of the DAM Reply message.

Problem in the device adapter level; could be due to a power failure.

Monitor the process.

Immediate status indicates link protocol or port event errors occur.

Fiber-optic connected disk interface problem. Could be due to a power failure.

If problem persists, call your support representative.

An incorrect META language was specified during configuration.

Configuration or software version incorrect.

Call your support representative.

An invalid hardware address was specified during configuration.

Configuration of device address incorrect or out of range.

Examine configuration files.

The disk driver has an internal data structure error.

Critical software resource problem.

Take a system dump. Call your support representative.

The INTERNAL TABLE is inconsistent.

Software problem.

Take a system dump. Call your support representative.

The DEVICE MANAGER received a request which it could not understand OR is not currently supported.

The application attempted an inappropriate action for the device.

Take a system dump and call your Hewlett-Packard Service Representative.

A message was received which is inappropriate for the current DEVICE MANAGER state, (e.g., an I/O request prior to DOBIND).

Software problem.

Call your support representative.

The transaction was aborted due to SYSTEM POWERFAIL.

Power failure occurred while transaction was active.

None.

The CYCLIC REDUNDANCY CHECK of the data transaction failed.

Transmission problem; possible cabling problem.

Verify cabling; call your support representative.

The ALINK DEVICE ADAPTER is indicating the fiber-optic link is non-functional, possibly due to a power failure.

Fiber-optic connected disk interface broken. Maybe due to power failure.

Monitor the process; if problem persists, call your support representative.

The error bit in the CS80 hardware status was set, which indicates an attempt to access beyond the END OF VOLUME.

Addressed block beyond volume range.

Should not occur with single volume devices. Call your support representative.

The error bit in the CS80 hardware status was set, which indicates an attempt to access beyond an END OF FILE.

A file mark was detected; should not occur on disks.

Call your support representative.

The error bit in the CS80 hardware status was set, which indicates an UNRECOVERABLE DATA ERROR. The sector number is entered into the BAD SECTOR TABLE.

Data was lost due to bad sectors.

Call your support representative.

The error bit in the CS80 hardware status was set, which indicates more than one sector had UNRECOVERABLE DATA ERRORS. The first bad sector number is placed in the BAD SECTOR NUMBER.

Data was lost due to bad sectors.

Call your support representative.

The error bit in the CS80 hardware status was set, which indicates an attempt to read UNITIALIZED DATA.

Data uninitialized at address location.

Call your support representative.

The error bit in the CS80 hardware status was set, which indicates an attempt to write to a "READ ONLY" device.

Device does not allow writes.

Verify the device is active. Call your support representative.

The error bit in the CS80 hardware status was set, which indicates the heads are NOT LOADED as yet.

A transient not ready condition existed.

Power on the device. Call your support representative.

The error bit in the CS80 hardware status was set, which indicates an attempt to SPARE FAILED due to no more spare sectors available.

Spare command failed.

Call your support representative.

The error bit in the CS80 hardware status was set, which indicates an attempt to access UNFORMATTED MEDIA.

Disk was not initialized.

Call your support representative.

The error bit in the CS80 hardware status was set, which indicates that the CS80 protocol requested too many operations at one time.

Software problem or cabling problem.

Call your support representative.

The error bit in the CS80 hardware status was set, which indicates that the device requires the I/O to be tried again.

Device required I/O; usually due to auto head alignment.

None.

The error bit in the CS80 hardware was set, which indicates the device has had power re-applied or the heads have re-loaded.

Device powered-on; head loaded.

None.

The error bit in the CS80 hardware status was set, which indicates that the device needs to align its heads or run internal diagnostics (RELEASE REQUIRED).

Device determined that automatic head alignment was required; performed same.

None.

The error bit in the CS80 hardware status was set, which indicates that the diagnostic frontpanel on the device was accessed (RELEASE REQUIRED).

Device allowed front-panel diagnostics to be executed.

Determine if front panel was accessed.

The error bit in the hardware status was set, which indicates that the operator unload button was pushed (RELEASE REQUIRED).

Device allowed the operator to spin-down pack.

Either push button back in, or remove pack.

The error bit in the hardware status was set, which indicates a HARDWARE FAULT detected by internal diagnostics.

Device diagnostics detected hardware problem.

Call your support representative.

The error bit in the CS80 hardware status is set, which indicates that a HARDWARE FAULT occurred in the addressed unit of the device.

Could be hardware problem, or a transient problem due to power-on.

Call your support representative.

The error bit in the CS80 hardware status was set, which indicates that a HARDWARE FAULT occurred in the device controller.

Device hardware problem.

Call your support representative.

The error bit in the CS80 hardware status was set, which indicates that an error occurred during a transfer of data between 2 units in the device (COPY DATA CS80 Command only).

This should never occur as this feature is not supported.

Call your support representative.

The error bit in the CS80 hardware status was set, which indicates the execution phase length is not as expected. A REJECT error occurred; could be cabling.

CS80 transaction was incorrect; could be cabling.

Verify that cabling is correct and call your support representative.

The error bit in the CS80 hardware status was set, which indicates that the CS80 Command bytes were out-of-sequence. A REJECT error occurred; could be cabling.

CS80 transaction was incorrect; could be cabling.

Verify that cabling is correct and call your support representative.

The error bit in the CS80 hardware status was set, which indicates that the parameter field of the CS80 Command is invalid. A REJECT error occurred; could be cabling.

CS80 transaction was incorrect.

Verify that cabling is correct and call your support representative.

The error bit in the CS80 hardware status was set, which indicates that the value in the PARAMETERS of the CS80 Command is too large. A REJECT error occurred; could be cabling.

CS80 transaction was incorrect.

Verify that cabling is correct and call your support representative.

The error bit in the CS80 hardware status is set, which indicates that the value in the ADDRESS field in the CS80 Command is illegal. A REJECT error occurred; could be cabling.

CS80 transaction was incorrect. The medium address range was exceeded.

Verify that cabling is correct and call your support representative.

The error bit was set in the CS80 hardware status was set, which indicates that CS80 Command Volume or Unit is illegal. A REJECT error occurred; could be cabling.

CS80 protocol was incorrect. The device address range was exceeded.

Verify that cabling is correct and call your support representative.

The error bit in the CS80 hardware status was set, which indicates that the OPCODE of the CS80 Command bytes is invalid. A REJECT error occurred; could be cabling.

CS80 command bytes could be invalid.

Verify that cabling is correct and call your support representative.

The error bit in the CS80 hardware status is set, which indicates the PARITY of the CS80 Command bytes is bad. A REJECT error occurred; could be cabling.

The device detected a parity error.

Verify that cabling is correct and call your support representative.

Immediate status returned, indicating the HOST targeted for this I/O did not respond.

Fiber-optic disk detected lack of host communication.

Verify connection and try again. If problem persists, call your support representative.