Create an appropriate entry in the IEFSSNxx member of your SYS1.PARMLIB if the subsystem is to be defined to z/OS at IPL.
If you include the BST01ARI call in your IEFSSNxx entry, the subsystem is defined and initialized at IPL.
Use this syntax when creating an entry with BST01ARI call in the IEFSSNxx member:
SUBSYS SUBNAME(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 at IPL.
Use this syntax if you only want the subsystem to be defined to z/OS, but without initialization:
SUBSYS SUBNAME(ssid)
Result: The specified subsystem is defined at IPL. You have to run BST01ARI at some later time to initialize the subsystem.
The following example shows an IEFSSNxx entry for a _beta log|z system. The subsystem is defined and initalized at IPL.
SUBSYS SUBNAME(B92P)
INITRTN(BST01ARI)
INITPARM('BETA.PARMLIB(B92SSI00)')
A separate address space is started for initialization by system procedure IEESYSAS when the subsystem is initialized at IPL.
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.