Sun StorageTek VSM System
 
Sun StorageTek VSM5 System
 

PLA-Support>Sun Systems>TAPE>Virtual Tape>SN-TP: VSM
 

In this Document

Goal

Solution

Applies to:

Goal

 This document illustrates various ways a VSM reports sense bytes in error messages

Solution

 
FIRST WAY:

THE VTSS is reporting a condition with the machine itself.
The SIM will always be presented to the operator in a SLS6659I message.
These are reported back as SIM messages:
The format is 32 sense bytes with the Error Code being in positions 22 & 23.
The SN (in HEX) of the machine that generated the sense bytes is in SN 17, 18, 19.
If the machine took a state save , the specific FSC might be in sense bytes 30 & 31.
EXAMPLE:
10.08.26 STC06954 .SLS6659I VTSS VSM1
SIM:00 00 10 00 00 00 8F E0 11 10 00 00 20 00 3E 10 42 00 00 9B 00 01 7596 04 10 42 03 F1 FF 8E4A
00 10 17 22 30
The FSCs can be looked up in the FSC dictionary. In this example the FSC is 7596 or
warm boot complete. For certain warmboots, the exact FSC of the warmboot is in SBs 30 & 31. In this case the FSC of the warmboot was an 8E4A.
If the Error Code (SB 22 & 23) is 7359, VTCS will follow the SLS6659I message with a SLS6974I message with additional data (if any exists) plus recommendations (if possible).

SECOND WAY:

VTD is reporting a problem with the VTV.
These are the sense bytes coming back from the VTD to the host. These are like any other 3490 type device.
The main FSC is in bytes 10 & 11. There could be other sense bytes in 12&13 14&15.
Note: This could be a VTSS or a tape drive (9840, T10k, etc) FSC.
EXAMPLE:
IOS000I 1E7C,9D,EOD,3F,0600,,**,261992,SMFDUMP 934 934 00000090
08400036401DA9200033(00C9020000000000)0000(000000C9)0E8C01201478CC00
00 03 07 10
In this example the primary FSC is 00C9 and the secondary one is 0200.
Other numbers of interest:
SB 03 is the EREP (Error Recovery Procedure Action) code.
SB 07 is the sense byte format code(will be 19, 20 ,21).

THIRD WAY:

The RTD is reporting a problem with itself or the MVC cartridge currently mounted on it.
The sense byes are reported to the console via VTSS then VTCS.
They are attached to a SLS6625E message.
They will be preceded by a SLS6684I message containing a CC/RC number
EREP code in byte 03
FSC from the tape drive(not VTSS) in bytes10 & 11
EXAMPLE:
This is a problem with the tape cartridge:
SLS6684I RTD RTD0CE1 ON VTSS VT30 RETURNED ECAM ERROR CC=5 RC=108
SLS6625E RTD RTD0CE1 REPORTED WRITE DATA CHK:
0A4420 25 436B96200700 39DB CE0E3224240000FF
00 03 10 11
The FSC is a 39DB
The EREP code is 25.
EXAMPLE:
This is a problem with the tape drive:
SLS6625E RTD DAL443F4 REPORTED DRIVE EQU CHK:
100020354340B4202000 2001 000000000000000000000000CE0E322115120000
00 1011
FSC = 2001 drive is running out of specifications. Normally the drive reset itself.

This solution has no attachment