Overview

Before beginning to install Adabas Audit Data Retrieval, please read the following pre-installation checklist. This checklist includes the following:

• Hardware requirements for Adabas Audit Data Retrieval
• Software requirements for Adabas Audit Data Retrieval
• Information that will be requested from you when running the installation REXX

The installation process will be shortened and made easier if this information is available before you begin. Please contact your system administrator if you need any site-specific information, for example, the names of system libraries (PROCLIB etc.) that can be used to receive Adabas Audit Data Retrieval data.

Hardware requirements

Adabas Audit Data Retrieval requires the following:

• IBM z/Series (z/Architecture).

OS requirements

Adabas Audit Data Retrieval requires the following:

• z/OS 2.3 or later with IBM SORT

  To install and run Adabas Audit Data Retrieval requires the following components, which must be compatible with your release of z/OS:

  • SMP/E
  • TSO/E
  • ISPF and ISPF/PDF
  • DFSORT (64 bit) or Syncsort (64 bit)
  • SMS (required for archiving to DASD)
  • RACF (or an equivalent security system, for example, ACF2)
  • VTAM (for multi-CPU operation only)
  • TCP/IP (for communication with Adabas Audit Viewer)

Software requirements Beta Systems products

Adabas Audit Data Retrieval V7R2 requires the following:

• BSA V7R2
• Beta 23 V7R2 (Beta Browser and other shared functions)

Refer to the Release Notes and Update Instructions for information on additional requirements, for example PTFs.

License requirements

A valid license is required. For details, see "License check handling" in BSA Installation and System Guide.

Information needed for installation REXX

The installation REXX will request the following information:

1. The following information on Adabas Audit Data Retrieval distribution and target libraries:

   Library	SMS or Volume/Unit	High-level qualifier
   Distribution library
   Target library

   Note: Specify the type of DASD units (9345, 3390, 3380 or 3350) and the volume names if you do not use SMS. You can use the same or different volumes for distribution and target libraries.

   When referring to Adabas Audit Data Retrieval installation libraries and databases, the Adabas Audit Data Retrieval documentation uses generic hlq or BETA97 as high-level qualifier. Choose your own leading qualifiers in accordance with the naming conventions of your data center.

2. The following information on the Adabas Audit Data Retrieval databases (default size in brackets):

   Database	SMS or Volume/Unit	Size in cylinders	High-level qualifier for cluster
   hlq.SYNC		1
   hlq.INDEX1		(100)
   hlq.GLOBL1		(100)
   hlq.CACHE1		(100)
   hlq.SPOOL1		(20)
   hlq.RELOD1		(20)
   hlq.MAIN		(20)
   hlq.MAIN.KEY		(10)
   hlq.LIST		(20)
   hlq.LIST.KEY		(20)
   hlq.ARC		(60)
   hlq.ARC.KEY		(25)
   hlq.MSG		(20)
   hlq.MSG.KEY		(10)
   hlq.LOG		(20)
   hlq.NOTES		(10)
   hlq.NOTES.KEY		(5)
   hlq.SFR		(10)
   hlq.SFR.KEY		(3)
   hlq.LGF		(20)
   hlq.LGF.KEY		(10)

   If databases cannot be placed on fail-safe storage (physical mirroring or Raid 5), you can use software mirroring. Make sure that original and mirror database are placed on different volumes.

3. VTAM network ID
   
   
4. A subsystem ID for the Adabas Audit Data Retrieval started task
   
   
5. The name of the PS dataset or PO dataset member that contains your license file
   
   
6. The name of the Adabas Audit Data Retrieval started task procedure
   
   
7. The dataset name of a system procedure library into which the two Adabas Audit Data Retrieval started task procedures will be placed
   
   
8. An unused port number where to listen for incoming requests from Adabas Audit Data View (AAV) and the name of the TCP/IP started task (TCP/IP stack) to be used
   
   
9. An unused SMF user record number between 128 and 255 (128..1151 if version 1) for the writing of SMF records (The SMF record number should be used exclusively for Adabas Audit Data Retrieval SMF records.)
   
   

Space requirements

A minimum of 1182 cylinders of space is required for the Adabas Audit Data Retrieval environment and its database if you want to create a new Adabas Audit Data Retrieval system. Refer to the respective Installation and System Guide to determine the space required for BSA or other products you are using. If you want to modify your space requirements, it can be done in the respective section, during the set up of the Adabas Audit Data Retrieval database.

The following are approximate space requirements for the standard installation of Adabas Audit Data Retrieval on 3390 DASD volumes:

Adabas Audit Data Retrieval target datasets	70 cylinders
Adabas Audit Data Retrieval distribution datasets	70 cylinders
Adabas Audit Data Retrieval databases (not mirrored)	515 cylinders

For more information on space requirements, see "Step 4: Creating a new Adabas Audit Data Retrieval database".

OMVS segment entry required for using TCP/IP

One of the following must be defined in RACF in order to enable the Adabas Audit Data Retrieval or Beta 02 started task to use the TCP/IP stack:

• The Adabas Audit Data Retrieval or Beta 02 started task has a RACF user profile; this user profile contains an OMVS segment.
• The Adabas Audit Data Retrieval or Beta 02 started task has a RACF user profile and uses the default OMVS segment entry (requires READ access to the BPX.DEFAULT.USER facility class).

Using default OMVS segments in USER and GROUP profiles

To set up RACF so that it automatically uses default OMVS segments for users and groups that do not have OMVS segments in their USER or GROUP profiles:

1. Create a FACILITY class profile called BPX.DEFAULT.USER having universal access READ and APPLDATA(defaultuser/defaultgroup).
2. Define a RACF user profile for defaultuser containing an OMVS segment
3. Define a RACF group profile for defaultgroup containing an OMVS segment

Note on APF authorization

The following BSA V7 modules must be loaded from an APF‑authorized library:

BST01ARI BST00ATH BST01CMD BST01MST BST01RFF BST01SFF BST01SSI BST00STH BST01SVC BST01XCF BST00XIN BST09XIN B02UXSIN

Separate BETA.APFLOAD recommended

The installation REXX asks you for the name of the library that you want to use for the modules requiring APF authorization.

Although it is possible to use the same library for authorized and non-authorized modules, using a separate library for authorized modules is recommended. The BSA and product modules requiring APF authorization are automatically placed into this separate library during installation. The standard name of this library is BETA.APFLOAD. See BSA Installation and System Guide for more information on the advantages and disadvantages of using the same or different libraries.

APF-authorized product modules

Some Adabas Audit Data Retrieval modules must also be loaded from an APF‑authorized library, for example, the security exit B97UXSEC.