Install Mainframe Components (v5.4.*)

This section contains documentation about Datamaker Mainframe installation. The installation procedure varies depending on your specific requirements and intended use.
tdm49
This section contains documentation about Datamaker Mainframe installation. This article applies to all service packs of v5.4 of the Mainframe installers on support.broadcom.com. The installation procedure varies depending on your specific requirements and intended use.
All reference data, JCL, parameters, executable load modules, and run components are supplied in TSO XMIT format data sets (LRECL=80, RECFM=FB, BLKSIZE=3120).
The
Ref Data
column on the XMI table identifies which XMIT files are required for which installation type. Pre-allocate the required data sets on the mainframe before you transfer the XMIT files to the mainframe. See Appendix A for a JCL example. Transfer the XMIT files to z/OS without character set conversion. For most sites, an FTP (Binary) transfer is satisfactory. For other sites, FTP options Mode B or Type E might be required depending on the architecture and setup.
Once the XMIT files are transferred to the mainframe, they are received into appropriately specified data sets. The source data set names that are used to create the XMIT files have a high-level qualifier of GRIDT01. You can follow any naming convention for the target data set names. If the names differ from the source data set names, edit the supplied JCL members to reflect the new names. For details of the TSO RECEIVE command, see the IBM TSO User Guide and the TSO Command reference. The following members contain JCL to define the data sets. These data sets are required for the installation and to execute the RECEIVE commands:
"GRIDT01.LIB.RUNJCL(RECEIVE)"(DB2 install)
"GRIDT01.LIB.RUNJCL(RECEIVEV)"(VSAM install)
Edit data set names in this member to appropriate values. Appendix B contains JCL to define and receive data into GRIDT01.LIB.RUNJCL.
After you supply the data sets in z/OS that are specific to your installation, complete the other installation and test steps. These steps are detailed in sections specific to each installation. If you have problems, including issues with the job output from any failing jobs, contact product support.