StorageTek Host Software Component 6.0, Руководство системного программиста

Страница: 246 / 718

216 VM/HSC 6.0 System Programmer’s Guide
1st ed., 6/30/04 - 312579601
summary report and to the SLSBKUP data set. Refer to Figure 11 on page 222
to see a sample discrepancy report. An errant and in-transit destination report,
followed by a block processing report, also is produced in this case. Figure 11
shows these reports.
Note: The VOLSERs and cell locations that are discrepant are sorted into an
incremental stack to reduce the amount of robotic movement.
Up to 10,000 discrepancies can be recorded for the Scratch and Select
discrepancy types; 96,000 discrepancies or one ACS can be recorded for the
Audit discrepancy type. Once these limits have been reached, discrepancy
saving is discontinued. Discrepancies saved prior to reaching the limits are
retained and output.
If you specify this option, normally SLSCNTL represents the current primary
data set; SLSCNTL2 specifies the current secondary data set. However, if you
are recovering from a link down or multi-host switch situation, SLSCNTL
should remain the current primary CDS on one side of the link while
SLSCNTL2 should be specified as the current primary CDS on the other side of
the link. If you are sure which two CDSs should be compared, do not specify
SLSSTBY.
Upon restore, the discrepancy blocks are used to generate UNSCratch,
UNSElect, and AUDIt statements to the SLSAUDIT data set.
Note: It is better to use OPTion(Copy) for regularly scheduled backups of the
HSC CDS. OPTion(Analyze) is designed to backup the CDSs when there may
be discrepancies between copies of the CDS.
(Restart)
specifies to bypass the initial copy of the control data sets to the SLSCOPY data
sets. This option is used when a system outage or job failure has occurred after
the control data sets have been copied to the SLSCOPY data sets. Analysis of
the previous backup run-time report indicates the successful copies.
If you have journals, the report should be inspected to determine if the journals
were successfully reset. If they have not been reset, a backup should be taken
again to obtain the most current control data sets prior to doing the journal
resets.
If the journals have been reset, OPTion(Restart) should be used to obtain the
information from the SLSCOPY data sets.
Backup