Overview

The table in this section shows which additional jobs must run to customize and activate BSA and Adabas Audit Data Retrieval after installing or applying maintenance.

Current Adabas Audit Data Retrieval level

If you want to find out which product level is currently installed in an environment, use online option P.2 or check the startup messages in the JESMSGLG.

Before submitting database update jobs ...

The Adabas Audit Data Retrieval started task(s) that are using this database must be down when running database update jobs. If you have more than one Adabas Audit Data Retrieval subsystem and if these subsystems do not share the same database, you must run the database update jobs for each Adabas Audit Data Retrieval subsystem that has a database of its own.

Customization and activation

		New installation
			Max. RC (stepname if rc<>0)
				Your RC
					Your notes
Define subsystem to z/OS (SETSSI ADD,SUBNAME=ssid)		(X)1 Skip this step if the subsystem ID has already been defined. For detailed information on subsystem initialization and required security definitions, see BSA Installation and System Guide.	n/a
Authorize load libraries		(X)2 Check whether your Adabas Audit Data Retrieval and BSA load libraries need to be authorized (if BETA.APFLOAD concatenated in steplib).	n/a
Update SVC (SVCUPDTE)		(X)3 SVCUPDTE dynamically updates the SVC that you have (re)linked with BSA installation job I#BSAJ11. The most recent SVC level is PBS4215. You can skip this job if your SVC is already up-to-date. The number and level of the active SVC is displayed in startup message IRM9151I. During the SVC update, all BSA and Beta product subsystems that are working with this SVC must be stopped. For detailed information on activating the SVC (IPL or dynamic method), see "Step 4: Specifying authorized functions to z/OS" and "Activating authorized functions (Beta SVC) in z/OS" in BSA Installation and System Guide.	0
Assemble and link B02UXSIN		X4 Run G#02XSIN from the BSA.CNTL to assemble and link B02UXSIN (logon security exit) into the BETA.APFLOAD.	0
Assemble and link B04UXSEC		X5 Run G#04XSEC from the BSA.CNTL to assemble and link B04UXSEC (BSA Service Manager security exit) into the BETA.APFLOAD. Use appropriate RACF definitions and B04UXSEC to protect access to the options and functions of the BSA Service Manager. For detailed information, see "RACF security" in BSA Service Manager Manual.	0
Assemble and link B97UXSEC		X6 The B97UXSEC that is active after installation does not check any security. The source code of a functional security exit is provided in member B97UXSEC in the BETA97.SAMPLIB. Run G#97XSEC from the BETA97.CNTL to assemble and link B97UXSEC into the BETA.APFLOAD. If you are using a modified exit, you have to reapply your modifications to the current source code first. Following is a list of the most recent changes: V7R1-00: New function code added to protect the execution of batch utilities (B97.ssid.BUE.programname)	0
F LLA,REFRESH		X7 Refresh LLA with the following console command if modified libraries are concatenated in the linklist: F LLA,REFRESH	n/a
B97INIT		X	48 RC=4 can be ignored if it is caused by the following warning: SFF9119W PROFILE NOT DEFINED FOR (BETA.INIT.ssid)
B97DBDEF Define/ initialize B97 VSAM clusters		X	0
B97DBFOR Allocate/ initialize B97 VSAM database		X	0
B97DBLOD (table data load)		X9 This job replaces the LGFxxx tables in the database. The data in the LGFxxx tables is used by _beta smf. RC=16 for step LGFDELE is okay if LGFxxx tables don't exist (new installation).	0

Note 1: Define ssid to z/OS

Skip this step if the subsystem ID has already been defined.

For detailed information on subsystem initialization and required security definitions, see BSA Installation and System Guide.

Note 2: Authorize load libraries

Check whether your Adabas Audit Data Retrieval and BSA load libraries need to be authorized (if BETA.APFLOAD concatenated in steplib).

Note 3: SVCUPDTE

SVCUPDTE dynamically updates the SVC that you have (re)linked with BSA installation job I#BSAJ11.

The most recent SVC level is PBS4215. You can skip this job if your SVC is already up-to-date. The number and level of the active SVC is displayed in startup message IRM9151I.

During the SVC update, all BSA and Beta product subsystems that are working with this SVC must be stopped.

For detailed information on activating the SVC (IPL or dynamic method), see "Step 4: Specifying authorized functions to z/OS" and "Activating authorized functions (Beta SVC) in z/OS" in BSA Installation and System Guide.

Note 4: B02UXSIN

Run G#02XSIN from the BSA.CNTL to assemble and link B02UXSIN (logon security exit) into the BETA.APFLOAD.

Note 5: B04UXSEC

Run G#04XSEC from the BSA.CNTL to assemble and link B04UXSEC (BSA Service Manager security exit) into the BETA.APFLOAD.

Use appropriate RACF definitions and B04UXSEC to protect access to the options and functions of the BSA Service Manager. For detailed information, see "RACF security" in BSA Service Manager Manual.

Note 6: B97UXSEC

The B97UXSEC that is active after installation does not check any security.

The source code of a functional security exit is provided in member B97UXSEC in the BETA97.SAMPLIB. Run G#97XSEC from the BETA97.CNTL to assemble and link B97UXSEC into the BETA.APFLOAD.

Note 7: F LLA,REFRESH command

Refresh LLA with the following console command if modified libraries are concatenated in the linklist:

F LLA,REFRESH

Note 8: B97INIT

RC=4 can be ignored if it is caused by the following warning:

SFF9119W PROFILE NOT DEFINED FOR (BETA.INIT.ssid)

Note 9: B97DBLOD

This job replaces the LGFxxx tables in the database. The data in the LGFxxx tables is used by _beta smf.

RC=16 for step LGFDELE is okay if LGFxxx tables don't exist (new installation).