The operator command SETSSI enables you to define a subsystem ID dynamically to z/OS.
If you include the BST01ARI call in your SETSSI command, the subsystem is defined and initialized.
Use this syntax if you want to include the BST01ARI call in your SETSSI command:
SETSSI ADD,SUB=ssid,INITRTN=BST01ARI,INITPARM='parmlib(member)'
where ssid is the Beta nn subsystem ID. The INITRTN parameter specifies the program to be executed (BST01ARI), and the INITPARM parameter specifies the BnnSSIxx member in the BETA.PARMLIB, which contains the parameters to be used by BST01ARI (see "Parameters for BST01ARI in BnnSSIxx").
Result: The specified subsystem is defined and initialized when you run the command.
Use this syntax if you only want the subsystem to be defined to z/OS, but without initialization:
SETSSI ADD,SUB=ssid
Result: The specified subsystem is defined when you run the command. You have to run BST01ARI at some later time to initialize the subsystem.
The following example shows a SETSSI command for a _beta log|z system. The subsystem is defined and initalized when you run the command.
SETSSI ADD,SUB=B92T,INITRTN=BST01ARI,INITPARM='BETA.PARMLIB(B92SSI01)'
A separate address space is started by system procedure IEESYSAS when the subsystem is initialized via the SETSSI command.
The start command is as follows:
IEESYSAS.BETAssid,PROG=BST01ARI,PARM='ssid,parmlib(member))'
The address space has the name BETAssid. Among other things, this procedure ensures that the specified parmlib member can be in a library that can be held in the user catalog and it can be on a migrate volume.
It is not possible to use SETSSI to activate or deactivate an existing subsystem that was already defined to z/OS beforehand.