Download z/OS product datasets
You can choose between the direct download and installation of the Dynatrace product datasets for z/OS or the manual extraction of the installation files depending on your ability to access the Dynatrace FTP server.
See Install the z/OS Java code module on how to download the JAR file.
Direct download
You can directly download the installation PAX file to your z/OS Unix System Services (USS) envionment from the Dynatrace FTP server using the FTPINSTL
install job below. This 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 it.
Before running the job:
- Determine the required z/OS USS directory to receive the PAX file and set the
MYUSS
variable in the job. - Determine the required high level qualifier for the install dataset names and set the
HLQ
variable in the job. - Change the volume serial number
VOLSER
to match 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 Dynatrace FTP server from your mainframe, 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
- Connect to the Dynatrace 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 theoneagentzos-R1nnnx.pax
file from Dynatrace ONE. To do so, please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.
- Upload the
oneagentzos-R1nnnx.pax
file to the desired USS directory. - Run
pax -rvf oneagentzos-R1nnnx.pax GIMZIP
to unpack the installation files. - Use the
EXTRACT
job below to extract the product datasets from the installation files. Before running the job, modify the following:- Determine the desired high level qualifier for the install dataset names and set the
HLQ
variable accordingly. - Set
MYUSS
to the z/OS USS directory path where you placedoneagentzos-R1nnnx.pax
file. - Change the volume serial number
VOLSER
to match site standards.
- Determine the desired high level qualifier for the install dataset names and set the
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 the zDC subsystem and the IMS code module including IMS ConnectDT.R1nnnx.SZDTLOAD
: Contains the CICS code moduleDT.R1nnnx.SZDTSAMP
: Includes sample JCL and CICS RDO definitions
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 z/OS USS directory use the following space:
Dsname Tracks(3390) %Used
---------------------------------------
DT.R12610.SZDTAUTH 893 5
DT.R12610.SZDTLOAD 59 27
DT.R12610.SZDTSAMP 520 57
./GIMZIP/ 8K
./oneagentzos-R12610.pax 5M
Update and maintenance
When updating 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.
- Stop the zDC.
- Wait for 15 minutes for the CICS code module to reset and clean up the control blocks.
- Update the zDC to the newer version.
- Start the zDC.
To update the code modules:
- Use the
FTPINSTL
orEXTRACT
jobs above to install the latest version of the code modules from theoneagentzos-R1nnnx.pax
file. - 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 update, redefine the ALIAS to the new distribution.
For example:
DELETE 'DT.DYNTRC.SZDTAUTH' NOSCRATCH
DEFINE ALIAS(NAME('DT.DYNTRC.SZDTAUTH') RELATE('DT.R12610.SZDTAUTH'))
DELETE 'DT.DYNTRC.SZDTLOAD' NOSCRATCH
DEFINE ALIAS(NAME('DT.DYNTRC.SZDTLOAD') RELATE('DT.R12610.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 Dynatrace 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.
- 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 cannot be higher than the zRemote release (the
nnn
part of the release number) or the zDC and zRemote may not connect.