StorageTek 6 manual Logging Interval

Table 68. Record Format for a Hard Failure (Continued)

Motion Hard Fail Software Error Record

BYTE #	Description of Field
62-67	VOLSER of cartridge (this field is only valid if
	Request type, byte 59, is ‘B’, ‘C’, ‘D’ or ‘E’
	and byte 60 has value character ‘1’)
68-89	Proprietary data
90-91	Host ID
92-94	Sequence number
95-95	Character ‘7’ indicates an error response
96-96	Response type,
	‘B’ = Mount response
	‘C’ = Dismount response
	‘D’ = Swap response
	‘E’ = Move response
	‘K’ = Catalog response
	‘X’ = View response
97-100	LMU Response Code (see Appendix A for
	definitions)
101-102	LSMid in error
103-112	Proprietary data
113-113	Character ‘H’ indicates a hard failure
114-641	Reserved
642-643	Record type X’6501’
644-647	StorageTek identifier X’FEEDFACE’
648-651	Timestamp

Logging Interval

When LMU 3.0 or 9315/9330 1.0 µ-software is properly installed in the ACS, the HSC identifies hard fails in LLG1 records and records robotic motion and temporary error counts in LLG6 records written to SYS1.LOGREC.

An LLG6 record is written to SYS1.LOGREC for each qualified ACS at the same interval that is defined for writing ACS-specific SMF records. A record is written not less than once in 24 hours, and always when the HSC is shutting down normally (assuming it has not been canceled).

An LLG1 record, which may or may not represent a hard fail, is written to SYS1.LOGREC for most operations requested by the HSC for which the LMU is unable to complete the HSC request. Operations that are automatically retried by the HSC are usually not errors, and some other states may be defined that are not logged as errors. See “LMU Response Codes” on page 611 for information on error and response codes. For

Appendix D. Logging ACS Robotics Motion 609

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