Pre-installation checklist

Overview

Before you begin the installation of Beta Systems Architecture, read through the following pre-installation checklist. The checklist tells you what information you will need during the installation process. The additional information required to install one of the Beta products can be found in the Installation and System Guide for that particular product.

Naming conventions

BSA and product dataset names used BSA and product documentation are used as examples only. You can choose names as you wish throughout the installation procedure.

Upgrading BSA V6 and Beta Systems V6 products

BSA V7 and Beta Systems V7 products require:

  • A new CSI
  • A new profile
  • The BSA V7 SVC

You cannot use an existing V6 CSI, V6 profile, or V6 SVC for BSA V7‑based products.

BSA components

The installation REXX of a product includes only the BSA components that are used by this product. Beta 23 is only included if it is used by the product. Use the setup program of the product that includes all shared components that you need in your environment.

 

Beta23
(Browser)

Beta07
(BOF)

Beta09
(VDF)

Beta11
(CAF)

Beta12
(IAF)

Beta14
(VPF)

_beta access V7

–

–

X

X

X

–

_beta access monitor V7

X

–

–

–

–

–

_beta check|z V7

X

–

–

–

–

–

_beta log|z V7

X

–

X

X

X

–

_beta doc|z V7

X

X

X

X

X

X

_beta doc|z plus V7

X

–

X

X

X

–

_beta doc|z transform V7

X

–

X

X

X

–

_beta move V7

X

–

–

–

–

–

Note: _beta browse (Beta23) is not a BSA component, but it is installed in the BSA libraries because its functions are used by more than one Beta product.

Checklist

You can make the installation process shorter and easier by obtaining the following information beforehand.

  1. For transfer of installation files to z/OS:
    • High-level qualifiers to be used by the extract job when setting up the libraries that will be used later in the installation process
  2. If you do not use System Managed Storage (SMS), the following information is needed:
    • The type of DASD units you want to use for installation libraries.
    • The volume names on which the distribution libraries, target libraries, and SMP/E datasets are to be allocated. Different volumes can be used for the distribution libraries, target libraries and SMP/E datasets.

      - Target libraries:

      - Distribution libraries:

      - SMP/E datasets:

    • The volume name on which the Beta parameter library is to be allocated.
  3. The dataset name first level qualifier for SMP/E and SMP/E service-dependent datasets.
  4. The dataset name first level qualifier for the BSA distribution and target libraries.
  5. The dataset name for the Beta parameter library (BETA.PARMLIB). This dataset cannot be the library SYS1.PARMLIB.
  6. A user type 3 or 4 SVC number between 200 and 255 for the Beta SVC.

    For the Beta SVC to be loaded at IPL, the SVC has to be linked into the SYS1.LPALIB and specified in the active IEASVCxx member of the SYS1.PARMLIB.

    You must designate one SVC number per BSA environment (version) you will be installing.

  7. The dataset name of a system procedure library into which the Beta SMP/E installation procedure will be placed.
  8. The space requirements as specified in the Release Notes and Update Instructions.
  9. The Beta installation procedure lets you install two different load libraries: the default names are BETA.APFLOAD for all modules that need APF authorization, and BSA.LOAD for all the remaining BSA modules. Every product installation procedure installs its own library (BETAnn.LOAD) in addition.

Modules requiring APF authorization

The following BSA modules are placed into the BETA.APFLOAD:

BST01ARI

Security initialization

BST00STH

Security router

BST00ATH

APF environment checker

BST01SSI

Subsystem initialization

BST01CMD

Operator commands for subsystem initialization

BST01SFF/ BST01RFF

Subsystem Function Facility

BST01SVC

Beta SVC module

BST01MST

Dynamic SVC update module

BST01XCF

BSA XCF Global Connect

BST00XIN

Default logon exit

BST09XIN

VDF user security initialization/termination
(only if VDF is installed). Supports mixed-case passwords. Please see the Installation and System Guides for VAF/CAF/IAF.

B02UXSIN

BSA TCP/IP server logon exit (initialization/ termination). Supports mixed-case passwords.

Additional modules are copied to this library during product installation, for example:

BnnUXSEC

product security exit

BnnSSnnn

SUBSYS interface module

Note on LOAD libraries

We suggest you follow the recommendation in the installation procedure and allocate three different load libraries when installing a Beta Systems product. The authorized BETA.APFLOAD should be put in the linklist. The program BST01ARI can then run at IPL time to initialize the security environment. The remaining two libraries (i.e. BSA.LOAD and BETAnn.LOAD) are concatenated under the STEPLIB DD statement of all product JCL samples.

Be aware of the following if you don't follow recommendations:

  • If the same library is used for authorized and unauthorized modules (i.e. BETA.APFLOAD and BSA.LOAD are merged into one), BSA.LOAD must be APF-authorized. Because the BSA.LOAD is concatenated with the product BETAnn.LOAD in every product JCL, the BETAnn.LOAD needs to be authorized as well.
  • If the BSA.LOAD library is not in the linklist concatenation, the program BST01ARI has to run as a batch job after every IPL for each Beta product subsystem. In this case, BST01ARI must not be specified in member IEFSSNxx as described in the Beta product Installation and System Guides. Only the subsystem ID must be entered here.