Installing Oracle Tuxedo Mainframe Adapter for SNA Communications Resource Manager (CRM) on z/OS MVS Platform

This section explains how to install the CRM component on a z/OS Multiple Virtual Storage (MVS) platform.

Note:

The installation process assumes the installer is familiar with Job Control Language (JCL) job operations and File Transfer Protocol (FTP) functions.

Summary of Installation Tasks

The following list is a summary of the tasks detailed in Installation Procedure:

•	Put the JCL files in the MVS environment prior to installation using the FTP program.

•	Allocate the initial datasets using one of the JCL jobs.

•	FTP the product software files (TMACRM.*) to the allocated datasets.

•	Run the second JCL job to allocate the final datasets.

•	Run the TSO RECEIVE command to unload the data in your product datasets. A third JCL file has been provided to run this procedure in batch.

The installation for this environment is semi-automated. Three JCL files are provided to facilitate prerequisites for allocating datasets in the MVS environment and to unload Tuxedo Mainframe Adapter for SNA product software into the allocated datasets.

The product installer contains the following files relating to this installation procedure:

•	README file contains notes on how to install the product in this environment. This is a summary of the procedure in this section.

•	createds.jcl file is a JCL example for creating MVS datasets to receive the Tuxedo Mainframe Adapter for SNA software.

•	uncmprss.jcl file is a JCL example to uncompress and unload into the product datasets.

•	TMACRM.LOAD file contains the Tuxedo Mainframe Adapter for SNA program objects. (Required)

•	TMACRM.DATA file contains Tuxedo Mainframe Adapter for SNA data files. (Required)

•	TMACRM.SAMPLE file contains sample JCL files.

Installation Procedure

Perform the following steps to install the CRM component on a z/OS MVS platform:

1.	Load the product on a machine that has File Transfer Protocol (FTP) access to the MVS UNIX directory (/mvs/ftp-unix) or MVS NT directory (/mvs.ftp-nt).

2.	Use FTP to put the following JCL files in the MVS destination PDS dataset:

createds.jcl

uncmprss.jcl

In your MVS environment, change the CREATEDS job to suit your environment. This job allocates the initial datasets needed to receive the product software files from the FTP file transfer and the SNACRM Load Library, sample and data datasets.

Use the SET statements in the CREATEDS job to set the high-level qualifiers of the receiving datasets according to the following syntax:

SET TMPPDS=[QUALIFIER]

In this statement, [QUALIFIER] is the high-level qualifier for initial datasets need to receive the product software files.

SET HLQPDSE=[QUALIFIER]

In this statement, [QUALIFIER] is the high-level qualifier for the SNACRM Load Library. The load library containing the TMACRM.LOAD program objects must be a Partitioned Dataset with Extended attributes (PDSE). The PDSE minimally must have storage class SMS declaration for z/OS.

SET SCLASS=[CLASS NAME]

In this statement, [CLASS NAME] is the storage class name of the PDSE. This is required for z/OS.

SET HLQPDS=[QUALIFIER]

In this statement, [QUALIFIER] is the high-level qualifier for the sample and data datasets. These are standard PDS.

The CREATEDS job has the following steps:

DELETE

Deletes any existing datasets previously created so you can run this JCL multiple times, if necessary.

CREATE

Allocates the initial datasets needed to receive the product software files and the SNACRM Load Library, sample and data datasets.

3.	Run the CREATEDS job.

4.	Put the files listed in Table 4‑1 into their corresponding datasets. Use the table as a worksheet and fill in the names you created in step Use the worksheet as a guide for transferring the product data to the z/OS platform.

 

Table 4‑1 MVS Installation Product Files and DD Name Datasets

Product File	Set Statement	Your Dataset Name
TMACRM.LOAD	TMPHLQ	.LOAD
TMACRM.DATA	TMPHLQ	.DATA
TMACRM.SAMPLE	TMPHLQ	.SAMPLE

Use Table 4‑2 as a worksheet to fill out the names of the datasets created for SNACRM Load Library, sample and data.

 

Table 4‑2 Set Statements and Corresponding Datasets

Set Statement	Your Dataset Name
HLQPDSE	.LOAD
HLQPDS	.DATA
HLQPDS	.SAMPLE

5.	From the UNIX/NT command prompt, set binary data transfer mode using the FTP program.

Note the following example of a put command:

put TMACRM.LOAD ’TMPHLQ.LOAD’

Transfer the datasets using the put command.

6.	In your MVS environment, change the UNCMPRSS job to suit your environment.

Modify the following variables in the JCL to the high-level qualifier you listed in the tables according to the following syntax:

<PRODHLQ>=[QUALIFIER]

Use the qualifier you listed in Table 4‑1.

<BEAPDSE>=[QUALIFIER]

Use the PDSE qualifier you listed in Table 4‑2.

<BEAPDS>=[QUALIFIER]

Use the PDS qualifier you listed in Table 4‑2.

The UNCMPRSS job has the following step:

UNLOLD

Performs a TSORECEIVE to uncompress and unload the data in your installation datasets created in step 8.

To manually perform the TSO RECEIVE command to unload the data in your installation datasets created in Step 8, enter a command similar to the following command:

TSO RECEIVE INDS(‘xxx’)

When prompted, enter:

DA(‘yyy’)

In these statements, the following definitions apply:

xxx

Is the dataset name you listed in Table 4‑1.

yyy

Is the corresponding dataset name you listed in Table 4‑2.