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 so, use the FTPINSTL job below. The FTP install job uses standard FTP procedures to receive the installation PAX file (oneagentzos-R1nnnx.pax, where R1nnnx is the release number) from the Dynatrace FTP server and extracts the product installation datasets from the PAX file.

Before running 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 site standards.
Notes
  • 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-R1nnnx.pax file. In all cases below, R1nnnx is the release number.

Procedure

  1. Connect to the FTP server from a Windows or Linux machine and download the oneagentzos-R1nnnx.pax file in binary mode. If you can't connect to the FTP server from a Windows or Linux machine, obtain the oneagentzos-R1nnnx.pax file from a Dynatrace Support or Sales Engineer.
  1. Upload the oneagentzos-R1nnnx.pax file to the desired USS directory.
  2. Run pax -rvf oneagentzos-R1nnnx.pax GIMZIP to unpack the installation files.
  3. 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-R1nnnx.pax file.
    3. Change the volume serial number VOLSER to match site standards.

If the job ends with a return code of 0, the installation was successful.

The installation process creates the following product datasets (the names are provided for the default high-level qualifier and the R1nnnx release version):

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

Consider defining an alias without the version number for the product datasets. Then 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 use the following space:

Dsname                Tracks(3390) %Used
---------------------------------------
DT.R12270.SZDTAUTH      893          5
DT.R12270.SZDTLOAD       61         24
DT.R12270.SZDTSAMP      520         57
./GIMZIP/                   8K
./oneagentzos-R12270.pax    5M

Upgrade and maintenance

Important

When upgrading the zDC from a version 1.211 or earlier to the version 1.213+, a special handling is required to avoid abends in CICS regions that you're monitoring.

  1. Stop the zDC.
  2. Wait for 15 minutes for the CICS code module to reset/cleanup the control blocks.
  3. Upgrade the zDC to newer version.
  4. Start the zDC.

To upgrade OneAgent for z/OS

  1. Use the FTPINSTL or EXTRACT jobs above to install the latest version of the OneAgent for z/OS modules from the oneagentzos-R1nnnx.pax file.
  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 that you create 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, redefine the ALIAS to the new distribution.

For example:

DELETE 'DT.DYNTRC.SZDTAUTH' NOSCRATCH
 DEFINE ALIAS(NAME('DT.DYNTRC.SZDTAUTH') RELATE('DT.R12270.SZDTAUTH')) 
 DELETE 'DT.DYNTRC.SZDTLOAD' NOSCRATCH
 DEFINE ALIAS(NAME('DT.DYNTRC.SZDTLOAD') RELATE('DT.R12270.SZDTLOAD'))

See the note below before deciding whether to use the current z/OS version or a backlevel version with a bug fix on.

The product maintenance is provided as part of the latest oneagentzos-R1nnnx.pax file in the FTP server. The current JCL in this document will download the latest release that contains the entire maintenance.

If you want to install a back-level release with a specific fix, you need to download the PAX file for that release. File names are of the form oneagentzos-R1nnnx.pax, where nnn is the release version and x is the fix version. This will only give you fixes that are backported and not any new enhancements. You can browse the folder on our FTP site (us-et-ftp01.dynatrace.com), choose the PAX file you want to install, and then modify your JCL using this PAX file.

We suggest that you use the most current one from the JCL above.

Refer to steps 1 and 2 above to install the maintenance.

Note
  • The maintenance product installation will serve as a complete replacement of the existing product libraries.
  • Be aware that the most current version of the z/OS release can not be higher than the zRemote release (the nnn part of the release number) or the zDC and zRemote may not connect.