Objective

This page provides installation requirements and summary for Universal Agent 7.2.x on a z/OS operating system.

System Requirements

Universal Agent for z/OS requires the following software releases:

z/OS 2.3, 2.4 or 2.5.
SMP/E 3.5 or later.
IBM Communication Server for z/OS 2.2, 2.3, or 2.4.
IBM Language Environment (LE) for z/OS 2.2, 2.3, or 2.4.
Windows workstation capable of establishing a TCP/IP network connection to the z/OS system.
TSO user ID with an OMVS segment.
About 1900 cylinders of DASD.
Two available TCP/IP ports on z/OS.

All Universal Agent programs use z/OS UNIX System Services. As such, z/OS UNIX requires the user profile with which a program executes to have a properly defined OMVS segment. The OMVS segment should define a unique UID value. The HOME value must specify an existing home directory to which the user ID has read and write access.

Additionally, the group(s) that the user ID is associated with must have an OMVS segment that defines a unique GID value for the group. Refer to IBM's UNIX System Services Planning manual for additional details on defining z/OS UNIX users.

Platform Requirements

Since platform requirements may change with new releases of a product, please consult the Platform Support for Universal Controller 7.2.x and Universal Agent 7.2.x page to make sure that your platform is supported before performing an installation.

Data Set Space Requirements

As part of the Universal Agent for z/OS package installation, a number of SMP/E and non-SMP/E data sets are allocated and cataloged. The space requirements for these data sets are listed in z/OS Installation - Data Set Inventory.

Installation Summary

Step 1	Download one of the Universal Agent 7.2.x for z/OS product distribution files.
Step 2a	If one of the distribution files with the .tar.Z extension was downloaded, decompress it using any utility that can process files in Lempel-Ziv (that is, compress) format. Use tar to extract the files from the uncompressed file. To do both in a single statement, decompress the file to stdout and pipe the result to tar (for example, zcat sb-v.r.m.l-zos.tar.Z \| tar xvf -).
Step 2b	If one of the distribution files with the .zip extension was downloaded, decompress it using any utility that can process files in ZIP (or, PKZIP) format. The .zip file can also be extracted using Windows native file extraction tools.
Step 3	Modify the UNVFTP.TXT script provided by the distribution file. This script contains statements to upload the installation files and sample JCL, which can be used to process the files after upload. Two versions of these files are included in the distribution file. The files in the main directory are EBCDIC-encoded files. ASCII-encoded versions of these files are in the `./ascii` subdirectory. See z/OS Installation - Transferring Installation Files to z/OS for complete details.
Step 4	Modify the JCL uploaded from UNVRECV.JCL and run the job to receive the TSO XMIT file(s). If the distribution file that contains the DFDSS archive is used, UNVRECV.JCL also contains a step to restore the contents of the archive. See Receive the Installation Datasets for complete details.
Step 5	Edit the INSTALL(#SETUP) member to meet local requirements as described in the #SETUP comment prolog. #SETUP creates customized installation JCL members in the INSTALL library. Execute the installation jobs as required for your SMP/E environment. See z/OS Installation - SMPE Installation for complete details.
Step 6	Create started task user and group profiles for Universal Broker and Universal Enterprise Controller. See z/OS Configuration - Started Tasks for complete details.
Step 7	Define the SUNVLOAD library to APF, Program Control, and LNKLST. See z/OS Configuration - Load Library for complete details.
Step 8	Define SMF exits for Universal Command and Universal Automation Center Agent. See z/OS Configuration - SMF Exits for complete details.
Step 9	Configure the UNIX System Services file systems used by the Universal Broker and Universal Enterprise Controller. See Universal Agent Database Configuration for complete details.
Step 10	Perform individual component customization, including JCL procedure edits and adding component licenses. See z/OS Installation - Customization for complete details.
Step 11	Follow the optional steps described in z/OS USS Installation to complete the installation, if desired.

Customization

Customization consists of editing PDS members in the Universal configuration library, UNVCONF.