General Library Statistics
The following statistics may help you trouble shoot and diagnose a problem situation with a library component:
|
Statistics |
Description |
|
Number of IPLs |
Number of times the machine was booted. |
|
Number of Door Opens |
Number of times the library door has been opened. |
|
Uptime Seconds |
How long the library has been online. |
|
Moves |
Number of successful sets of get/put operation. A single move consists of one get and one put operation. |
|
Mounts |
Number of successful put operations to a drive. |
|
Empty Reads |
Number of times an empty cell was detected. |
|
Cap Gets |
A count of the number of times a get was executed from the CAP. |
|
Cap Puts |
A count of the number of times a put was executed to the CAP. |
|
Get Retries |
Number of times a get operation required a retry operation. A single move will have two retries before failing. |
|
Get Failures |
Number of times a get operation failed. For every failed get operation, there will be two get retries logged. |
|
Put Retries |
Same as get retries, except for put operations. |
|
Put Failures |
Same as get failures, except for put operations. |
|
Label Retries |
Same as get retries, except for label reading operations. |
|
Label Failures |
Same as get failures, except for label reading operations. |
|
Label Reads |
Number of time a cartridge label was read. |
|
Target Retries |
Same as get retries, except for targeting operations. |
|
Target Failures |
Same as get failures, except for targeting operations. |
|
Target Reads |
Number of times targeting operations succeeded. |
Job rate intervals are set to 5 and 15 minutes to better understand peak machine usage.
For example, one customer may only require peak machine performance for a time of less than five minutes. So, some electromechanical components may not heat sufficiently to cause short or long-term reliability issues. On the other hand, another customer may require peak performance for a full 15 minutes or more. Peak performance for such long periods generally indicates that components will reach higher operating temperatures, and in turn require more costly components.
Defines the hourly drive job rate the library was given during a continuous five-minute intervals. For instance, if 13 mounts were executed during one five-minute interval, the 151 to 175 usage bin would be incremented by 1 (13 mounts/ 5 minutes x 60 minutes/hour = 156 mounts per hour). If no mount activity takes place during a five-minute interval, the idle bin is incremented by one.
|
Statistics |
Description |
|
Idle |
No mounts in a five-minute interval |
|
1 to 25 |
One to two mounts in a five-minute interval |
|
26 to 50 |
Three to four mounts in a five-minute interval |
|
51 to 75 |
Five to six mounts |
|
76 to 100 |
Seven to eight mounts |
|
101 to 125 |
Nine to 10 mounts |
|
126 to 150 |
11 to 12 mounts |
|
151 to 175 |
13 to 14 mounts |
|
76 to 200 |
15 to 16 mounts |
|
201 to 225 |
17 to 18 mounts |
|
226 to 250 |
19 to 20 mounts |
|
251 to 300 |
21 to 25 mounts |
|
201 to 350 |
26 to 29 mounts |
|
351 to 400 |
30 to 33 mounts |
|
401 to 450 |
34 to 37 mounts |
|
451 to 500 |
38 to 41 mounts |
|
501 to 550 |
42 to 45 mounts |
|
551 to 600 |
46 to 50 mounts |
|
601 to 650 |
51 to 54 mounts |
|
651 to 700 |
55 to 58 mounts |
|
Over 700 |
More than 58 mounts in a five-minute interval |
Defines the hourly drive job rate the library was given during continuous fifteen-minute intervals. For instance, if 31 mounts were executed during one fifteen-minute interval, the 101 to 125 usage bin would be incremented by 1 (31 mounts/ 15 minutes x 60 minutes/hour = 124 mounts per hour). If no mount activity takes place during a fifteen-minute interval, the idle bin is incremented by one.
|
Statistics |
Description |
|
Idle |
No mounts in a 15-minute interval |
|
1 to 25 |
One mount in a 15-minute interval |
|
26 to 50 |
Two or three mounts in a 15-minute interval |
|
51 to 75 |
Four to five mounts |
|
76 to 100 |
Six mounts |
|
101 to 125 |
Seven to eight mounts |
|
126 to 150 |
Nine to 10 mounts |
|
151 to 175 |
11 mounts |
|
76 to 200 |
12 to 13 mounts |
|
201 to 225 |
14 to 15 mounts |
|
226 to 250 |
16 mounts |
|
251 to 300 |
17 to 20 mounts |
|
201 to 350 |
21 to 23 mounts |
|
351 to 400 |
24 to 26 mounts |
|
401 to 450 |
27 to 30 mounts |
|
451 to 500 |
31 to 33 mounts |
|
501 to 550 |
34 to 36 mounts |
|
551 to 600 |
37 to 40 mounts |
|
601 to 650 |
41 to 43 mounts |
|
651 to 700 |
44 to 46 mounts |
|
Over 700 |
More than 47 mounts in a 15-minute interval |
A count of the number of times a get was executed from the CAP, with bins incremented when the CAP is opened. This gives an indication of how the CAP is being used. Counts in the 21+ bin would indicate that the CAP is being used for normal operations, not just import operations.
|
Statistics |
Description |
|
Idle |
Cap was opened with no gets since the last open |
|
1 |
One get was executed between opens |
|
2 |
Two gets were executed between opens |
|
3 |
Three gets |
|
4 |
Four gets |
|
5 |
Five gets |
|
6 - 10 |
Six to 10 gets |
|
11 - 15 |
11 to 15 gets |
|
16 - 20 |
16 to 20 gets |
|
21 - Maximum |
Over 21 gets |
A count of the number of times a put was executed to the CAP, with bins incremented when the CAP is opened. This gives an indication of how the CAP(s) is being used. Counts in the 21+ bin would indicate that the CAP is being used for normal operations, not just export operations. This could happen, for instance, if more than 20 mount/dismount diagnostics were executed from the CAP, or if the CAP cells were used as storage elements for an extended period of time, having multiple mount/dismount operations processed with them.
|
Statistics |
Description |
|
Idle |
Cap was opened with no puts since the last open |
|
1 |
One put was executed between opens |
|
2 |
Two puts were executed between opens |
|
3 |
Three puts |
|
4 |
Four puts |
|
5 |
Five puts |
|
6 - 10 |
Six to 10 puts |
|
11 - 15 |
11 to 15 puts |
|
16 - 20 |
16 to 20 puts |
|
21 - Maximum |
Over 21 puts |