BST01ARI: Initializing subsystem and security environment

BST01ARI: Initializing subsystem and security environment

Overview

BST01ARI initializes the subsystem environment and security environment of a subsystem. BST01ARI must have run before you can start the STC.

The BST01ARI call can be included in the IEFSSNxx entry or SETSSI command that defines the subsystem to z/OS. Or you can call BST01ARI in a batch job or the STC procedure.

BST01ARI in batch job or STC

Use this syntax when calling BST01ARI in a batch job or the STC procedure:

//stepname EXEC PGM=BST01ARI,
// PARM='ssid,parmlib(member)'

where ssid is the Beta nn subsystem ID. The EXEC parameter specifies the BnnSSIxx member in the BETA.PARMLIB, which contains the parameters to be used by BST01ARI (see "Parameters for BST01ARI in BnnSSIxx").

Example

//stepname EXEC PGM=BST01ARI,
// PARM='B92T,BETA.PARMLIB(B92SSI01)'

If ssid not defined

If BST01ARI runs in a batch job or STC procedure and detects that the specified 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").

Reinitialize environment

If you have to run BST01ARI to reinitialize the subsystem, for example, because the security exit has been changed, you must stop the started task first before running BST01ARI.

Address space

The complete initialization functionality is supported when BST01ARI runs in a batch job or the STC procedure.

No additional address space is created.

RACF authorization for BST01ARI

Use the following profile in the RACF facility class to protect BST01ARI against unauthorized access:

BETA.INIT.ssid

where ssid is the subsystem ID.

The following RACROUTE is issued when a user calls BST01ARI to initialize a subsystem that has been defined to z/OS:

REQUEST=AUTH,CLASS='FACILITY',ACCESS=READ

If this profile is not defined, the result depends on your security system. RACF is typically set up to allow the requested action anyway, but returns a warning. In this case, BST01ARI initializes the subsystem and ends with RC=4.

The following RACROUTE is issued when a user calls BST01ARI to define and initialize a subsystem:

REQUEST=AUTH,CLASS='FACILITY',ACCESS=ALTER

If this profile is not defined, BST01ARI ends with RC=16.

Return codes of BST01ARI

0

The program terminated normally

4

The program terminated with a warning. Possible reasons are:

  • Profile BETA.INIT.ssid has not been defined
  • A module which was specified could not be loaded, because it was not found or because it was not in an authorized library
  • FREEMAIN failed

8

The program terminated abnormally due to parse error. Statements in member IEFSSNxx are not correctly coded.

12
  • The program terminated abnormally because GETMAIN failed.
  • The SVC you have specified is invalid for Beta products. The corresponding SVC entry for the subsystem is deleted.

16

The program terminated abnormally. Possible reasons are:

  • ENQUEUE failed (for example, started task was active)
  • DYNALLOC or OPEN error (for example, parameter dataset or member not found)
  • ESTAE failed (recovery)
  • BST01ARI and BST01SSI are not authorized.

20

The program abended.

Parameters for BST01ARI in BnnSSIxx

Member BnnSSIxx in the BETA.PARMLIB contains a set of parameters for the program BST01ARI. These parameters can be coded as shown in the table below. See the product documentation for details on which parameters are to be used and how to use them.

Parameter

Description

Option

UXSRT

Security router (module name must be BST00STH)

required

UXSEC

Security user exit module

Specify UXSEC=IEFBR14 if the security exit is not required.

optional

UXSIN

Security user exit module for logging onto a subsystem

If security is not required, simply do not code this parameter. Do not attempt to switch it off with IEFBR14, as this will return a warning. (Exception: BOF)

optional

SVC

Beta SVC number

required

XCF

YES activates XCF functionality

See also Installation and System Guide of the product concerned.

optional

XCF_PROD

Two-digit product identifier of the subsystem

This parameter is required if XCF = YES. See also Installation and System Guide of the product concerned.

optional

XCF_GBAS

Enables the use of the BSA XCF Global Connect component

See also Installation and System Guide of the product concerned.

optional

GOTO_OCF

Enables communication between an XCF sysplex and an external system

See also Installation and System Guide of the product concerned.

optional

ROUTE_TO

Automatically reroutes requests to the specified subsystem

See also Installation and System Guide of _beta access and _beta doc|z.

optional

SUBSYS

Specifies the name of the subsystem interface program

The subsystem interface program ensures that jobs using the subsystem interface do not end abnormally when the subsystem is not available, but remain in wait status until the subsystem is started.

See also _beta doc|z Installation and System Guide.

optional

FSSM

Specifies the functional subsystem module

See also _beta doc|z Installation and System Guide.

optional