SUBSYS SUBNAME(subname)
[CONSNAME(consname)]
[INITRTN(initrtn)
[INITPARM(initparm)]]
[PRIMARY({NO|YES})
[START({YES|NO})]]
BEGINPARALLEL- SUBSYS
- The statement that defines a subsystem that is to be added to the system. If more than one SUBSYS statement appears for the same subsystem name, the first statement will be the one used to define the subsystem. The duplicate statements will be rejected with a failure message that is sent to the console.
- SUBNAME(subname)
- The subsystem name. The name can be up to 4 characters long; it must begin with an alphabetic or national character (#, @, or $), and the remaining characters (if any) can be alphanumeric or national.
- CONSNAME(consname)
- The
name of the console to which any messages that the SSI issues as part
of initialization processing are to be routed. This name is optional
and can be 2-8 characters long. This console name is also passed to
the routine named on the INITRTN keyword if it is specified.
The default is to issue messages to the consoles that are receiving the INTIDS routing attribute.
- INITRTN(initrtn)
- The
name of the subsystem initialization routine. This name is optional
and can be 1-8 characters long. The first character can be either
alphabetic or national (#, @, or $). The remaining characters can
be either alphanumeric or national. The routine receives control in
supervisor state key 0. It must be the name of a program accessible
through
LNKLST
. - INITPARM(initparm)
- Input
parameters to be passed to the subsystem initialization routine. The
input parameters are optional and are variable in length for a maximum
of 60 characters. If blanks, commas, single quotation marks, or parentheses
are included in the input parameters, the entire parm field must be
enclosed in single quotation marks. If the parm field is enclosed
in single quotation marks, a single quotation mark within the field
must be specified as two single quotation marks.
The INITPARM keyword can only be specified if the INITRTN keyword is specified.
- PRIMARY({NO|YES})
- Parameter
indicating whether this is the primary subsystem. The primary subsystem
is typically a job entry subsystem (either JES2 or JES3).
This parameter is optional. Initialize the primary subsystem before any secondary subsystem(s) except SMS. If you specify PRIMARY on more than one statement, the system issues message IEFJ008I and defines the second subsystem but ignores the PRIMARY specification.
The IEFSSNxx parmlib member is the only place you can define the primary subsystem. It cannot be defined using the dynamic SSI services IEFSSI REQUEST=ADD macro or the SETSSI ADD command.
The default is NO.
- START({YES|NO})
- Parameter indicating
whether an automatic START command should be issued for the primary
subsystem.
If the parmlib entry for the primary subsystem is START(NO), the operator must start it later with a START command. If the parmlib entry for the primary subsystem does not specify the START parameter, it defaults to START(YES).
The START parameter cannot be specified for a secondary subsystem. If you specify the PRIMARY(NO) parameter, there is no default for the START parameter.
- BEGINPARALLEL
- The statement that indicates that the subsystem initialization
routines specified in SUBSYS statements that follow the BEGINPARALLEL
statement are invoked in parallel to reduce the amount of time it
takes for all subsystems to initialize.
For subsystems that do not support parallel processing, you must ensure that the SUBSYS statement appears before the BEGINPARALLEL statement. For example, for the SMS subsystem definition IGDSSIN, be sure to specify the subsystem definitions before you specify the BEGINPARALLEL statement. For SMS, if you specify BEGINPARALLEL before the subsystem definition, the system issues message IEF009E about potential problems. Note that all initialization routines specified before the BEGINPARALLEL keyword are invoked serially, and all routines specified after the BEGINPARALLEL keyword are invoked in parallel. The BEGINPARALLEL keyword must be specified after the SMS entry.
For the z/OS® Communications Server TNF and VMCF subsystems, you must specify the subsystem definitions before you specify the BEGINPARALLEL statement if the INITRTN parameter is included on the subsystem definitions. For information about starting the TNF and VMCF subsystems, see z/OS V2R1.0 Communications Server: IP Configuration Guide
If you do not specify BEGINPARALLEL, the subsystem initialization routines run serially, and you do not obtain any performance benefits of parallel processing. See the configuration or installation documentation of the subsystem for information about whether the subsystem initialization routines can support running in parallel.
You only need to specify one BEGINPARALLEL statement. If you specify more than one statement, the system issues a message indicating that it is using the first BEGINPARALLEL statement it finds and ignores any other statements. This is also true if you specify multiple concatenated IEFSSxx members with BEGINPARALLEL statements across a sysplex.
You can include any number of records in the IEFSSNxx parmlib member.