Download OneAgent to z/OS

You have two options for OneAgent deployment on z/OS

  • Direct download and installation
  • Manual extraction of installation files

Direct download

You can directly download the installation PAX file of the OneAgent for z/OS to your mainframe from the Dynatrace FTP server.

To do it, use the FTPINSTL job below. The FTP install job uses standard FTP procedures to receive the installation PAX file (oneagentzos-R1nnnxx.pax, where R1nnnxx is the release number) from the Dynatrace FTP server and extracts the product installation datasets from the PAX file.

Here's what you need to modify before using the job:

  1. Determine the required USS directory to receive the PAX file and set the MYUSS variable in the job.
  2. Determine the required high level qualifier for the install dataset names and set the HLQ variable in the job.
  3. Change the volume serial number VOLSER to match the site standards.
  • The install job must be in mixed case.
  • Sequence numbers are not allowed.
  • Make sure that the JCL is uploaded with CAPS OFF and NUM OFF options.

Manual extraction

If you don't have access to the FTP server from your z/OS environment, follow the procedure below to extract the product installation datasets from the oneagentzos-R1nnnxx.pax file. In all cases below, R1nnnxx is the release number.


  1. Connect to the FTP server from a Windows or Linux machine and download the oneagentzos-R1nnnxx.pax file in binary mode. If you can't connect to the FTP server from a Windows or Linux machine, obtain the oneagentzos-R1nnnxx.pax file from Dynatrace Support or Sales Engineer.
  2. Upload the oneagentzos-R1nnnxx.pax file to the desired USS directory.
  3. Run pax -rvf oneagentzos-R1nnnxx.pax GIMZIP to unpack the installation files.
  4. Use the EXTRACT job below to extract the product datasets from the installation files. Before running the job, modify the following:
    1. Determine the desired high level qualifier for the install dataset names and set the HLQ variable accordingly.
    2. Set MYUSS to the USS directory path where you placed oneagentzos-R1nnnxx.pax file.
    3. Change the volume serial number VOLSER to match the site standards.

If the job ends with a RC of 0, the installation has been successful. The installation process creates the following product datasets (the names are provided for the default high level qualifier and the R1nnnxx release version):

  • DT.R1nnnxx.SZDTAUTH: Contains zDC load modules, IMS and IMS Connect code modules of OneAgent.
  • DT.R1nnnxx.SZDTLOAD: Contains CICS code modules of OneAgent.
  • DT.R1nnnxx.SZDTSAMP: Includes sample JCL and CICS RDO definitions.

Consider defining an alias without the version number for the product datasets. In that case you'll be able to install maintenance without updating the jobs for zDC, CICS and IMS installers.

Installed datasets and installation files in the USS directory take that much space:

Dsname                Tracks(3390) %Used
DT.R119500.SZDTAUTH   88            30
DT.R119500.SZDTLOAD   53            30
DT.R119500.SZDTSAMP  305            59
./GIMZIP/                   6Meg
./oneagentzos-R119500.pax   5Meg

Upgrade and maintenance

Follow the procedure below to upgrade OneAgent for z/OS.

  1. Install the latest version of the OneAgent for z/OS modules from the oneagentzos-R1nnnxx.pax file using FTPINSTL or EXTRACT jobs above
  2. Update the zDC job, the DFHRPL in the CICS procedure, and the IMS code module injection job to point to the new distribution.

We recommend creating version independent ALIAS datasets for the product libraries. Use the ALIAS datasets in the zDC, CICS and IMS code module injection jobs. Whenever there is an upgrade, re-define the ALIAS to the new distribution.

For example:


The product maintenance is provided as part of the latest oneagentzos-R1nnnxx.pax file in the FTP server. Refer to the steps 1 and 2 above to install the maintenance.

  • The maintenance product installation will serve as a complete replacement of the existing product libraries