StorageTek 6 Restore, JCL Requirements, Only, Short, Slsprint, Slscntl, SLSCNTL2, SLSJRNnn, Slsin

Restore

Note: If OPTion(Analyze) was specified for backup, this parameter should be specified for the restore.

(Only)

specifies that all statements are sent to the SLSAUDIT data set. The CDS and Journal /FILE statements need not be present. The control data sets are not restored.

(Short)

specifies that Audit statements only are sent to the SLSAUDIT data set. The control data sets are restored.

JCL Requirements

The following definitions apply to RESTore utility JCL:

SLSPRINT

output messages from the utility program.

SLSCNTL

the primary control data set.

SLSCNTL2

the secondary copy of the CDS (optional).

Note: SLSBKUP the backup data set. SLSSTBY a standby copy of the control data set having only the heartbeat block updated (optional).

SLSJRNnn

if journaling is enabled, statements that define all journals since the last backup. There are two journals per host and up to 16 hosts. The possibility exists that the journals could have been off-loaded since the last control data set backup. If so, all archived journals must also be specified here.

It is the user’s responsibility to specify the archived journals, since there are no means of checking for missing archived journals. There is also no provision for specifying more than 99 journals. Allowable values for nn are 01 to 99, but numbers cannot be skipped.

SLSAUDIT

identifies where the UNSCratch, UNSElect, and AUDIt statements are to be placed. SLSAUDIT has a logical record length (LRECL) of 80 and a block size (BLKSIZE) of 80. These statements are in the optimal order and can be directly input to an execution of SLUADMIN. The data set name specified in SLSAUDIT can be used as

SLSIN

input to SLUADMIN. This is a PUNCH file.

278VM/HSC 6.0 System Programmer’s Guide

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