StorageTek 6 Manual Do Utilizador

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

The CDSDEF control statement is required and provides static information to the HSC. 
This information is used by the HSC at initialization and remains for the life of the HSC 
execution. The primary, secondary, and standby control data sets are dynamically 
allocated. The CDSDEF PARMLIB control statement defines which copies of the control 
data set are used while the HSC is running. 

Information used to build the SVC99 parameter lists is acquired from the parameter data 
set. 

If journaling is active, JRNDEF statements must be used (refer to “Journal Definition 
(JRNDEF) Control Statement” on page 92 for more information). 

Control information provided to the HSC by CDSDEF includes:

• the name(s) for HSC control data set(s)

• the DASD volume where the specified CDS resides 

• the unitname for the SVC99 parameter list for CDS allocation 

• switch information controlling the enabling of a standby CDS. 

• The number of CDS copies used by the HSC is dependent on the number of CDS 

copies defined in the CDSDEF PARMLIB control statement. Control and journal 
data sets may not be defined in SLKJCL; the CDSDEF statement must be in the 
PARMLIB definitions. It is not determined by the LIBGEN SLIRCVRY macro 
TCHNIQE parameter. 

• The HSC uses all of the CDS copies defined in the CDSDEF control statement 

(whether this includes more or less CDS copies than are specified by the TCHNIQE 
parameter). However, if journaling is specified by the TCHNIQE parameter, journals 
must be defined for successful HSC initialization. 

Caution: Parameters specified for the CDS definition cannot be changed without a 
complete restart of the HSC on all hosts.