Chapter 8. Problem Determination Procedures

This chapter describes how to determine when a problem has occurred in the library and the actions necessary to resolve the problem.

See Table 11 for quick reference to particular conditions.

Quick Reference Table to Problem Determination Procedures

 

Table 11. Quick Reference to Problem Determination procedures

 

 

 

 

Conditions

Reference

 

 

Library Manager failures in a DFSMS/MVS

ªLibrary Manager Failure in a DFSMS/MVS

environment (includes HA1 Switchovers)

Environmentº on page 261

 

 

Library Manager failures in an MVS/BTLS

ªLibrary Manager Failure in an MVS/BTLS

environment (includes HA1 Switchovers)

Environmentº on page 265

 

 

 

 

Reported via a host console message

ªDFSMS System Managed Tape Messagesº

 

 

on page 268

 

 

 

 

Intervention Required on Library Manager

ªIntervention Required Conditions and

 

System Summary or SNMP OPINT trap

Actionsº on page 282

 

message

 

 

 

 

 

Disruption of services or physical damage to

ªVirtual Tape Server Recovery Actionsº on

 

a site with a Virtual Tape Server.

page 302

 

 

Import/Export List Volume status codes in

ªAppendix B. Virtual Tape Server

the status ®le

Import/Export Advanced Functionº on

 

page 307

 

 

 

When a problem occurs in the library or associated tape subsystems, completion of one or more library operations may not be possible. This topic provides information on how to identify problems, what is their signi®cance to continuing operations in the library, and what actions to take for recovery.

Several symptoms indicate that a problem occurred with the library and/or associated tape subsystems. These symptoms are in the following general categories:

1.One or more jobs that require volumes in the library are not progressing or completing as expected. The possible causes are:

v The workload demand on the library exceeds its capability. For example, the number of requests to mount volumes on drives in a library received in a period exceeds the number the library can process during that period. The result is that the requests stay in the library manager queue for a longer period before being performed. Although this is not a problem with the library, if this is occurring on a regular basis, workload balancing must be addressed.

vA failure of a component in the library is causing degraded performance. Library operations are performed, but are slower to complete because of the failure. For example, when one of the two grippers fails, all operations continue with the other gripper, but take longer to complete than when both grippers are functional. Service is required to correct the problem.

vThe library or attached tape subsystems detected a failure or exception condition that is preventing one or more library operations from completing. The library reports the condition to the host for operator or service

© Copyright IBM Corp. 1993, 1999

259

Page 281
Image 281
IBM Magstar 3494 manual Quick Reference Table to Problem Determination Procedures, Conditions Reference