Objective

This Universal Agent 7.2.x for z/OS Quick Start Guide provides a short summary on how to install Universal Agent on a z/OS system and run a few simple batch jobs demonstrating Universal Agent on z/OS. For a complete description of the installation process, see Universal Agent 7.2.x Installation, Upgrade, and Applying Maintenance.

The following information is provided:

• System Requirements
• Downloading the Universal Agent 7.2.x for z/OS distribution file.
• Installing Universal Agent 7.2.x on z/OS.
• Licensing Universal Agent components.
• Encrypting passwords to be used in Universal Agent jobs.
• Executing a Universal Command job.
• Executing a Universal Data Mover job.
• Executing a Universal Broker query job.

System Requirements

• z/OS 2.2, 2.3, or 2.4.
• 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.

Platform Requirements

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

Downloading the Universal Agent 7.2.x for z/OS Distribution File

The Universal Agent 7.2.x for z/OS product distribution file - sb-7.2.x.x-zos.tar.Z - is available for download from the Stonebranch Customer Portal.

A customer user name and password - provided by Stonebranch, Inc. - are required to access the Customer Portal.

Installing Universal Agent 7.2.x for z/OS

Licensing your Universal Agent 7.2.x for z/OS Components

After Universal Agent 7.2.x for z/OS has been installed, you must configure the following Universal Agent components with product licenses before they can be used:

• Universal Command Manager
• Universal Connector
• Universal Data Mover Manager

For each component, product license information (license parameter keywords and their values) is contained in a separate text file provided by your Stonebranch, Inc. account representative.

The format of a product license file name is: <component name>_<customer name>_<operating system>_<schedule or solution>.txt. For example: Agent_Stonebranch_MVS_A1.txt.

Universal Command Manager License File

For Universal Command Manager, Agent is used as the <component name> in the product license file name and as the name of the product in the file itself - see below.)
 

The following is a sample Universal Command Manager for z/OS product license file:

Universal Data Mover Manager License File

For Universal Data Mover Manager, MFT is used as the <component name> in the product license file name and as the name of the product in the file itself - see below.)
 

The following is a sample Universal Data Mover Manager for z/OS product license file:

UNVCONF Product Library

In the UNVCONF product library:

• Enter the Universal Command Manager license parameters into the Universal Command Manager configuration file, member UCMCFG00.
• Enter the Universal Connector license parameters into the Universal Connector configuration file, member USPCFG00.
• Enter the Universal Data Mover Manager license parameters into the Universal Data Mover Manager configuration file, member UDMCFG00.

It is recommended that you enter license information at the end of the file. (The values are specified in the same syntax as all other configuration options.)

Restart Universal Broker

For Universal Broker to read the license information, you must stop and restart it.
 

Encrypting User ID and Password for Job Execution

Universal Command and Universal Data Mover typically require user credentials to execute work on a remote host. The user credentials can be stored in an encrypted format for privacy reasons. Read access to the file should be restricted to authorized users even though the contents are encrypted. Universal Command and Universal Data Mover will read user credentials in the encrypted format.

The following JCL example executes the UENCRYPT utility that encrypts command options it reads from the UNVIN ddname and writes them to the UNVOUT ddname in the form of an encrypted command file. This example creates member DALLAS in the PDS/E PROD.UNV.USERS. The DALLAS member will contain the user ID and password options specified in the UNVIN ddname in a UENCRYPT format.

Executing a Universal Command Job

The following JCL example executes the UNIX command "ls -l" on remote host DALLAS using the encrypted command file created above.

Executing a Universal Data Mover Job

Universal Data Mover execution is driven by an easy to use scripting language. The Universal Data Mover script controls the transfer sessions established with remote hosts and the file and transfer operations performed on the host's file systems.

The following JCL example executes Universal Data Mover. Universal Data Mover always reads the script from the UNVSCR ddname. In this example, the script establishes a session with remote host DALLAS and transfers the data set allocated to ddname DATA to file app.data on the remote host. The default transfer mode of binary is used for transferring the data.

Running a System Query

Use the Universal Query utility to query the Universal Broker for Broker and active component information. Universal Query returns information about the Universal Broker, as specified by configuration options, as well as information regarding the components managed by Universal Broker.

The following JCL example executes the UQUERY utility. In this example, UQUERY will query the Broker running on host DALLAS.