Download z/OS product datasets
You can download the PAX file containing the CICS, IMS, z/OS Java, and zDC modules in two ways:
- Dynatrace version 1.272+ Download via Deployment API.
- Dynatrace version 1.276+ Download via web UI.
Starting with OneAgent release 1.275, the PAX file will no longer be published on our FTP server.
Download the PAX file
You can download the latest or a specific PAX file version via web UI or the Deployment API of OneAgent.
The PAX file version must be equal to or lower than the zRemote module version.
Download latest version via web UI
-
In the Dynatrace menu, go to Deploy Dynatrace and select Start installation.
-
Select z/OS and Download z/OS product datasets to download the latest PAX file version.
The file name
dynatrace-zos-1.nnn.m.pax
includes the major release versionnnn
andm
minor.
Download a specific version via web UI
You can download a specific PAX file version via web UI as follows:
-
In the Dynatrace menu, go to Settings and select Monitoring > Monitoring oveview.
-
Select Download Dynatrace OneAgent or ActiveGate installer and define your preferred version:
- Installer:
OneAgent - z/OS
Build: Select your preferred major version
Revision: Select your preferred minor version
- Installer:
-
Select Continue and Download z/OS product datasets to download your defined PAX file version.
The file name
dynatrace-zos-1.nnn.m.pax
includes the major release versionnnn
andm
minor.
Download latest version via Deployment API
You can download the latest PAX file version via Deployment API as follows:
-
Generate an Access token with the scope PaaS integration - Installer download (
InstallerDownload
). -
Download the latest PAX file via Deployment API - Download latest OneAgent:
HTTP method Dynatrace environment Endpoint GET
SaaS
https://{your-environment-id}.live.dynatrace.com/api/v1/deployment/installer/agent/zos/mainframe/latest
GET
Managed
https://{your-domain}/e/{your-environment-id}/api/v1/deployment/installer/agent/zos/mainframe/latest
Below is a sample
curl
command for a SaaS environment that uses the Deployment API to download the latest PAX file version:1curl -X GET "https://<environment>.live.dynatrace.com/api/v1/deployment/installer/agent/zos/mainframe/latest" -H "accept: */*" -H "Authorization: Api-Token <accessToken>" --output dynatrace-zos.paxReplace
<environment>
with your Dynatrace environment ID and<accessToken>
with your generated access token.
Download a specific version via Deployment API
You can download a specific PAX file version via Deployment API as follows:
-
Generate an Access token with the scope PaaS integration - Installer download (
InstallerDownload
). -
List all available PAX file versions via Deployment API - List available versions of OneAgent.
HTTP method Dynatrace environment Endpoint GET
SaaS
https://{your-environment-id}.live.dynatrace.com/api/v1/deployment/installer/agent/versions/zos/mainframe
GET
Managed
https://{your-domain}/e/{your-environment-id}/api/v1/deployment/installer/agent/versions/zos/mainframe
Below is a sample
curl
command for a SaaS environment that uses the Deployment API to list all available PAX file versions:1curl -X GET "https://<environment>.live.dynatrace.com/api/v1/deployment/installer/agent/versions/zos/mainframe" -H "accept: */*" -H "Authorization: Api-Token <accessToken>"Replace
<environment>
with your Dynatrace environment ID and<accessToken>
with your generated access token. -
Download a specific PAX file version via Deployment API - Download OneAgent of specific version:
HTTP method Dynatrace environment Endpoint GET
SaaS
https://{your-environment-id}.live.dynatrace.com/api/v1/deployment/installer/agent/zos/mainframe/version/{version}
GET
Managed
https://{your-domain}/e/{your-environment-id}/api/v1/deployment/installer/agent/zos/mainframe/version/{version}
Below is a sample
curl
command for a SaaS environment that uses the Deployment API to download a specific PAX file version:1curl -X GET "https://<environment>.live.dynatrace.com/api/v1/deployment/installer/agent/zos/mainframe/version/<version>" -H "accept: */*" -H "Authorization: Api-Token <accessToken>" --output dynatrace-zos.paxReplace
<environment>
with your Dynatrace environment ID,<version>
with your selected PAX file version, and<accessToken>
with your generated access token.
Extract product datasets
You can extract the product datasets from the PAX file as follows:
-
Transfer the PAX file to your z/OS USS directory in binary mode.
-
Rename the PAX file from
dynatrace-zos-1.nnn.m.pax
todynatrace-zos.pax
. -
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 placed thedynatrace-zos.pax
file. - Change the volume serial number
VOLSER
to match site standards.
1//EXTRACT JOB ('ACCTINFO'),'User name or comment',NOTIFY=&SYSUID,2// MSGLEVEL=(1,1),CLASS=A,MSGCLASS=X,REGION=0M,3// COND=(0,NE)4//*5//* !!!!!!!! IMPORTANT !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!6//*7//* When upgrading the zDC to version 1.213+ while8//* the CICS code module is enabled, it is important to follow9//* the below steps in the given sequence.10//*11//* 1. Stop the zDC12//* 2. Wait for 15 minutes for the CICS code module to13//* reset/cleanup the control blocks14//* 3. Upgrade the zDC to newer version15//* 4. Start the zDC16//*17//* !!!!!!!! IMPORTANT !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!18//*19//* This job extracts the product installation datasets from20//* the installation files at <MYUSS>/GIMZIP to21//* <hlq>.<rel>.SZDT* libraries.22//*23//* Change the JOB card and the SET statements below to meet24//* site standards.25//*26//* Verify if the SMPCPATH and SMPJHOME DD below points to the27//* correct PATH to meet site standards.28//*29//* WARNING!30//* This JCL must be in mixed case and sequence numbers are not allowed31//*32// EXPORT SYMLIST=*33// SET HLQ='DT' <== HLQ of the target PDS datasets34// SET REL='R12770' <== Release number35// SET VOLSER='NSM001' <== Volume of the target PDS datasets36// SET MYUSS='/u/dt' <== USS work directory37//STEP1 EXEC PGM=IKJEFT01,DYNAMNBR=1038//SYSPRINT DD SYSOUT=*39//SYSTSPRT DD SYSOUT=*40//STDOUT DD SYSOUT=*41//STDERR DD SYSOUT=*42//SYSIN DD DUMMY43//SYSTSIN DD *,SYMBOLS=EXECSYS44BPXBATCH SH rm -Rf &MYUSS/GIMZIP45BPXBATCH SH cd &MYUSS && +46 pax -rvf dynatrace-zos.pax GIMZIP47//STEP2 EXEC PGM=GIMUNZIP,PARM='HASH=YES'48//SMPDIR DD PATH='&MYUSS/GIMZIP/',PATHDISP=KEEP49//SMPCPATH DD PATH='/usr/lpp/smp/classes/',PATHDISP=KEEP50//SMPJHOME DD PATH='/usr/lpp/java/J8.0/',PATHDISP=KEEP51//SMPOUT DD SYSOUT=*52//SYSPRINT DD SYSOUT=*53//SYSUT3 DD UNIT=SYSALLDA,SPACE=(CYL,(25,5))54//SYSUT4 DD UNIT=SYSALLDA,SPACE=(CYL,(25,5))55//SYSIN DD *,SYMBOLS=EXECSYS56<GIMUNZIP>57 <ARCHDEF archid="AUTHLIB"58 replace="YES"59 volume="&VOLSER"60 newname="&HLQ..&REL..SZDTAUTH">61 </ARCHDEF>6263 <ARCHDEF archid="LOAD"64 replace="YES"65 volume="&VOLSER"66 newname="&HLQ..&REL..SZDTLOAD">67 </ARCHDEF>68 <ARCHDEF archid="SAMPLE"69 replace="YES"70 volume="&VOLSER"71 newname="&HLQ..&REL..SZDTSAMP">72 </ARCHDEF>73</GIMUNZIP>74/*75//STEP3 EXEC PGM=IKJEFT01,DYNAMNBR=1076//SYSPRINT DD SYSOUT=*77//SYSTSPRT DD SYSOUT=*78//STDOUT DD SYSOUT=*79//STDERR DD SYSOUT=*80//SYSIN DD DUMMY81//SYSTSIN DD *,SYMBOLS=EXECSYS82BPXBATCH SH cp &MYUSS/GIMZIP/dynatrace-oneagent-zos-java.jar +83 &MYUSS/dynatrace-oneagent-zos-java.jar84//STEP4 EXEC PGM=IKJEFT01,DYNAMNBR=5585//SYSPRINT DD SYSOUT=*86//SYSTSPRT DD SYSOUT=*87//STDOUT DD SYSOUT=*88//STDERR DD SYSOUT=*89//SYSIN DD DUMMY90//SYSTSIN DD *,SYMBOLS=EXECSYS91BPXBATCH SH rm -Rf &MYUSS/GIMZIP92//If the job ends with a return code of
0
, the extraction was successful.optional Delete
dynatrace-zos.pax
anddynatrace-oneagent-zos-java.jar
(if it is not needed) to free up disk space. - Determine the desired high-level qualifier for the install dataset names and set the
Product datasets
The extraction 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 module including IMS ConnectDT.R1nnnx.SZDTLOAD
: Contains the CICS moduleDT.R1nnnx.SZDTSAMP
: Includes sample JCL and CICS RDO definitions
On an average, the product datasets and installation files in the z/OS USS directory use the following disk space:
1Dsname Tracks(3390) %Used2---------------------------------------3DT.R1nnnm.SZDTAUTH 893 54DT.R1nnnm.SZDTLOAD 61 275DT.R1nnnm.SZDTSAMP 1221 24
1./GIMZIP/ 8K2./dynatrace-zos-1.nnn.m.pax 5M
Define aliases
We recommend defining an ALIAS
without the version number for the product datasets. Use these ALIAS
in the zDC, CICS, and IMS module injection jobs. You can then perform maintenance without updating the jobs.
For example:
1DEFINE ALIAS(NAME('DT.DYNTRC.SZDTAUTH') RELATE('DT.R12770.SZDTAUTH'))2DEFINE ALIAS(NAME('DT.DYNTRC.SZDTLOAD') RELATE('DT.R12770.SZDTLOAD'))