Defining the subsystem ID to z/OS and initializing the subsystem

Overview

Before you can start a Beta nn started task:

  1. Its subsystem ID must be defined to z/OS.
  2. Its subsystem environment and security environment must be initialized by BST01ARI.

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").

Prerequisites for initialization

  • The required security definitions must be present (see "Security definitions required for subsystem initialization").
  • You must be authorized to run the procedure.
  • The subsystem you want to initialize must not be active.
  • BST01ARI, BST01SSI and the modules specified in the BnnSSIxx member must be in an APF-authorized library link-edited with AC(1). The default name of this library is BETA.APFLOAD. This library must be included in the linklist if BST01ARI is called at IPL or via SETSSI.

IPL or dynamic methods

The subsystem can be defined to z/OS at IPL or dynamically. There are several options:

  • At IPL via an entry in the IEFSSNxx member

    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.

  • Dynamically via SETSSI

    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.

  • Dynamically via BST01ARI

    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").