Beta Systems distributes its software via download from the Beta Systems website. BSA is included in the product download.
You will need to register when visiting this page for the first time:
https://customer.betasystems.com/
The software is made available as a ZIP archive, which includes all the folders and files that are necessary to install the software. Unzip the installation archive under Windows, and then run the setup program of the product, which transfers the installation datasets to the z/OS host. Folder names and file names are self-explanatory.
Important: The installation REXX of a product includes only the BSA components that are used by this product. Use the setup program of the product that includes all shared components that you need in your environment. See "Pre-installation checklist" for more details.
The installation process involves these steps:
Each step is described in more detail below.
By default, the setup program uses ftp for data transfer to the host, which assumes that IBM FTP server is available.
About 250 MB of temporary space are required on the PC. Space requirements on the z/OS host depend on the number of components you will be installing.
The following steps are carried out on a Windows PC:
You can find the setup program in the product zOS folder. All data for both the product and BSA are included in this setup program.
The setup program will request the following information in sequence:
CDUNPK00 and CDUNPKnn unpack the installation datasets. CDUDEL00 and CDUDELnn can be used for deleting installation libraries and datasets. The job card for the BSA and product installation jobs will be requested later when you run the installation REXX on the z/OS host.
The high-level qualifier of BSA must be different from the high-level qualifier of the product. The high-level qualifiers specified here are used for transferred installation datasets and unpacked datasets. Specify new unique HLQs to avoid allocation errors during unpacking. The high-level qualifiers for SMP/E and tailored CNTL libraries, databases, etc. will be requested later when you run the installation REXX on the z/OS host.
For automatic transfer via ftp:
Alternatively, you can also transfer the datasets manually.
The setup program transfers the installation datasets to the z/OS host.
Depending on whether you selected BSA or product or both, the following datasets will be present after transfer:
|
Dataset |
Description |
|---|---|
|
hlqbsa.CDFILE |
Packed dataset (super file) that contains the BSA installation data |
|
hlqbsa.JOBLIB |
Partitioned dataset that contains the installation jobs CDUNPK00 and CDUDEL00 |
|
hlqprod.CDFILE |
Packed dataset (super file) that contains the product installation data |
|
hlqprod.JOBLIB |
Partitioned dataset that contains the installation jobs CDUNPKnn and CDUDELnn |
If you are experiencing difficulties with the setup program's automatic file transfer, you can also transfer the required files manually. To do this, choose option Transfer files to z/OS manually in the setup program and specify a destination folder for the files that are to be transferred.
The setup program creates the ftp script ftp.txt, which contains all the necessary information on the files that need to be transferred (source files, target datasets and their attributes, and transfer modes). You can run this script directly in your ftp client if you provide appropriate values for the placeholders <IPADDRESS>, <PORT>, <USERNAME> and <PASSWORD>.
For example, under Windows, open a command box, change to the destination folder, and then enter the following command:
ftp ‑s:ftp.txt
You can also use another suitable file transfer facility instead of ftp.
Important: For security reasons, you should delete the contents of the destination folder from your PC after the transfer, or at least remove your credentials from ftp.txt.
Unpack the super file(s) on the z/OS host:
The result will be a collection of installation libraries and datasets whose format is usable as input for the installation process. For example, hlqbsa.DATA and hlqprod.DATA are libraries whose members contain the MCS statements (one per product and per additional facility or add-on).
Job CDUNPKnn will end in error if it encounters a dataset of the same name during data extraction, for example, relicts of a previous or incomplete installation. In this case, run CDUDELnn first to delete offending datasets.
You can ignore RC=8 if this is caused by message "IDC3012I ENTRY datasetname NOT FOUND", which means that one or more of the datasets to be deleted were not present. Afterwards, run CDUNPKnn to unpack again.