Overview

In this step, you define the Adabas Audit Data Retrieval subsystem to z/OS, initialize the Adabas Audit Data Retrieval subsystem environment, and initialize the Adabas Audit Data Retrieval security environment.

Current Beta SVC required

Initialization of the Adabas Audit Data Retrieval subsystem environment and security environment is carried out via the program BST01ARI, which requires the current Beta SVC. For information on specifying and activating the Beta SVC, see the description of installation step 4 in the BSA Installation and System Guide.

Creating an entry in member IEFSSNxx

Create an entry for the Adabas Audit Data Retrieval subsystem in member IEFSSNxx of your SYS1.PARMLIB dataset or another dataset concatenated in the MSTJCLxx or LOADxx member.

Using named parameters, the entry looks like this:

SUBSYS SUBNAME(ssid)
INITRTN(BST01ARI)
INITPARM('BETA.PARMLIB(B97SSIxx)')

Using positional parameters, the entry looks like this:

ssid,BST01ARI,'BETA.PARMLIB(B97SSIxx)'

where ssid is the Adabas Audit Data Retrieval subsystem ID, BST01ARI the program to be executed, and BETA.PARMLIB(B97SSIxx) the parameter member for program BST01ARI.

Note: BST01ARI and the modules specified in member B97SSIxx must exist in an APF-authorized library concatenated in the linklist, link-edited with AC(1). The default name of this library is BETA.APFLOAD.

When IPLing the system, the entry in member IEFSSNxx defines the Adabas Audit Data Retrieval subsystem to z/OS and initializes the Adabas Audit Data Retrieval subsystem environment and security environment via BST01ARI.

Defining subsystem dynamically

Instead of IPLing the system at this point, you can also dynamically define the Adabas Audit Data Retrieval subsystem to z/OS and then initialize the Adabas Audit Data Retrieval subsystem environment and security environment.

To do this:

1. Enter this console command to dynamically define the Adabas Audit Data Retrieval subsystem to z/OS:

   SETSSI ADD,SUBNAME=ssid

   where ssid is the Adabas Audit Data Retrieval subsystem ID. (Note: Do not initialize the subsystem environment in this console command.)

2. Submit the tailored batch job B97INIT (which runs program BST01ARI) to initialize the Adabas Audit Data Retrieval subsystem environment and security environment.

   BST01ARI must run before you start the Adabas Audit Data Retrieval started task.

The following pages of this section provide additional information on the program BST01ARI.

JCL in B97INIT

You can find JCL for BST01ARI in the BETA97.CNTL in member B97INIT.

+-----------------------------------------------------------------------+
|jobcard |
|//INIT EXEC PGM=BST01ARI, |
|// PARM='ssid,BETA.PARMLIB(B97SSIxx)' |
|//* |
|//*STEPLIB DD DSN=BETA.APFLOAD, |
|//* DISP=SHR |
|//* |
|//SYSUDUMP DD SYSOUT=* |
+-----------------------------------------------------------------------+

EXEC parameter for BST01ARI

PARM='ssid,parmlib(parmmember)'

where:

• ssid is the Adabas Audit Data Retrieval subsystem ID
• parmlib is the name of the Beta parameter library
• parmmember is the member containing the parameters for the BST01ARI program

Note on member B97SSIxx

Member B97SSIxx in the BETA.PARMLIB contains a set of parameters for the BST01ARI program. The following parameters are coded:

Parameter	Description
UXSEC=B97UXSEC	Name of the Adabas Audit Data Retrieval security user exit module The default name is B97UXSEC. An IEFBR14-like security user exit module is installed by default, which answers all security requests with RC=0. You can also specify UXSEC=IEFBR14 if the security exit is not required. A sample security exit is provided in source form. If you want to activate security, assemble and link B97UXSEC into the BETA.APFLOAD before you run BST01ARI.
UXSRT=BST00STH	Name of the security router, which calls the product security exit The specified name must be BST00STH.
UXSIN=B02UXSIN	Name of the logon exit (TCP/IP) The BSA logon exit authenticates users that connect to the system via TCP/IP, for example, users of Adabas Audit Viewer (AAV). The default name of the exit is B02UXSIN. We recommend that you do not change this name. Code this parameter in B97SSIxx if the BSA TCP/IP server runs within the Adabas Audit Data Retrieval STC or if you are using the BSA CI. The parameter must be coded in member B02SSIxx if the BSA TCP/IP server runs as a standalone STC (BETA02). For more information, see "BSA TCP/IP server logon exit (B02UXSIN)" in BSA Installation and System Guide.
SVC=nnn	Number of the Beta SVC

Note on APF authorization

BST01ARI, BST00STH, and the security user exit must be in an APF-authorized library. The default name of this library is BETA.APFLOAD. We recommended that you include the BETA.APFLOAD in the linklist concatenation so that BST01ARI can run automatically at IPL. For more information, see "Pre-installation checklist" in BSA Installation and System Guide.

RACF authorization for BST01ARI

To prevent unauthorized access to the program BST01ARI, a RACROUTE is issued when a user submits this batch job. The RACF request is:

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

The entity name is 'BETA.INIT.ssid', where ssid is the subsystem ID coded in the EXEC parameter.

In most cases, BST01ARI will end with RC=4 (warning message because profile is not defined), which is okay.

Return codes of BST01ARI

0	The program terminated normally.
4	The program terminated with a warning. Possible reasons are: The profile 'BETA.INIT.ssid' is not 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.
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) The program BST01ARI is not authorized
20	The program abended.