Before you can start a Beta nn started task:
You can include the BST01ARI call in the entry or command that defines the subsystem. Or you can define the subsystem first and then run BST01ARI some time later (but before the start of the STC).
Use the profile BETA.INIT.ssid in the RACF facility class to protect BST01ARI against unauthorized access (see "RACF authorization for BST01ARI").
The subsystem can be defined to z/OS at IPL or dynamically. There are several options:
If you include the BST01ARI call in your IEFSSNxx entry, the subsystem is defined and initialized at IPL. Note: BST01ARI must be available in the linklist.
Alternatively, you can create an IEFSSNxx entry without this call and run BST01ARI later.
If you include the BST01ARI call in your SETSSI command, the subsystem is defined and initialized when you run the command. Note: BST01ARI must be available in the linklist.
Alternatively, you can submit the SETSSI command without this call and run BST01ARI later.
If BST01ARI detects that a subsystem has not been defined, it defines this subsystem ID to z/OS and then initializes the subsystem environment and security environment. Note: This is protected by higher security (see "RACF authorization for BST01ARI").