162 VM/HSC 6.0 System Programmer’s Guide
1st ed., 6/30/04 - 312579601
Notes:
1. The job name in the startup SLKJCL file must match the subsystem name specified
with the LIBSUBSYS parameter in the SYSPROF or it must be specified with the
SSYS parameter in the /PARM statement. Refer to “SSYS” on page 158 for more
information.
2. Control data sets are defined using the CDSDEF control statement. The CDSDEF
statement must be present in your PARMLIB definitions. Control and journal data
sets may no longer be defined in JCL. Refer to ‘‘CDS Definition (CDSDEF) Control
Statement’’ in the HSC System Programmer’s Guide for more information.
3. The number of CDS copies used by the HSC is dependent on the number of CDS
copies defined in the CDSDEF PARMLIB control statement. It is not determined by
the TCHNIQE parameter of the LIBGEN SLIRCVRY macro. 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).
4. Journals are defined using the JRNDEF control statement. The JRNDEF statement
must be present in your PARMLIB definitions if you want to use journaling. Journal
data sets may no longer be defined in JCL. Refer to ‘‘Journal Definition (JRNDEF)
Control Statement’’ in the HSC System Programmer’s Guide for more information.
5. If journaling is specified by the TCHNIQE parameter of the LIBGEN SLILIBRY
macro, journals must be defined in your PARMLIB definitions for successful HSC
initialization.
Description of /FILE Statement
The following is a description of the JCL /FILE statement used in the example job for the
ACS INIT command.
SLSSYSXX
statement that defines the sequential data set or PDS member containing the
PARMLIB definitions.