DS8000 Service Documentation Version 7.5

MAP1110 SIM generation and interpretation for z/OS

SIM generation for the storage facility is no longer intended as a mechanism to provide notification of the need for service, as it was for earlier generations of IBM DASD. SIMs are provided only to support notification for automated-operations monitoring functions that some customers have put in place.

About this task

The strategy for SIM presentation is as follows:

For non-media events, the SIM will be offloaded as a Unit Check on the next IO operation to any device in each Logical SubSystem (LSS).
For media events, the SIM is to be offloaded on the next IO operation to the reporting device within the LSS.
Unlike previous products, SIM offload will not be repeated.
Unlike 2105, the SIM ID is not the same as the Problem Number in the Problem (Serviceable Event).
SIM reporting level can be altered from the HMC. See MAP1110 Section-1 Changing the SIM reporting levels.

Use Table 1 for access to additional tasks and information in this MAP.

Table 1. MAP1110 Section reference
Task or information	Section
Changing the SIM Reporting levels	MAP1110 Section-1 Changing the SIM reporting levels
Repair Using a SIM Console Message	MAP1110 Section-2 Repair using a SIM console message
SIM Sense Reference Information	MAP1110 Section-3 SIM sense reference information
SIM Media Maintenance Procedures	MAP1110 Section-4 SIM media maintenance procedures

MAP1110 Section-1 Changing the SIM reporting levels

About this task

The SIM reporting is set to the following default levels:

Table 2. SIM reporting levels
Type	Sense switch description	Level
Hardware non-DDM	CU Threshold	2
Hardware DDM	Device Threshold	2
Media	Media Threshold	0

Table 3. Definition of reporting thresholds:
Threshold level	Report to Operator
0	All SIMs
1	Acute, Serious and Moderate severity SIMS
2	Acute and Serious severity SIMs
3	Acute severity SIMs only
4	None

If the customer requests that SIM reporting thresholds are modified from the default values, then perform the following steps.

Procedure

Change the SIM reporting levels.

From the navigation area, click Storage Facility Management > storage facility > SF image.
From the bottom Task area, select Service Utilities > Enable/Disable Control Switches.
Use the previous tables to set the SIM threshold reporting levels to the values requested by the customer.
Click Set.
Click OK in the message box, then click Cancel to exit.

MAP1110 Section-2 Repair using a SIM console message

About this task

The storage facility maintenance strategy does not rely on the analysis of data in environmental recording, editing and printing (EREP) reports, or sense bytes on the console. Sense data records for some storage facility temporary and all permanent errors are sent from the storage facility to the system to give information necessary to perform needed system error recovery procedures. The storage facility sense data is logged in the error-recording data set (ERDS) in the system, but is not used for storage facility problem determination.

Unlike ESS, the SIM ID is not the same as the Problem Number in the Problem (Serviceable Event). Correlation of SIMs to Serviceable Events can be done only by comparison of Reference Codes and timestamps.

MAP1110 Section-3 SIM sense reference information

About this task

The refcode Format is SSSS-SSSS-0009 for HW SIMs, SSSS-SSSS-0082 for Media SIMs, where SSSS-SSSS is the SRC. The refcode is created from SIM sense byte data as shown in Table 4. For details about the refcode, see the Decode a refcode chart directly below Table 4.

Table 4. Storage facility SIM Sense bytes for hardware SIMs
Sense Byte	Meaning	Value
11-13	Ref Code Bytes 2-4	Third through fifth byte of refcode.
14	Ref Code Bytes 5- Procedure Number	x'09' = other types
15-19	Product Serial Number	nnnnnnnn
20-21	Subsystem Identifier (SSID)	Subsystem ID for the LSS
22-23	RefCode Bytes 0-1	First and second byte of refcode
28	SIM type	FE

Decode a refcode chart

00    03 04    07 08    11 12    15 16    19 20    23 24    27 28    31 
xxxxxxxx 00xxxxxx xxxxxxss ssss0009 nnnnnnnn SSIDssss xxxxxxx FExxxxxxx
                              |                   |           |
                              |______________     |           |       
                                    _________|____|           |
                                    |        |                |
                            Refcode ssss-ssss-0009          FE=Hardware SIM

Table 5. Storage facility SIM Sense bytes for Media SIMs
Sense Byte	Meaning	Value
4	Device Physical Address	Second byte value of Device Address or otherwise x'00'
11-13	Ref Code Bytes 2-4	Third through fifth byte of refcode.
14	Ref Code Bytes 5- Procedure Number	x'09' = other types
15-19	Product Serial Number	nnnnnnnn
20-21	Subsystem Identifier (SSID)	Subsystem ID for the LSS
22-23	RefCode Bytes 0-1	First and second byte of refcode
28	SIM type	FE
29-31	Logical cylinder and head	x'cccchh'

Decode a refcode chart

00    03 04    07 08    11 12    15 16    19 20    23 24    27 28    31    
xxxxxxxx ddxxxxxx xxxxxxss ssss0082 nnnnnnnn SSIDssss xxxxxxxx FFcccchh
          |                   |                   |            |
          |                   |______________     |            |       
          |                         _________|____|            |
          |                         |        |                 |
   Device address                Refcode ssss-ssss-0082       FF=Media SIM

MAP1110 Section-4 SIM media maintenance procedures

About this task

The customer must perform media maintenance to recover from Media Errors. Instruct the customer to perform the media maintenance procedure indicated in Table 6.

Table 6. Media Maintenance Procedure
Procedure Number	Description	ICKDSF Commands
2	The first part of this procedure finds all tracks with unrecoverable data and supplies information on the allocation of the user data (for example, dataset names).	Use ICKDSF Release 16 or higher. Enter the following commands: IODELAY SET MSEC(100) See note 1 below. ANALYZE <UNIT() DDNAME()> NODRIVE SCAN See note 2 below.
2	The second part of this procedure returns the indicated track to a usable condition. Data on this track has been lost. All subsystem attempts at media maintenance have been unsuccessful. All attempts to recover the data have been unsuccessful.	See Table 2 for the location of the SRC and addresses of the failing track and head (cccchh) in the sense information. For each track that reports an SRC of: BE504910, BE504920, BE504910, BE504920 Issue the following command (all on the same line): INSPECT <UNIT()DDNAME()> <VFY()NOVFY>ASSIGN NOCHECK NOPRESERVE TRACK(cccc,hh) See note 3 below. Note: The above ICKDSF inspect command will result in the loss of all customer data on that track.

Notes:

IODELAY adjusts ICKDSF to run concurrently with customer operations.
ANALYZE scans the volume for data that is not readable or not usable.
The NOPRESERVE parameter must be specified for the DS8000®. The PRESERVE parameter is not valid for the DS8000. All previous attempts by the subsystem to recover the data have not been successful. Although the track will be returned to a usable state, all customer data on the specified track will be lost when the INSPECT command is run.

For additional information see MAP5240 Customer data check.