Overview of installation steps

Overview

This section gives an overview of the installation steps. Each step is then described in detail in a separate section of its own.

The installation descriptions in the BSA and product Installation and System Guide assume that you use one common SMP/E environment for the BSA functions and all Beta products. They also assume that you use only one set of BSA libraries for all Beta products.

Note: Always check the accompanying Release Notes and Update Instructions or Technical Note for possible instruction updates before beginning the installation process.

Installation steps

Step 1: Preparing the installation datasets

Download and unzip the installation archive on a Windows PC and then run the setup program. The product and/or BSA installation datasets are transferred to the z/OS host. The installation datasets are unpacked by extract jobs.

Step 2: Running the installation REXX

The installation REXX uses ISPF panels to ask you to enter the installation parameters. If you decide to install one or more Beta products in this installation process (provided they are on the same installation medium), the product installation procedure is called in the course of execution.

The installation procedure creates several batch jobs that are submitted in the next step. These batch jobs are placed in the newly allocated CNTL file.

Step 3: Submitting the installation batch jobs

You have to submit the installation batch jobs manually. Check that all batch jobs run correctly. If they don't, consult the output listings and try to determine the source of the error. If you cannot determine and correct the error, contact Beta Systems support. This step will place the Beta SVC into an LPALIB dataset.

Step 4: Specifying authorized functions to z/OS

The Beta SVC and the APF-authorized library are specified to your z/OS system. The activation of the Beta SVC and the APF-authorized library can be done either dynamically or via system IPL.

Note

  • Perform one installation step after the other to make sure that the values you need are available. Step 1 must be executed before step 2, and so on.
  • If you are installing a Beta product in a multi-CPU environment and would like to allow users access to Beta product subsystems on remote CPUs, you must set up the communication facilities and product subsystem definitions. You can use XCF and/or OCF.