StorageTek Host Software Component 6 User Manual

1st ed., 6/30/04 - 312579601

operations that do result in an error, only those that requested robotic motions are logged 
as hard fails with the appropriate indicator set in the record. Errors that do not represent 
failed robotic motions are software errors. These should be analyzed and reported to 
StorageTek. 

In a single-host environment, there is only one SYS1.LOGREC data set and only one copy 
of the HSC. In such an environment, everything is straightforward and easy to manage.

Recommended procedures in this environment are: 

• Offload SYS1.LOGREC to a history data set, and 
• Follow Computer Associates’ CA-9/R+ Installation Instructions. 

The extracted data for the reporting period may then be sent to the reliability measuring 
service for inclusion in their industry-wide report. 

Data are interpreted differently in a multi-host environment than in a single-host 
environment. For this reason more explanation is necessary. 

Since the LMU counts robotic motions started and temporary errors by LSM and not by 
host, when any host requests ACS statistics from an LMU, the data that is written to 
SYS1.LOGREC in an LLG6 record represents the total robotic motions started and 
temporary errors that occurred on each LSM since the last time that any R+ host requested 
ACS statistics from the LMU. The robotic motions started by all hosts are consolidated 
into one LLG6 record. 

However, the robotic motions that end in a hard fail that are reported in LLG1 records are 
only logged to the SYS1.LOGREC of the R+ host that experienced the hard fail. Software 
failures are similarly logged only by the host that experienced the failure (an LLG1 record 
without the ‘‘hard fail’’ indicator). 

Follow Computer Associates’ published procedures for extracting data from all R+ hosts 
from the LOGREC history tapes and send the extracted data for the reporting period to the 
reliability measuring service for inclusion in their industry-wide report.