Obtaining drive error information from HP-UX system
The HP-UX system does not provide error logs for analysis. Therefore, you must use the device diagnostic
tests and Device Error Log for problem determination. See “CE Logs menu (CE Offline Mode)” on page
133. When you locate a FID, go to “Maintenance starting point” on page 1.
See “TAPEUTIL in HP-UX system environment” on page 269 for information about the host attachment
software service tool tapeutil for HP systems.
Refer to the IBM Tape Device Drivers Installation and User's Guide for information about HP/UX service
and diagnostic aids.
Obtaining drive error information from Windows system
See “TAPEUTIL in Windows system environment (NTUTIL) ” on page 275 for information about the host
attachment software service tool tapeutil for Windows systems.
Refer to IBM Tape Device Drivers Installation and User's Guide for information about Windows service and
diagnostic aids.
Running NTUTIL
If ntutil is running and an error condition is detected, an error message is displayed. The error sense data
has the format that is seen in Figure 30 on page 71. The err 0 ERROR_SUCCESS>, or error number, is
explained in “NTUTIL symbolic error and error number” on page 71.
enter selection: 39
Scsi status: 02h/Sense information Length 60h
Sense KEY/ASC/ASCQ = 02/3a/00
KEY meaning is: not ready
Sense Info - - - consult SCSI spec for details
00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
------------------------------------------------------------
0000 - 70 00 02 00 00 00 00 58 00 00 00 00 3a 00 86 02
0010 - C4 08 00 00 00 00 01 40 00 00 00 00 00 00 0A 00
0020 - 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0030 - 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0040 - 00 00 00 00 00 00 00 00 32 46 31 20 20 20 20 00
0050 - 00 00 00 50 51 52 39 35 30 00 00 00 00 00 00 00
analyze <> called with rc 1 err 0 <ERROR_SUCCESS> data 0
total elapsed time in seconds = 0.00
Return to continue:
HEX ASCII DESCRIPTION
86 FID (FRU identification number) Byte 14
C408 FSC (fault symptom code) Bytes 16 and 17
324631 2F1 Microcode level, Bytes 72-74
505152393530 VOLSER# in ASCII or EBCDIC
Figure 30: NTUTIL error sample
For further information on gathering error data, refer to the IBM Tape Device Drivers Installation and
User's Guide and the IBM Tape System 3592 Hardware Reference. On certain errors, an
ntutil
test_unit_ready
command (39) must be issued to display the sense information. Sense information
can also be retrieved with a
Log_sense
command (83).
NTUTIL symbolic error and error number
--------------------------------------------------
| Symbolic Error | NT Error Number |
|--------------------------------|-----------------|
| ERROR_SUCCESS | 0 |
| ERROR_INVALID_FUNCTION | 1 |
Messages 71
