Sun StorageTek 9840 Tape Drive
 
Sun StorageTek T10000 Tape Drive
 

PLA-Support>Sun Systems>TAPE>Tape Hardware>SN-TP: STK T-Series Drive
 

In this Document

Goal

Solution

Applies to:

Goal

 Describe how to find the FSC in a customer log for a T10000 or 9x40 error.

Solution

How to Read SCSI Sense Information - 9x40 and T10000 SCSI Sense Data

Sense data can be found in the application error log (e.g. TSM Activity Log) or the /var/adm/messages file.

Sense breakdown:

Details from the T10000 Fibre Channel Reference (pn E20425).

• Go to the Commands chapter.
• Go to the Request Sense command breakdown in this chapter.
• Look at the Sense Data breakdown.
• Note the following bytes:
  Byte 2 - lower half contains the Sense Key
  Byte 12 - contains the ASC
  Byte 13 - contains the ASCQ
  Bytes 18 to 23 - FSCs (may not be present)

Consult table 3-147 and find the Sense Key/ASC/ASCQ combination from the sense to get a description of the problem.

Use the following error message as an example:

In the example above we have Sense Key = 5, ASC = 1A, ASCQ = 00.  

If you look this up in the table it states: Parameter list length error (mode select or other parameter data was truncated)

Note - in this case no FSC information is available. Bytes 18 - 23 are zero's.

How To Read And Interpret Mainframe Generated Sense Information

======General Information: Reference IOS000I Message Breakdown

Mainframe sense data will be found in an IOS000I Message in SYSLOG regardless of the sense byte format. (3490 or 3590)
3490 Formatted Sense Data

Reference 3490 Hardware Reference

Devices running in 3490 emulation – this includes all RTD's. This sense format typically has “20” in sense byte 7. The FSC's start at sense byte 10 for a total of 4 FSC's. They may be bracketed as shown. All RTD sense will be in this format.

Error received IOS000I 685,61,dck,02,0600, ,**,c81336,dfhsma 0840202341a074200100(37f43cda37f4355b)0000(00000000)ce0e342234360000

Let’s address sense information and how to break it down. In the IBM mainframe world there’s basically two different models that are emulated. One of them was the 3490, and the other is the 3590 device. Let’s review these in chronological order: first the 3490 device because that came out first. Let’s suppose an IOS000I message is displayed on the console. This will be a message found in something called SYSLOG, which logs all the errors in SYSLOG. In this case, go to sense byte seven, which is byte 0,1, 2,3,4,5,6,7, and notice a 20 there. That 20 denote that this is a 3490 device because it is sending back 3490 type sense. If it was a 50, it is probably a 3590 sense, not a 3490. That’s the first clue that this is 3490 sense. If it’s a 3490 sense then the first sense bytes starts in byte 10, so that was 7, 8, 9 10. So these (figure a), 37F4 make up a fault code. Please look up 37F4 FSC. There are four different fault codes, 37F4 is the first one, then 3CDA, then 37F4 again, and the last one is 355B. The way this works is that the first error that it encountered, 37-Fox-4, is fault code that is weighted more heavily than any of the rest. The rest of these have to do with recovery, they’re fault codes that it incurred while it’s doing recovery, so this is the first, second, third and last, although there could be other fault codes between the third and the last. So it should give some indication that it can’t read the tape, it’s a read problem. The 37F4 fault code relates to legacy read problems. So, this could very well be a 9840C drive that’s trying to read a tape written by 9840A or B device.

3590 Formatted Sense Data

Reference the IBM Fibre 3590 manual

For read/write errors on a drive running in 3590 emulation there will be a 50 in byte 7. This designates format 50 sense data. With 3590 sense data the first sense byte is contained in bytes 19 and 20. The second sense byte is in bytes 21 and 22. Only 2 FSCs are available in this sense format. See the reference material for a list of commands available in the 3590 command set.

For format 41, 50, or 60 sense, the first Fault Symptom Code (FSC) will be in Sense Bytes 19 and 20 while the second to last FSC will be in Sense Bytes 21 and 22.

For format 51 sense, the unique device Fault Symptom Code (FSC) may be in Sense Bytes 14 and 15. Bytes 16-21 will contain the EBCDIC Volume Serial Number of the cartridge loaded if the volume serial number can be obtained from the tape or RFID.

This solution has no attachment