Note: To upgrade from previous releases of eLink for Mainframe TCP, refer to Oracle Tuxedo Mainframe Adapter for TCP Release Notes.Prior to beginning the installation, verify hardware and software requirements. For system requirements, refer to the Oracle Tuxedo Mainframe Adapter for TCP Release Notes. Ensure that your installation workstation is connected to z/OS through TCP/IP, and is capable of running FTP.Listing 4‑1 Allocating the Install Data Set/cdrom/unixmf/cics directory,/cdrom is the directory where the drive is mounted.D: is the CD-ROM drive.FTP the file called INSTALL to the temporary data set created in the “Task 1: Allocate Temporary Data Sets” section. Listing 3-2 is the process for downloading the INSTALL file using FTP.Listing 4‑2 Uploading Distribution Files
Note:
1. Modify the JOBCARD to your standards.
2. Modify the variable “YOURHLQ.” If you intend to rename them, modify the variables JCL, OBJECT, and SOURCE.
3. Submit the revised INSTALL JCL. This JCL creates six partitioned data sets based on the “high-level-qualifier” you have specified as the value of the JCL parameter (&HLQ) in the JCL.Listing 4‑3 Sample INSTALL JCLUpload all the files on the distribution medium to the partitioned data sets allocated by the job INSTALL in the “Task 3: Create the PDS Libraries” section.The TMA TCP for CICS distribution files are grouped under one of the following directory structures:/cdrom is the directory where the drive is mounted.D: is the CD-ROM drive.
Table 4‑1 Partitioned Data Sets Listing 4‑4 Uploading Distribution Files Using FTPUpload the CONTROL files.Listing 4‑5 Upload control FilesUpload the JCL files.Listing 4‑6 Uploading JCL FilesUpload the SOURCE files.Listing 4‑7 Uploading SOURCE FilesUpload the INCLUDE files.Listing 4‑8 Uploading INCLUDE FilesUpload the OBJECT files.Listing 4‑9 Uploading OBJECT FilesUpload the PLKED files.Listing 4‑10 Uploading PLKED FilesVerify that the distribution libraries were uploaded. For the listing of files that should be on your system, refer to the “List of Distribution Files and Members” section.Define the CICS VSAM files (Connections, Requesters, Service Names, User Connection, Inbound Service).
1. Modify DELETE/DEFINE control cards VCON, VREQ, VSVC, VUSR, and VISN in the PDS "YOURHLQ".BEATCPC.CONTROL. Listing 4‑11 is an example of a modified DELETE/DEFINE.Listing 4‑11 Sample DELETE/DEFINE Control CardDELETE YOURHLQ.BEATCPC.BEAVSVC -
CLUSTER PURGE -
DEFINE CLUSTER ( -
NAME (YOURHLQ.BEATCPC.BEAVSVC) -
SHAREOPTIONS (2 3) -
KEYS (16 0) -
CISZ (1024) -
TRACKS (5 1) -
VOLUMES (CICS01)) -
DATA ( -
RECORDSIZE (56, 56) -
NAME (YOURHLQ.BEATCPC.BEAVSVC.DATA)) -
INDEX ( _
NAME (YOURHLQ.BEATCPC.BEAVSVC.INDEX))Change all instances of YOURHLQ.BEATCPC.BEAVSVC to a physical data set name that meets your standards. Change the TRACKS and VOLUMES parameters to appropriate values for your installation. The provided value for the TRACKS parameter works for most installations, but this value can be increased if necessary.
2. For the BLDVSAM JCL, complete the following steps.
a. Modify the JOBCARD to your standards.
b.
c. Submit BLDVSAM.
3. Verify the results. There should be three data sets in YOURHLQ.BEATCPC corresponding to each of the five VSAM files. The three data sets are as follows:
• One data set has DATA as the extension
• One data set has INDEX as the extension
Note: A condition code of 8 is acceptable on DELETE steps. If you receive condition codes other than zero for DEFINE steps, you should evaluate this for potential problems.Before you go on to the next step, we recommend that you check the following items in PROCS CMPBC, CMPLMAP, CMPLKED, and LNKIBM in the PDS YOURHLQ.BEATCPC.JCL.
•
• Unit = references.
1. Verify the CICS table entry definitions (PCTs, PPTs, FCTs) in CSDU (from the PDS "YOURHLQ".BEATCPC.CONTROL).
2. Modify the group and list name in CSDU (from the PDS "YOURHLQ".BEATCPC.CONTROL).
3.
a. Modify the JOBCARD to your standards.
b.
c. Modify the SYSIN DSN=YOURHLQ.BEATPC.CONTROL.
d. Submit CSDUPD.
Note:
2. Link the CICS Admin maps (MainMenu, Connection, Requester, Outbound Service Name, Inbound Service Name, User Connection Account, Handler Configuration). In the JCL in MAKLMAP (from the PDS "YOURHLQ".BEATCPC.JCL"), complete the following steps.
a. Modify the JOBCARD to your standards.
b.
c.
Note: LNKLIB is where your CICS region executable binary files reside.
d. Modify the variable PROG, if you renamed mapsets.
e. Submit MAKLMAP.Pre-Link/Link the CICS Admin Programs (MainMenu, Connection, Requester, Outbound Service Name, Inbound Service Name, User Connection Account, Handler Configuration). In the JCL in MAKL1 (from the PDS "YOURHLQ".BEATCPC.JCL"), complete the following steps.
1. Modify the JOBCARD to your standards.
2.
3.
Note: LNKLIB is where your CICS region executable binary files reside.
4. Modify the LKED.SYSIN program names, if you renamed programs.
5. Submit MAKL1.
Note: A “COND CODE = 004” is normal.Pre-Link/Link the CICS utility Programs (Pre-Requester, Application Handler, Shutdown, and Configuration Converter). In the JCL in MAKL0 (from the PDS "YOURHLQ".BEATCPC.JCL"), complete the following steps.
1. Modify the JOBCARD to your standards.
2.
3.
Note: LNKLIB is where your CICS region executable binary files reside.
4. Modify the LKED.SYSIN program names, if you renamed programs.
5. Submit MAKL0.
Note: A “COND CODE = 004” is normal.Pre-Link/Link the CICS TCP Programs (Requester and Handler). In the JCL in MAKL3 (from the PDS "YOURHLQ".BEATCPC.JCL"), complete the following steps.
1. Modify the JOBCARD to your standards.
2.
Note: LNKLIB is where your CICS region executable binary file resides.
3. Modify the INCLUDE OBJECT program name, if you renamed programs.
4. Modify the LKED.SYSIN program names, if you renamed programs.
5. Submit MAKL3.
Note: A “COND CODE = 004” is normal.
•
1. Modify the JOBCARD to your standards.
2.
Note: LNKLIB is where your CICS region executable binary file resides.
3. Submit MAKLKED.Verify the VSAM files
BEALOG DFHDCT TYPE=SDSCI, DSCNAME=BEALOG, BLKSIZE=136, RECSIZE=132, RECFORM=VARUNB, TYPEFLE=OUTPUT, BUFNO=1 BEAL DFHDCT TYPE=EXTRA, DESTID=BEAL, DSCNAME=BEALOG
1. Listing 4‑12 Sample CICS Startup JCL with TMA TCP additions
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•