Installation Guide

Installing Oracle Tuxedo Mainframe Adapter for TCP (CICS)

Installing Oracle Tuxedo Mainframe Adapter for TCP (CICS) (hereafter referenced as TMA TCP for CICS) consists of the following basic tasks and topics.

Note:

To upgrade from previous releases of eLink for Mainframe TCP, refer to Oracle Tuxedo Mainframe Adapter for TCP Release Notes.

Preparing for Installation

Before you install TMA TCP for CICS, complete the following tasks.

Task 1: Verify System Requirements

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.

Task 2: Check Pre-Installation Considerations

Verify that all block sizes in the supplied JCL are appropriate for the device types being used. By default, 3380 is assumed.

Installing TMA TCP for CICS

Complete the following tasks to install Oracle TMA TCP for CICS

Task 1: Allocate Temporary Data Sets

Allocate a temporary data set on z/OS direct access storage device (DASD) for the installation job as shown in the following example.

Note:

Specify either the Volume Serial parameter or the Generic Unit parameter, but not both.

Listing 5-1 Allocating the Install Data Set

Data Set Name:	YOURHLQ.TEMP.INSTALL
Volume serial:nnnnn				(Blank for authorized default volume)
Generic unit:				(Generic group name or unit address)
Space units:		TRACK		(BLKS, TRKS, CYLS, KB, MB or BYTES)
Primary quantity:	1			(In above units)
Secondary quantity:1				(In above units)
Directory blocks:0				(Zero for sequential data set) 
Record format:	FB
Record length:	80
Block size:	6160
Expiration date:				(YY/MM/DD, YYYY/MM/DD YY.DDD,
				YYYY.DDD in Julian form DDDD for
				retention period in days or blank)
Enter "/" to select option
Allocate Multiple Volumes

Task 2: Transfer the Installation JCL

The TMA TCP for CICS product is distributed on a single CD-ROM (with other members of the Oracle TMA TCP product). The TMA TCP for CICS distribution files are grouped under one of the following directory structures:

To FTP from UNIX to the mainframe, the distribution files are in:

/cdrom/unixmf/cics directory,

/cdrom is the directory where the drive is mounted.

To FTP from Windows to the mainframe, the distribution files are in:

D:\ntmf\cics

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 5-2 Uploading Distribution Files

% ftp zos-machine
Connected to zos-machine.
Name (zos-machine:unix-id): tso-id
331 Send password please.
Password: tso-password
230 tso-id is logged on.
Remote system type is z/OS.
ftp> quot site rec=fb
ftp> quot site lr=80
ftp> put INSTALL 'data set name allocated'
200 Port request OK.
125 Storing data set 'data set name allocated'
2749 bytes sent in 0.00 seconds (555.12 Kbytes/s)
ftp> quit
221 Quit command received. Goodbye.

Task 3: Create the PDS Libraries

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.

Note: This is an instream PROC; the variables are at the end of the PROC.

Modify the JOBCARD to your standards.
Modify the variable “YOURHLQ.” If you intend to rename them, modify the variables JCL, OBJECT, and SOURCE.
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.

The INSTALL JCL includes the name BEATCPC as part of the data set name. For example.

Listing 5-3 Sample INSTALL JCL

//JDOE1   JOB (INSTALL),'J DOE',NOTIFY=&SYSUID,
//         CLASS=C,MSGCLASS=X,MSGLEVEL=(1,1),TIME=1440
//*
//INSTALL  PROC   HLQ=,               ** YOUR HIGH LEVEL QUALIFIER
//         DASD=,                     ** DASD DEVICE TYPE
//         VOLUME=,                   ** SERIAL NUMBER OF TARGER VOLUME
//         BLKFB=6160,                ** BLKSIZE FOR FIXED BLOCK FILE
//*====================================================================
//*      THESE JCL WILL CREATE THE PDS FILES REQUIRED FOR
//*      THE INSTALLATION OF BEA TMA TCP FOR CICS
//*====================================================================
//         PDSCNTL='CONTROL',         ** 'YOURHLQ'.BEATCPC.CONTROL
//         PDSINCL='INCLUDE',         ** 'YOURHLQ'.BEATCPC.INCLUDE
//         PDSJCL='JCL',              ** 'YOURHLQ'.BEATCPC.JCL
//         PDSOBJS='OBJECT',          ** 'YOURHLQ'.BEATCPC.OBJECT
//         PDSLKED='PLKED',           ** 'YOURHLQ'.BEATCPC.PLKED
//         PDSSRCE='SOURCE'           ** 'YOURHLQ'.BEATCPC.SOURCE
//         PDSLKED='PLKED',           ** 'YOURHLQ'.BEATCPC.PLKED
//         PDSSRCE='SOURCE'           ** 'YOURHLQ'.BEATCPC.SOURCE
//*--------------------------------------------------------------------
//* WE RECOMMEND THAT YOU KEEP THE NODE 'BEATCPC' IN THE data set NAMES
//*--------------------------------------------------------------------
//EXEC  PGM=IEFBR14
//PDSCNTL  DD  DSNAME=&HLQ..BEATCPC.&PDSCNTL.,DISP=(NEW,CATLG,DELETE),
//             DCB=(DSORG=PO,RECFM=FB,LRECL=80,BLKSIZE=&BLKFB),
//             UNIT=&DASD,VOL=SER=&VOLUME,SPACE=(CYL,(1,1,5))
//*
//PDSJCL   DD  DSNAME=&HLQ..BEATCPC.&PDSJCL.,DISP=(NEW,CATLG,DELETE),
//             DCB=(DSORG=PO,RECFM=FB,LRECL=80,BLKSIZE=&BLKFB),
//             UNIT=&DASD,VOL=SER=&VOLUME,SPACE=(CYL,(1,1,5))
//*
//PDSINCL  DD  DSNAME=&HLQ..BEATCPC.&PDSINCL.,DISP=(NEW,CATLG,DELETE),
//             DCB=(DSORG=PO,RECFM=FB,LRECL=80,BLKSIZE=&BLKFB),
//             UNIT=&DASD,VOL=SER=&VOLUME,SPACE=(CYL,(1,1,5))
//*
//PDSOBJS  DD  DSNAME=&HLQ..BEATCPC.&PDSOBJS.,DISP=(NEW,CATLG,DELETE),
//             DCB=(DSORG=PO,RECFM=FB,LRECL=80,BLKSIZE=3200),
//             UNIT=&DASD,VOL=SER=&VOLUME,SPACE=(CYL,(3,1,5))
//*
//PDSLKED  DD  DSNAME=&HLQ..BEATCPC.&PDSLKED.,DISP=(NEW,CATLG,DELETE),
//             DCB=(DSORG=PO,RECFM=FB,LRECL=80,BLKSIZE=&BLKFB),
//             UNIT=&DASD,VOL=SER=&VOLUME,SPACE=(CYL,(3,1,5))
//*
//PDSSRCE  DD  DSNAME=&HLQ..BEATCPC.&PDSSRCE.,DISP=(NEW,CATLG,DELETE),
//             DCB=(DSORG=PO,RECFM=FB,LRECL=80,BLKSIZE=&BLKFB),
//             UNIT=&DASD,VOL=SER=&VOLUME,SPACE=(CYL,(1,1,5))
//*
//         PEND
//*--------------------------------------------------------------------
//*   CUSTOMIZE THE PARAMETER ACCORDING TO YOUR INSTALLATION
//*--------------------------------------------------------------------
//         EXEC  PROC=INSTALL,
//            DASD=3390,			** YOUR DEVICE TYPE
//            VOLUME=MVS201,		** YOUR VOLUME SERIAL NUMBER
//            HLQ='PRODUCTS.BEA.TMA',	** YOUR HIGH LEVEL QUALIFIER
//            PDSCNTL='CONTROL',		** BEATCPC  CONTROL
//            PDSINCL='INCLUDE',		** BEATCPC  INCLUDE
//            PDSJCL='JCL',			** BEATCPC  JCL
//            PDSOBJS='OBJECT',		** BEATCPC  OBJECT
//            PDSLKED='PLKED',		** BEATCPC  PLKED
//            PDSSRCE='SOURCE		'** BEATCPC  SOURCE

Task 4: Upload the Distribution Files

Upload 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:

To FTP the distribution files from UNIX to the mainframe, the files are in:

/cdrom/unixmf/cics

/cdrom is the directory where the drive is mounted.

To FTP files from Windows to the mainframe, the files are in:

D:\ntmf\cics

D: is the CD-ROM drive.

The previous directory structures include the following partitioned data sets.

Table 5-1 Partitioned Data Sets
From	To
`./control`	Your PDS for `CONTROL` (`YOURHLQ.BEATCPC.CONTROL`) (ASCII mode)
`./jcl`	Your PDS for JCL (`YOURHLQ.BEATCPC.JCL`) (ASCII mode)
`./source`	Your PDS for `SOURCE` (`YOURHLQ.BEATCPC.SOURCE`) (ASCII mode)
`./include`	Your PDS for `INCLUDE` (`YOURHLQ.BEATCPC.INCLUDE`) (ASCII mode)
`./object`	Your PDS for `OBJECT` (`YOURHLQ.BEATCPC.OBJECT`) (Binary mode)
`./plked`	Your PDS for `PLKED` (`YOURHLQ.BEATCPC.PLKED`) (Binary mode)

Listing 5-4 Uploading Distribution Files Using FTP

% ftp zos-machine
Connected to zos-machine.
Name (beavs:tso-id):
331 Send password please.
Password: tso-password
230 tso-id is logged on.
Remote system type is z/OS.
ftp> prompt off
Interactive mode off
ftp> quot site rec=fb
200 SITE command was accepted
ftp> quot site lr=80
200 SITE command was accepted

Upload the CONTROL files.

Note:

You must set ASCII mode on.

Listing 5-5 Upload control Files

ftp> lcd /cdrom/unixmf/cics/control
Local directory now /cdrom/unixmf/cics/control
ftp> cd 'YOURHLQ.BEATCPC.CONTROL'
250 "'YOURHLQ.BEATCPC.CONTROL'" partitioned data set is working directory
ftp>ascii
200 Representation type is Ascii
ftp> mput *
local: CSDU remote: CSDU
200 Port request OK.
125 Storing data set "YOURHLQ".BEATCPC.CONTROL(CSDU)
250 Transfer completed successfully.
5740 bytes sent in 0.01 seconds (747.10 Kbytes/s)
.
.
.

Upload the JCL files.

Note:

You must set ASCII mode on.

Listing 5-6 Uploading JCL Files

ftp> lcd /cdrom/unixmf/cics/jcl
Local directory now /cdrom/unixmf/cics/jcl
ftp> cd 'YOURHLQ.BEATCPC.JCL'
250 "'YOURHLQ.BEATCPC.JCL'" partitioned data set is working directory.
ftp>ascii
200 Representation type is Ascii
ftp> mput *
local: BLDVSAM remote: BLDVSAM
200 Port request OK.
125 Storing data set "YOURHLQ".BEATCPC.JCL(BLDVSAM)
250 Transfer completed successfully.
2214 bytes sent in 0.00 seconds (563.49 Kbytes/s)
.
.
.

Upload the SOURCE files.

Note:

You must set ASCII mode on.

Listing 5-7 Uploading SOURCE Files

ftp> lcd /cdrom/unixmf/cics/source
Local directory now /cdrom/unixmf/cics/source
ftp> cd 'YOURHLQ.BEATCPC.SOURCE'
250 "'YOURHLQ.BEATCPC.SOURCE'" partitioned data set is working directory.
ftp>ascii
200 Representation type is Ascii
ftp> mput *
local: BEACCLN1 remote: BEACCLN1
200 Port request OK.
125 Storing data set YOURLHQ.BEATCPC.SOURCE(BEACCLN1)
250 Transfer completed successfully.
10578 bytes sent in 0.01 seconds (1013.85 Kbytes/s)
.
.
.

Upload the INCLUDE files.

Note:

You must set ASCII mode on.

Listing 5-8 Uploading INCLUDE Files

ftp> ascii
ftp> lcd /cdrom/unixmf/cics/include
ftp> cd ’"YOURHLQ".BEATCPC.INCLUDE’
250 "’YOURHLQ.BEATCPC.INLUDE’" partitioned data set is working directory
ftp>ascii
200 Representation type is Ascii
ftp> mput *
200 Port request OK.
125 Storing data set "YOURHLQ".BEATCPC.INCLUDE’(CLIENT)
250 Transfer completed successfully.
local: CLIENT remote: CLIENT
3736 bytes sent in 0.0081 seconds (4.5e+02 Kbytes/s)
.
.
.

Upload the OBJECT files.

Note:

You must set binary mode on.

Listing 5-9 Uploading OBJECT Files

ftp> binary
200 Representation type is IMAGE.
ftp> lcd /cdrom/unixmf/cics/object
Local directory now /cdrom/unixmf/cics/object
ftp> cd 'YOURHLQ.BEATCPC.OBJECT'
250 "'YOURHLQ.BEATCPC.OBJECT'" partitioned data set is working directory.
ftp>binary
200 Representation type is Image
ftp> mput *
local: BEACFGSV remote: BEACFGSV
200 Port request OK.
125 Storing data set "YOURHLQ".BEATCPC.OBJECT(BEACFGSV)
250 Transfer completed successfully.
6240 bytes sent in 0.00 seconds (1466.96 Kbytes/s)
.
.
.

Upload the PLKED files.

Note:

You must set binary mode on.

Listing 5-10 Uploading PLKED Files

ftp> binary
200 Representation type is Image
ftp> lcd /cdrom/unixmf/plked
ftp> cd ’"YOURHLQ".BEATCPC.PLKED’
250 "’"YOURHLQ.BEATCPC.PLKED’" partitioned data set is working directory
ftp>binary
200 Representation type is Image
ftp> mput *
200 Port request OK.
125 Storing data set "YOURHLQ.BEATCPC.PLKED(BEACIC00)
250 Transfer completed successfully.
local: BEACIC00 remote: BEACIC00
64560 bytes sent in 0.7 seconds (90 Kbytes/s)
.
.
.

Verify 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.

Task 5: Define the CICS VSAM Files

Define the CICS VSAM files (Connections, Requesters, Service Names, User Connection, Inbound Service).

Modify DELETE/DEFINE control cards VCON, VREQ, VSVC, VUSR, and VISN in the PDS "YOURHLQ".BEATCPC.CONTROL. Listing 5-11 is an example of a modified DELETE/DEFINE.

Listing 5-11 Sample DELETE/DEFINE Control Card

DELETE 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.

For the BLDVSAM JCL, complete the following steps.

Modify the JOBCARD to your standards.
Modify YOURHLQ.BEATCPC.XXXX, where XXXX is BEAVCON, BEAVREQ, BEAVSVC, BEAVUSR, and BEAVISN.
Submit BLDVSAM.

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 no extension
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.

Task 6: Verify Contents of PROCS

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.

You may need to modify them to meet your standards. You will need to review the following:

All references to CICS and TCP/IP data set names.
The data set names associated with the STEPLIB, SYSMSGS, SYSXMSCS, SYSPATH, and SYSLIB DD names.
Unit = references.

Task 7: Change Resource Names (Optional)

The default names for Oracle TMA TCP for CICS Mapsets, Programs, Transids, and VSAM data sets are listed in Appendix A, “Changing Resource Names.” If you want to use a different naming convention, use the procedure for changing names included after each table.

Note:

You must have the C 370 compiler to customize resource names.

Task 8: Define the CICS Table Entries

Verify the CICS table entry definitions (PCTs, PPTs, FCTs) in CSDU (from the PDS "YOURHLQ".BEATCPC.CONTROL).
Modify the group and list name in CSDU (from the PDS "YOURHLQ".BEATCPC.CONTROL).
In the JCL in CSDUPD (from the PDS "YOURHLQ".BEATCPC.JCL), complete the following steps.

Modify the JOBCARD to your standards.
Modify the STEPLIB and DFHCSD data set names.
Modify the SYSIN DSN=YOURHLQ.BEATPC.CONTROL.
Submit CSDUPD.
Verify the results.

Note: A “COND CODE 0004” may result due to the DELETE commands for non-existent CSD objects.

Task 9: Build TMA TCP for CICS Executables

To build the executables for Oracle TMA TCP for CICS, you need to complete the following tasks.

If there is not a PDS allocated where the executables for your CICS region reside, allocate such a PDS before running any JCL that builds executables.
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.

Modify the JOBCARD to your standards.
Modify the PROCS JCLLIB card with the correct HLQ.
Modify the variables YOURHLQ, PDSOBJS and LNKLIB for your PDS.

Note: LNKLIB is where your CICS region executable binary files reside.

Modify the variable PROG, if you renamed mapsets.
Submit MAKLMAP.
Verify the results.

Complete one of the following procedures depending on your compiler:

Pre-Link/Link TMA TCP for CICS

The following sections explain the procedures for linking programs and mapsets prior to running the Oracle TMA TCP for CICS product.

Note:

The following sections apply for a C 370 compiler.

Linking the CICS Admin Programs

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.

Modify the JOBCARD to your standards.
Modify the PROCS JCLLIB card with the correct HLQ.
Modify the variables YOURHLQ, PDSOBJS, TCPLIB and LNKLIB for your PDS.

Note: LNKLIB is where your CICS region executable binary files reside.

Modify the LKED.SYSIN program names, if you renamed programs.
Submit MAKL1.
Verify the results.

Note: A “COND CODE = 004” is normal.

Linking the CICS Utility Programs

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.

Modify the JOBCARD to your standards.
Modify the PROCS JCLLIB card with the correct HLQ.
Modify the variables YOURHLQ, PDSOBJS, TCPLIB and LNKLIB for your PDS.

Note: LNKLIB is where your CICS region executable binary files reside.

Modify the LKED.SYSIN program names, if you renamed programs.
Submit MAKL0.
Verify the results.

Note: A “COND CODE = 004” is normal.

Linking the CICS TCP Programs

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.

Modify the JOBCARD to your standards.
Modify the variables YOURHLQ, PDSOBJS, TCPLIB and LNKLIB for your PDS.

Note: LNKLIB is where your CICS region executable binary file resides.

Modify the INCLUDE OBJECT program name, if you renamed programs.
Modify the LKED.SYSIN program names, if you renamed programs.
Submit MAKL3.
Verify the results.

Note: A “COND CODE = 004” is normal.

Linking without the C 370 Compiler

If you do NOT have the C 370 compiler, use the following procedure to Linkedit the PreLinked objects. Link the Prelinked objects of the following programs.

CICS TCP Programs (Requester and Handler).
CICS Utility Programs (Pre-Requester, Application Handler, Shutdown, and Configuration Converter).
CICS Admin Programs (MainMenu, Connection, Requester, Service Name).

In the JCL in MAKLKED (from the PDS "YOURHLQ.BEATCPC.JCL"), complete the following steps.

Modify the JOBCARD to your standards.
Modify the variables YOURHLQ, TCPLIB and LNKLIB for your PDS.

Note: LNKLIB is where your CICS region executable binary file resides.

Submit MAKLKED.
Verify the results.

Task 10: Verify the CICS Setup

Log on to your CICS region to install and verify the components you set up for Oracle TMA TCP for CICS.

CEDA INSTALL GROUP(____)

This is the group name you used in CSDU

CEMT INQUIRE PROG(____)

Verify the mapsets and programs

CEMT INQUIRE TRAN (____)

Verify the transids

CEMT INQUIRE FILE(____)

Verify the VSAM files

Task 11: Assemble and Link the CICS DCT

Note:

Recent releases of CICS allow this task to be with CSD instead of this method.

Add the following entries to the CICS DCT.

Entry
BEALOG DFHDCT TYPE=SDSCI,
DSCNAME=BEALOG,
BLKSIZE=136,
RECSIZE=132,
RECFORM=VARUNB,
TYPEFLE=OUTPUT,
BUFNO=1
BEAL DFHDCT TYPE=EXTRA,
DESTID=BEAL,
DSCNAME=BEALOG

Assemble and link the DCT.

Task 12: Modify the CICS Startup JCL

Add the Oracle Tuxedo Mainframe Adapter load library (LNKLIB) to the DFHRPL concatenation.
Add the following DD statement to CICS file concatenation.

   //BEALOG DD SYSOUT=*,DCB=(DSORG=PS,RECFM=V,BLKSIZE=136)

Add DD statement to make the connection between the logical names of the VSAM files and the DSN.

Note:

If DSN statements were added to the CSDU, this step is not necessary.

The following is an example of a CICS startup JCL.

Listing 5-12 Sample CICS Startup JCL with TMA TCP additions

//CICSREG JOB
//CICSCNTL EXEC PGM=IDCAMS,REGION=1M
//SYSPRINT DD SYSOUT=*
//SYSIN DD DISP=SHR,DSN=CICSTS31.SYSIN(DFHRCYES)
//DTCNTL EXEC PGM=IDCAMS,REGION=1M
//SYSPRINT DD SYSOUT=*
//SYSIN DD DISP=SHR,DSN=CICSTS31.SYSIN(DFHRCNO)
//*
//CICS EXEC PGM=DFHSIP, REGION=32M, TIME=1439, COND=(1,NE,CICSCNTL),
// =START=COLD,SYSIN,SEC=NO,GRPLIST=ETPLIST
//STEPLIB DD DISP=SHR,DSN=CICSTS31.SVTSC.SDFHAUTH
// DD DISP=SHR,DSN=CICSTS31.SDFHAUTH
// DD DISP=SHR,DSN=MASTCAT.MQM112.SCSQAUTH
// DD DISP=SHR,DSN=COB2140.COB2CICS.MODLIB
// DD DISP=SHR,DSN=C370.SEDCLINK
// DD DISP=SHR,DSN=ADLE370.V1R3M0.SCEECICS
// DD DISP=SHR,DSN=ADLE370.V1R3M0.SCEERUN
//DFHRPL DD DISP=SHR,DSN=CICSTS31.SVTSC.SDFHLOAD
// DD DISP=SHR,DSN=CICSTS31.SDFHLOAD
// DD DISP=SHR,DSN=BEA.BEA100.BEALOAD
// DD DISP=SHR,DSN=TCPIP.V3R1.SEZALINK
// DD DISP=SHR,DSN=TCPIP.V3R1.SEZATCP
// DD DISP=SHR,DSN=MQM112.SCSQCICS
// DD DISP=SHR,DSN=MQM112.SCSQLOAD
// DD DISP=SHR,DSN=COB2140.COB2CICS
// DD DISP=SHR,DSN=MASTCAT.COB2140.COB2LIB
// DD DISP=SHR,DSN=MASTCAT.PLI230.PLILINK
// DD DISP=SHR,DSN=C370.SEDCLINK
// DD DISP=SHR,DSN=ERW121.SERWLOAD
// DD DISP=SHR,DSN=ADLE370.V1R3M0.SCEECICS
// DD DISP=SHR,DSN=ADLE370.V1R3M0.SCEERUN
//SYSIN DD DISP=SHR,DSN=CICSTS31.CICS.SYSIN(TCICS)
//DFHCSD DD DISP=SHR,DSN=CICSTS31.DFHCSD
//DFHCMACD DD DISP=SHR,DSN=CICSTS31.DFHCMACD
//DFHJ01A DD DISP=SHR,DSN=CICSTS31.CICS.DFHJ01A
//DFHJ01B DD DISP=SHR,DSN=CICSTS31.CICS.DFHJ01B
//DFHJ01X DD DISP=SHR,DSN=CICSTS31.CICS.DFHJ01X
//DFHAUXT DD DISP=SHR, DSN=CICSTS31.CICS.DFHAUXT,
//DFHBUXT DD DISP=SHR, DSN=CICSTS31.CICS.DFHBUXT,
//DFHDMPA DD DISP=SHR,DSN=CICSTS31.CICS.DFHDMPA
//DFHDMPB DD DISP=SHR,DSN=CICSTS31.CICS.DFHDMPB
//DFHRSD DD DISP=SHR,DSN=CICSTS31.CICS.DFHRSD
//DFHGCD DD DISP=SHR,DSN=CICSTS31.CICS.DFHGCD
//DFHLCD DD DISP=SHR,DSN=CICSTS31.CICS.DFHLCD
//DFHXRMSG DD DISP=SHR, DSN=CICSTS31.CNTL.CICS.DFHXRMSG
//DFHXRCTL DD DISP=SHR,DSN=CICSTS31.CNTL.CICS.DFHXRCTL
//DFHTEMP DD DISP=SHR,DSN=CICSTS31.CNTL.CICS.DFHTEMP
//DFHINTRA DD DISP=SHR,DSN=CICSTS31.CNTL.CICS.DFHINTRA
//DFHJACD DD DISP=SHR,DSN=CICSTS31.CICS.DFHJACD
//DFHJPDS DD DISP=SHR,DSN=CICSTS31.DFHJPDS
//DFHJOUT DD SYSOUT=(A,INTRDR)
//DFHCXRF DD SYSOUT=X
//MQMMSG DD SYSOUT=*
//LOGUSR DD SYSOUT=*, DCB=(DSORG=PS,RECFM=V, BLKSIZE=136)
//MSGUSR DD SYSOUT=*, DCB=(DSORG=PS,RECFM=V, BLKSIZE=136)
//TCPDATA DD SYSOUT=*, DCB=(DSORG=PS,RECFM=V, BLKSIZE=136)
//BEALOG DD SYSOUT=*, DCB=(DSORG=PS,RECFM=V, BLKSIZE=136) ** BEA Connect
//COUT DD SYSOUT=*, DCB=(DSORG=PS,RECFM=V, BLKSIZE=137)
//PLIMSG DD SYSOUT=*, DCB=(DSORG=PS,RECFM=V, BLKSIZE=137)
//COUT DD SYSOUT=*, DCB=(DSORG=PS,RECFM=V, BLKSIZE=137)
//SYSABEND DD SYSOUT=*
//TRACEOUT DD SYSOUT=*
//PRINTER DD SYSOUT=*,DCB=BLKSIZE=121
//*
//PRTDMPA EXEC PGM=DFHDUP, PARM=SINGLE, REGION=0M, COND=(1,NE,DTCNTL)
//STEPLIB DD DSN=CICSTS31.SDFHLOAD,DISP=SHR
//SYSIN DD DUMMY
//DFHDMPDS DD DISP=SHR,DSN=CICSTS31.CICS.DFHDMPA
//DFHTINDX DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//DFHPRINT DD SYSOUT=*
//*
//PRTDMPB EXEC PGM=DFHDUP, PARM=SINGLE, REGION=0M, COND=(1,NE,DTCNTL)
//STEPLIB DD DSN=CICSTS31.SDFHLOAD,DISP=SHR
//SYSIN DD DUMMY
//DFHDMPDS DD DISP=SHR,DSN=CICSTS31.CICS.DFHDMPB
//DFHTINDX DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//DFHPRINT DD SYSOUT=*
//*
//* PRTAUXT EXEC PGM=DFHTUP, REGION=0M, COND=(1,NE,DTCNTL)
//* STEPLIB DD DSN=CICSTS31.SDFHLOAD,DISP=SHR
//* DFHAUXT DD DISP=OLD,DSN=CICSTS31.CICS.DFHAUXT
//* DFHAXPRT DD SYSOUT=*
//* DFHAXPRM DD DUMMY
//*
//PRTBUXT EXEC PGM=DFHTUP, REGION=0M, COND=(1,NE,DTCNTL)
//STEPLIB DD DSN=CICSTS31.SDFHLOAD,DISP=SHR
//DFHAUXT DD DISP=SHR,DSN=CICSTS31.CICS.DFHBUXT
//DFHAXPRT DD SYSOUT=*
//DFHAXPRM DD DUMMY

List of Distribution Files and Members

The following tables list and describe the members that make up each distribution partitioned data set.