How to Determine the FSC from the Sense Bytes in Message SLS6659I

Asset ID:	1-71-1014781.1
Update Date:	2017-06-13
Keywords:

Solution Type Technical Instruction Sure

Solution 1014781.1 : How to Determine the FSC from the Sense Bytes in Message SLS6659I

Applies to:

Sun StorageTek Virtual Tape Control Software (VTCS) - Version 6.2 and later
Sun StorageTek VSM System - Version 3.0 and later
Sun StorageTek VSM5 System - Version All Versions and later
IBM z/OS on System z
***Checked for relevance on 03-Jan-2014***

Goal

This document describes how to find what problem is indicated by the sense bytes in the SLS6659I message.

Solution

Message SLS6659I is issued by the VTCS software to indicate that there is a SIM message pending on the VTSS.

From the sense bytes in the message (the long string of numbers/letters), a fault symptom code (FSC) can be obtained. This FSC can then be looked up to determine what problem the VTSS is reporting.

The FSC is made up of the four characters that comprise sense bytes 22 and 23. There are two characters per sense byte. To locate the FSC in the sense bytes, start counting the sense bytes from 0:

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 73 51 00 00 00 00 00 00 00 00

In the above simplified example, the FSC is 7351 which indicates the VTSS attempted to dial home but that failed.

Another example:

SLS6659I VTSS VTSS11 SIM:0010100000008FE0111000009F003E1041000BBA0000759605104202F1008EE9

In this example, the FSC is 7596 which indicates a warm boot completed on the VTSS. Also, additional sense bytes (30 and 31) can further clarify the problem. In this second example, bytes 30/31 indicate FSC8EE9 which is a VIM inventory error for a VIM build failure.

If a search of MOS knowledge does not provide detail regarding the particular FSC, please open an issue in MOS for further investigation. Oracle's StorageTek hardware support will be able to determine the meaning of the FSC.

Internal Comments
FSC Lookup is an internal tool that is not accessible to the customer.
Tech Review history
Audited/updated 03/16/2010 - [regina.hodel@oracle.com], Mainframe SW Content Team - retrieved from archive and updated to meet standards and clean up the examples.
Previously Published As STKKB6275

Attachments

This solution has no attachment