Filter
Top Products
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
environment (includes HA1 Switchovers)
“Library Manager Failure in a DFSMS/MVS
Environment” on page 261
Library Manager failures in an MVS/BTLS
environment (includes HA1 Switchovers)
“Library Manager Failure in an MVS/BTLS
Environment” on page 265
Reported via a host console message “DFSMS System Managed Tape Messages”
on page 268
Intervention Required on Library Manager
System Summary or SNMP OPINT trap
message
“Intervention Required Conditions and
Actions” on page 282
Disruption of services or physical damage to
a site with a Virtual Tape Server.
“Virtual Tape Server Recovery Actions” on
page 302
Import/Export List Volume status codes in
the status file
“Appendix B. Virtual Tape Server
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 significance 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.
v A 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.
v The 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
|
|
|
|
|
|
|
|
|