|
|
Installing Oracle Tuxedo Mainframe Adapter for TCP (IMS) (hereafter referenced as TMA TCP for IMS) consists of the following basic tasks.
| Note: | To upgrade from previous releases of eLink for Mainframe TCP, refer to Oracle Tuxedo Mainframe Adapter for TCP Release Notes. |
Complete the following tasks prior to installing the TMA TCP for IMS software:
To install TMA TCP for IMS, complete the following tasks:
The directory structures on the TMA TCP for IMS software CD include the following partitioned datasets:
The following datasets are allocated to receive the Tuxedo Mainframe Adapter for TCP file distribution.
DSNAME: hlq1.hlq2.CONTROL
DSORG: PO
DIRBLKS: 10
RECFM: FB
LRECL: 80
BLKSIZE: 23440 (or other valid blocksize)
SPACE: 2 tracks
Usage: IMS sample definitions, sample configuration file
DSNAME: hlq1.hlq2.INCLUDE
DSORG: PO
DIRBLKS: 10
RECFM: FB
LRECL: 80
BLKSIZE: 23440 (or other valid blocksize)
SPACE: 2 tracks
Usage: C header file, COBOL copybooks
DSNAME: hlq1.hlq2.JCL
DSORG: PO
DIRBLKS: 10
RECFM: FB
LRECL: 80
BLKSIZE: 23440 (or other valid blocksize)
SPACE: 2 tracks
Usage: Sample LINK and execute JCL
DSNAME: hlq1.hlq2.MSGCAT
DSORG: PS
DIRBLKS: 10
RECFM: FB
LRECL: 100
BLKSIZE: 32000 (or other valid blocksize)
SPACE: 2 tracks
Usage: Message text
DSNAME: hlq1.hlq2.OBJECT
DSORG: PO
DIRBLKS: 10
RECFM: FB
LRECL: 80
BLKSIZE: 3200
SPACE: 1 cylinder
Usage: Pre-linked object files
DSNAME: hlq1.hlq2.SOURCE
DSORG: PO
DIRBLKS: 10
RECFM: FB
LRECL: 80
BLKSIZE: 23440 (or other valid blocksize)
SPACE: 1 track
Usage: Sample IMS client and server transactions
The following runtime datasets are also allocated.
DSNAME: hlq1.hlq2.LOAD
DSORG: PO
DIRBLKS: 10
RECFM: U
LRECL: 0
BLKSIZE: 6133 (or other valid blocksize)
SPACE: 1 cylinder
Usage: Load library
DSNAME: hlq1.hlq2.CONFIG
DSORG: PS
RECFM: FB
LRECL: 80
BLKSIZE: 23440 (or other valid blocksize)
SPACE: 1 track
Usage: Configuration File
DSNAME: hlq1.hlq2.MSGLOG
DSORG: PS
RECFM: VB
LRECL: 1028
BLKSIZE: 6144 (or other valid blocksize)
SPACE: 1 cylinder
Usage: Message Log
DSNAME: hlq1.hlq2.SVRLOG
DSORG: PS
RECFM: VB
LRECL: 32756
BLKSIZE: 32760 (Note: required blocksize)
SPACE: 1 cylinder
Usage: Server Response Log
The TMA TCP for IMS product is distributed on a single CD-ROM (with other members of the Tuxedo Mainframe Adapter for TCP product). The TMA TCP for IMS distribution files are grouped under one of the following directory structures:
Because the distribution files are located on a CD-ROM, you probably use a UNIX-based system or a PC-based system to access the files on the CD-ROM and file transfer them to z/OS.
Transfer the contents of each subdirectory to the corresponding distribution library on the z/OS system. Use a file transfer program (such as FTP) or any other mechanism that allows you to transfer files to your z/OS system. The file transfer program must be able to:
The IBM File Transfer Program (FTP, distributed as part of TCP/IP for z/OS) satisfies both of these requirements.
Each file in each subdirectory on the distribution CD-ROM corresponds to a member of the associated target library. For example, file BEATCPI in the JCL subdirectory corresponds to member BEATCPI in the JCL distribution library.
| Note: | All files in the CONTROL, INCLUDE, JCL, and SOURCE subdirectories are text files; be sure to specify text (or ASCII) mode when you transfer these files from the CD-ROM to their corresponding z/OS distribution library members. |
| Note: | The MSGCAT file and all files in the OBJECT subdirectory are binary files; specify binary (or image) mode when you transfer these files from the CD-ROM to the corresponding z/OS distribution library members. |
The TMA TCP for IMS program is delivered as a pre-linked object file. Use the LNKBEA34 JCL file for linking with IBM’s TCP/IP.
Tailor the JCL as required to match your installation’s standards and naming conventions. Review the following items and make the necessary changes before you submit the job.
SYS1.SCEELKED), TCP/IP for z/OS datasets (for example, SYS1.SEZACMTX), and IMS (for example, IMSV5R1.RESLIB).BEATCPI.DIST.OBJECT).HEWL) as required to match the name used by your installation.| Note: | The link job references components supplied by LE/370, TCP/IP for z/OS, and IMS. |
When the job completes successfully, you receive a return code of 0 from the link-edit steps and an executable load module is placed into the specified target load library. The load module should have attributes of AMODE=31, RMODE=24. There should be no unresolved external references.
Listing 4-3 is JCL to link the distributed object files into an executable load module.
//JOBNAME JOB ETC.
//LKED EXEC PGM=HEWL,COND=(4,LT),
// REGION=2M,PARM='AMODE=31,MAP,XREF'
//SYSLIB DD DSNAME=SYS1.SCEELKED,DISP=SHR
// DD DSNAME=SYS1.SEZACMTX,DISP=SHR
//SYSPRINT DD SYSOUT=*
//SYSLMOD DD DISP=SHR,DSNAME=BEATCPI.DIST.LOAD
//SYSUT1 DD UNIT=VIO,SPACE=(TRK,(10,10))
//RESLIB DD DISP=SHR,DSN=IMSV5R1.RESLIB
//SYSLIN DD DISP=OLD,DSN=BEA.HLQ.OBJECT(PREBEA34)
// DD *
INCLUDE RESLIB(DFSLI000)
ENTRY CEESTART
NAME BEATCPI(R)
/*
//
To integrate TMA TCP for IMS into your IMS environment, you must properly define it to MVS.
To use OTMA to integrate TMA TCP for IMS into your z/OS environment, you must properly define it in the program property table (PPT). Listing 4-4 is a sample program entry for the Tuxedo Mainframe Adapter for TCP product. Also, you must link the program to an APF authorized library.
PPT PGMNAME(BEATCP34) /* PROGRAM NAME = BEATCP34 */
CANCEL /* PROGRAM CAN BE CANCELED */
KEY(7) /* PROTECT KEY ASSIGNED IS 7 */
SWAP /* PROGRAM IS SWAPPABLE */
NOPRIV /* PROGRAM IS NOT PRIVILEGED */
DSI /* REQUIRES DATA SET INTEGRITY */
PASS /* CANNOT BYPASS PASSWORD PROTECTION */
SYST /* PROGRAM IS A SYSTEM TASK */
AFF(NONE) /* NO CPU AFFINITY */
NOPREF /* NO PREFERRED STORAGE FRAMES */
Oracle TMA TCP for IMS makes use of a text configuration file which is read and processed during initialization to establish the configuration. Any text editor (such as the ISPF Editor) can be used to create the configuration file. CONFIGOT, the OTMA sample in the CONTROL distribution library is a sample configuration file which you may use as a starting point for creating configuration files tailored to your particular installation.
Place your completed configuration file in the configuration dataset allocated in the Task 1: Allocate z/OS Datasets section. A configuration file includes the following basic sections:
For detailed information about syntax and parameter definitions for the configuration file, refer to the Oracle Tuxedo Mainframe Adapter for TCP IMS User Guide.
SYSTEM parameters control the overall operational environment of Oracle TMA TCP for IMS. Because TMA TCP for IMS cannot “wait” on the IMS Message Queue, the queue is periodically interrogated (polled) to determine if any new work has arrived (for example, IMS Client requests or Server responses). Set the SleepTime parameter to specify the amount of time that TMA TCP for IMS “sleeps” (waits) during idle periods before checking the IMS Message Queue for work.
You must provide at least one GATEWAY TYPE=LOCAL statement to define access to your local (IMS) gateway by remote systems. In this statement, specify the following:
Make sure that remote systems are correctly configured with the corresponding IP Address, Port Number, Account ID (if used), and Password (if used). Otherwise, attempts by remote systems to connect to this gateway fail.
GATEWAY TYPE=REMOTE statements define access to remote systems by the IMS gateway. In particular, each GATEWAY TYPE=REMOTE statement specifies:
The IP Address, Port Number, Account ID, and Password must match the configuration of the remote system. Otherwise, attempts to establish an outbound session with the remote system fails.
SERVICE TYPE=REMOTE statements define remote services to which TMA TCP for IMS has access. Each statement specifies:
GATEWAY TYPE=REMOTE statement.| Note: | It is permissible to have more than one SERVICE TYPE=REMOTE statement for the same (local) service name. When this is the case, each statement must identify a different remote Logical Machine ID. This allows TMA TCP for IMS to “spread” requests for a particular service among multiple remote systems offering the service, thus balancing the load and improving overall throughput. |
SERVICE TYPE=LOCAL statements define local services offered by a local IMS host. There can be multiple SERVICE TYPE=LOCAL statements and multiple statements defining the same service, provided each specifies a different local IMSID. Each statement requires the following information:
The Local Service Name is the name used by an IMS Client transaction to request the service. The Remote Service Name is the name of the service as defined on the remote system.
| Note: | The local and remote service names can be different; however, the Remote Service Name must match the configuration of the remote system. |
IMSID (Logical IMS ID) that offers the service
The IMSID is a symbolic name that uniquely identifies an IMS system definition. This name must match a logical IMS ID (IMSID) specified in a HOST, TYPE=IMS statement.
You must create JCL to run the Oracle TMA TCP for IMS product. The following section specifies how to create JCL for running as an OTMA client.
When running the product as an OTMA client, TMA TCP for IMS runs in its own address space under z/OS as a started task or long running job. Member RUNOTM in the JCL distribution library is a sample job for executing TMA TCP for IMS.
When tailoring the JCL for your OTMA installation, pay particular attention to the following:
TIME=1440, since TMA TCP for IMS executes as a non-ending job.STEPLIB for the LE/370 runtime datasets, including SYS1.SCEERUN and SYS1.SCEELKED. Use whatever dataset names are appropriate for your installation.DD cards for SYSUDUMP and/or CEEDUMP. In the event of an abnormal termination (ABEND), LE/370 writes a formatted dump to CEEDUMP.DD card for SYSTCPD pointing to the TPC/IP Data file (for example, TCPIP.V3R1.DATA – change the dataset name as necessary to conform to your installation). This dataset is used by TCP/IP in the TMA TCP for IMS address space (when using IBM TCP/IP).DISP=MOD in the MSGLOG DD statement; new messages are appended to the end of the dataset (existing messages are preserved). If you want the Message Log to be overwritten with each new execution of TMA TCP for IMS, code DISP=OLD (or DISP=SHR) in the MSGLOG DD statement; existing messages are lost.Before you attempt to start TMA TCP for IMS the first time, make sure that the proper IMS definitions are in place.
If you are using RACF for security, you must set up a FACILITY Class Profile in RACF of IMSXCF.group.client. You can configure the group and client names for TMA TCP for IMS.
Start TMA TCP for IMS by submitting the JCL prepared in the Task 6: Create JCL to Run TMA TCP for IMS section.
For additional information on operating this product, refer to the Oracle Tuxedo Mainframe Adapter for TCP IMS User Guide.
When you start TMA TCP for IMS for the first time, you should do so in a controlled environment, using a small, simple configuration to methodically test the system to verify your installation and the configuration. For additional information on using this product, refer to the Oracle Tuxedo Mainframe Adapter for TCP IMS User Guide.
The Tuxedo Mainframe Adapter for TCP CD-ROM contains the following libraries and executable programs. After installing the TMA TCP for IMS software, verify that these libraries and programs are installed on your system.
|