The parameters are:
- ADD
- Directs that a subsystem be added dynamically.
Note
that with the exception mentioned in the next paragraph, you cannot
specify in a SETSSI ADD command a subsystem initialization routine
in a library added in a new LNKLST that was activated after IPL.
A job that is already running does not normally use a new LNKLST.
Because the SETSSI command runs in the MASTER address space, which
started at IPL, it does not normally use a new LNKLST.
There
is an exception to the above. You could use a SETPROG LNKLST,UPDATE,ASID=1
command to update the LNKLST prior to issuing the SETSSI ADD command. However, you should use that SETPROG command with caution, because
you would be depending on it to complete execution prior to the running
job's accessing the updated LNKLST.
- DEACTIVATE | DEACT
- Specifies that a subsystem is to be dynamically deactivated.
DEACTIVATE stops any new requests from being passed to the subsystem's
function routines. Function requests that are already processing
are allowed to complete. Note that a subsystem is still defined to
the system, even if you issued the DEACTIVATE parameter.
Only subsystems
with SSI-managed vector tables can be reactivated
with the SETSSI command. SSI-managed vector tables are vector tables
that were created with the IEFSSVT macro. See z/OS MVS Programming: Authorized Assembler Services Reference EDT-IXG for more information on the IEFSSVT macro.
Note: You can only issue the DEACTIVATE command if the target
subsystem is dynamic and permits the use of the SETSSI command.
- ACTIVATE | ACT
- Specifies that a subsystem is to be dynamically activated. You
can also use the ACTIVATE command to reactivate a previously deactivated
subsystem provided a vector table managed by the SSI is available.
Note: You can only issue the ACTIVATE command if the target subsystem
is dynamic and permits the use of the SETSSI command.
- SUBNAME | SUB | S=subname
- Specifies the subsystem name to be dynamically added, deactivated
or activated.
Subsystem names that are not enclosed in apostrophes
may contain any character that is valid for operator commands, with
the following exceptions:
- , comma
- ( left parenthesis
- ) right parenthesis
- / slash
- = equals sign
Subsystem names containing these characters must be enclosed
in apostrophes.
Subsystem names that contain any character
that is not valid for operator commands must be enclosed in apostrophes.
See MVS system commands reference for a list of characters supported by commands.
Note
that the SUBNAME parameter applies to the ADD command, DEACTIVATE
command, and the ACTIVATE command. For the SETSSI ADD command, note
the following when selecting subsystem names:
- If you specify a subsystem name with the characters ‘*’
and ‘?’, the DISPLAY SSI command or the IEFSSI REQUEST=QUERY
service specifying that subsystem name may return information about
subsystems other than this one. The ‘*’ and ‘?’ are
treated as wildcard characters for these services.
- If you specify a subsystem name of ‘!PRI’, the DISPLAY
SSI command or the IEFSSI REQUEST=QUERY service specifying that subsystem
name returns information about the primary subsystem, even though
there is already a subsystem named ‘!PRI’.
- CONSNAME | C=consname
- Specifies the name of the console to which SSI issued messages
are routed. CONSNAME is an optional parameter. It can be 2- to 8-bytes
long and is also passed to the routine named on the INITRTN keyword
(if specified).
- INITRTN | I=initrtn
- Specifies the name of the subsystem initialization routine.
INITRTN is an optional parameter. It can consist of at most eight
characters, beginning with an alphabetic or national ($, #, or @)
character. The remaining characters can be either alphanumeric or
national ($, #, or @). The routine receives control in supervisor
state key 0. It must be a program that is accessible through a LINKLIB
or the LPALIB.
- INITPARM | P=initparm
- Specifies the input parameter that is passed to the subsystem
initialization routine. INITPARM is an optional parameter. It can
be no more than 60 characters long. If you use delimiters such as
blanks, commas, apostrophes, equal signs, or parentheses or a ‘/’
in the parameter data, you must enclose the entire field in apostrophes.
You must code two consecutive apostrophes to pass an apostrophe as
part of the parameter data.
Note: The INITPARM parameter
must be specified with the INITRTN parameter. If the INITRTN is not
specified, the system issues a syntax error message and the command
is not processed.
Note: - In the command invocation, anything after the first blank is treated
as a comment.
- The command invocation cannot be more than 126 characters long.
You may need to use the 1-character keyword abbreviations to keep
the length of the command invocation within this limit.
Example 1:
To define the ‘CAW’ subsystem to the system, call its initialization
routine and pass the specified parameter to the initialization routine,
enter:
SETSSI ADD,SUBNAME=CAW,INITRTN=CAWINIT,INITPARM=HELLO
Example 2:
To temporarily stop new function requests to the subsystem to see
if one of the function routines in the ‘CAW’ subsystem is
causing abends, enter:
SETSSI DEACTIVATE,SUBNAME=CAW