Previous     Contents     Index     DocHome     Next     
iPlanet Application Server Enterprise Connector for CICS Administrator's Guide



Chapter 3   Installing the Mainframe Component


After you install the iPlanet Application Server Enterprise Connector for CICS you need to install the mainframe component.

This chapter describes the following topics:



Overview

You can connect the CICS Connector to the IBM mainframe in one of the following ways:

  • via TCP/IP

    This method is used when the iPlanet Application Server installed on Windows NT or Solaris is connected via TCP/IP to a Relay component on OS/390 (MVS). The Relay communicates over the APPC with CICS. See Figure 3-1.

Figure 3-1    Installing the Connector via TCP/IP

  • via Direct APPC/SNA

    This method is used when the iPlanet Application Server installed on Windows NT is connected via direct APPC connection to CICS on OS/390 (MVS). See Figure 3-2.

Figure 3-2    Installing the Connector via Direct APPC Using SNA

When you complete the installation either via TCP/IP or via direct APPC using SNA installation, the PhoneBook sample application is available for end-to-end installation verification of the iPlanet Application Server Enterprise Connector for CICS. See Appendix A "Operating the TELCO Sample".



Installing and Configuring CICS


The CICS components are supplied as downloaded PC files on the iPlanet Application Server Enterprise Connector for CICS installation media. You must upload the required Partitioned Data Sets (PDS) to MVS as part of the mainframe installation using either FTPor a 3270 emulator file transfer utility.


To Upload the Library Files on Windows NT

Run the mfinst.bat installation utility from the following directory:

\iPlanet\iAS6\ias\APPS\adapters\cics\backend


To Upload the Library Files on Solaris

Run the file mfinst.sh installation utility from the following directory:

<instdir>/iAS6/ias/APPS/adapters/cics/backend

The Installer Dialog Box appears. See Figure 3-3.

Figure 3-3    Installer Dialog Box

The Installer Dialog Box contains information about the following fields:


User and Host Information

Table 3-1 lists names and IDs used to connect to the CICS system.

Table 3-1    User and Host Information

Variable  

Definition  

Host Name  

TCP/IP Host address where the CICS system is located.  

Userid  

The administrator's ID on the mainframe.  

Password  

Password of administrator's ID  

Permanent Prefix  

The dataset prefix for the installation libraries. This prefix affects the permanent names of the CICS Installation Dataset, the CICS Load Dataset, the Relay Installation Datataset, the Relay Load Dataset, and the CICS DBRM dataset.  


CICS Installation Dataset

The CICS Installation Dataset contains jobs for the CICS installation. Table 3-2 lists variables and definitions for the CICS Installation Dataset.

Table 3-2    CICS Installation Dataset

Variable  

Definition  

Temp Name  

The temporary name assigned to the installation dataset during upload.  

Permanent name  

The permanent name assigned to the installation dataset. The prefix of this name is the Permanent prefix defined in the User and Host information.  


CICS Load Dataset

The CICS Load Dataset contains modules for the CICS connector. Table 3-3 lists variables and definitions for the CICS Load Dataset parameters. 

Table 3-3    CICS Load Dataset

Variable  

Definition  

Temp Name  

The temporary name assigned to the CICS Load dataset during upload.  

Permanent name  

The permanent name assigned to the CICS Load dataset.  

 


Relay Installation Dataset

The Relay Installation Dataset contains jobs for the Relay installation. Table 3-4 lists and defines parameters for the Relay Installation Dataset. 

Table 3-4    Relay Installation Dataset

Variable  

Definition  

Temp Name  

The temporary name assigned to the Relay Installation dataset during upload.  

Permanent name  

The permanent name assigned to the Relay Installation dataset.  


Relay Load Dataset

The Relay Load Dataset contains modules for the component. Table 3-5 lists and defines parameters for the Relay Load Dataset.

Table 3-5    Relay Load Datase

Variable  

Definition  

Temp Name  

The temporary name assigned to the Relay Load dataset during upload  

Permanent name  

The permanent name assigned to the Relay Load dataset.  


CICS DBRM

The CICS DBRM is the Data Base Request Module library. Table 3-6 lists and defines parameters for the CICS DBRM.

Table 3-6    CICS DBRM

Variable  

Definition  

Temp Name  

The temporary name assigned to the CICS DBRM dataset during upload.  

Permanent name  

The permanent name assigned to the CICS DBRM dataset.  


Unit and Volume Name

The Unit and Volume Name lists the assigned names for the Unit and Volume used.

Table 3-7    Unit and Volume Name

Variable  

Definition  

Unit name  

Disk unit name.  

Volume name  

Disk volume name.  

Figure 3-4 shows an example of a completed installer dialog box.

Figure 3-4    Completed Installer Dialog Box.

  1. Press OK to continue. Figure 3-5 displays the generated JCL file.

Figure 3-5    Management Console Editor - Generated JCL    

The JCL editor modifies the JCL to fit your mainframe environment according to the instructions as viewed in the screen capture above. All of the JCL file can be changed, except for the job name. To apply the changes, choose File and then Save before submitting the job.


To Submit JCL for Execution

  1. Choose File>Exit from the menu bar.

    The utility will begin to FTP the files to the mainframe, and submit the JCL file to extract the files into permanent libraries.

  2. Once a job (JCL) finishes, outputs from the job are displayed as shown in Figure 3-6.

Figure 3-6    Management Console Editor: Outputs from job (JCL)

Review the job output.

  1. Click File>Exit to close the window.

  2. Go to Configuring CICS on the Mainframe.


Uploading MVS Library Files via TCP/IP

If you have TCP/IP configured on your mainframe, you can use the supplied installation program from within the installer to tailor and upload the libraries. If TCP/IP is not installed, follow the instructions given as described in Uploading MVS Library Files Using 3270 File Transfer.


Uploading MVS Library Files Using 3270 File Transfer

The following procedure applies to users that use a 3270 emulation software and its file transfer capability.


To Transfer Libraries to MVS

  1. Allocate four data sets on MVS with 1recl=80, blksize=3120, recfm=fb.

    For example:

    • IAS.CICS.LOAD.XMIT

    • IAS.CICS.INSTALL.XMIT

    • IAS.RELAY.INSTALL.XMIT

    • IAS.RELAY.LOAD.XMIT

  2. Use the 3270 emulation program to transfer the following files to the respective MVS data sets. Use the MVS/TSO binary transfer type and fixed-file option.

    • LOAD.XMT

    • INSTALL.XMT

    • RELINST.XMT

    • RELLOAD.XMT

    These files are found in

    <instdir>\IAS\APPS\adapters\cics\backend

    on Windows NT.

  3. Issue the following TSO command:

    RECEIVE INDATASET(IAS.CICS.LOAD.XMIT)

  4. At the prompt, enter the following:

    DATASET(IAS4CICS.V6R0M0.CICS.LOAD)

    where IAS4CICS.V6R0M0.CICS.LOAD is the name of the product load library.

  5. Issue the following TSO command:

    RECEIVE INDATASET(IAS.CICS.INSTALL.XMIT)

  6. At the prompt, enter the following:

    DATASET(IAS4CICS.V6R0M0.CICS.INST)

    where IAS4CICS.V6R0M0.CICS.INST is the name of the installation library.

  7. Issue the following TSO command:

    RECEIVE INDATASET(IAS.RELAY.INSTALL.XMIT)

  8. At the prompt, enter the following:

    DATASET(IAS4CICS.V6R0M0.RELAY.INST)

    where IAS4CICS.V6R0M0.RELAY.INST is the name of the installation library for the RELAY component.

  9. Issue the following TSO command:

    RECEIVE INDATASET(IAS.RELAY.LOAD.XMIT)

  10. At the prompt, enter the following:

    DATASET(IAS4CICS.V6R0M0.RELAY.LOAD)

    where IAS4CICS.V6R0M0.RELAY.LOAD is the name of the load library for the RELAY component.


Configuring CICS on the Mainframe

You need to configure the components to install the connection to the mainframe computer. The following steps provide information on how to perform this task.


To Configure the CICS Components

  1. Ensure APPC Logmode Entry is Present.

  2. Define the Sample CICS Application in VTAM.

  3. Define a Remote PU for each NT Server Platform Connected Directly to CICS via APPC

  4. Create the VSAM Datasets Using DEFFILES Member.

  5. Update the CICS Resource Definitions by Running the Supplied CICSDEF.

  6. Install a Resource Group for the APPC Connection.

  7. Add the Product Load Library to CICS DFHRPL List.

  8. Define the Necessary Entries in the Application Table VSAM File.


Ensure APPC Logmode Entry is Present

Code Example 3-1 demonstrates definitions of APPC Logmode entry in the MODE TABLE associated with the CICS VTAM definition.

A MODE entry with the same name must be defined in the MODE TABLE associated with APPC/MVS LU (logical unit).

Code Example 3-1    Creating the VTAM mode table MTAPPC

//MODETAB JOB
//* ANY SITE PROCEDURE FOR ASSEMBLY AND LINK CAN BE USED
//* THIS SAMPLE IS USING HIGH LEVEL ASSEMBLER
//* IN LATEST OS/390 VERSIONS, IEWL WILL INVOKE THE DFSMS BINDER
//ASM EXEC PGM=ASMA90,REGION=5048K,
// PARM='OBJECT,NODECK,LIST,XREF(SHORT)'
//SYSLIB DD DSN=SYS1.SISTMAC1,DISP=SHR
//SYSUT1 DD UNIT=SYSDA,SPACE=(CYL,(10,5))
//SYSIN DD *
MTAPPC MODETAB
APPCMODE MODEENT LOGMODE=APPCMODE, *
FMPROF=X'13', *
TSPROF=X'07', *
PRIPROT=X'B0', *
SECPROT=X'B0', *
COMPROT=X'D0B1', *
RUSIZES=X'8585', *
PSERVIC=X'060200000000000000000300'
MODEEND
END
//SYSLIN DD DSN=&&LOADME,DISP=(,PASS),UNIT=SYSDA,
// SPACE=(TRK,(30,10),RLSE)
//SYSPRINT DD SYSOUT=*
//LKED EXEC PGM=IEWL,PARM='MAP,LET,LIST',REGION=912K,
// COND=(8,LT,ASM)
//SYSLIB DD DSN=SYS1.MACLIB,DISP=SHR
//SYSLMOD DD DISP=SHR,DSN=SYS1.VTAMLIB
//SYSUT1 DD UNIT=SYSDA,SPACE=(CYL,(3,2)),DSN=&SYSUT1
//SYSPRINT DD SYSOUT=*
//SYSLIN DD DSN=&&LOADME,DISP=(OLD,DELETE)
// DD *
NAME MTAPPC(R)


Define the Sample CICS Application in VTAM

Code Example 3-2 is a sample VTAM definition for CICS. In most cases, CICS is already defined and running.

Code Example 3-2    Sample VTAM major node for CICS  

SUNCICS2 VBUILD TYPE=APPL APPLICATION MAJOR NODE

A06CICS2 APPL EAS=160, ESTIMATED CONCURRENT SESSIONS *

ACBNAME=A06CICS2, APPLID FOR ACB *

MODETAB=MTAPPC, *

PARSESS=YES, *

SONSCIP=YES, *

AUTH=(ACQ,VPACE,PASS) CICS CAN ACQUIRE & PASS TMLS


Note

Do not add APPC=YES to the CICS VTAM definition.



Define a Remote PU for each NT Server Platform Connected Directly to CICS via APPC

If your application server is connected directly to CICS (using APPC connections), define the remote PU (the application server machine) to VTAM and CICS.

Refer to Code Example 3-3.

Code Example 3-3    Sample PU and LU6.2 Definition for Windows NT 

*/*

SWSHMUEL VBUILD TYPE=SWNET

PUSHMUEL PU PUTYPE=2,ADDR=C1,MAXDATA=1456, *

CPNAME=SHMUELNT

SHMUELNT LU LOCADDR=0


Create the VSAM Datasets Using DEFFILES Member

Create the VSAM datasets using DEFFILES member in CICS installation library. See Code Example 3-4.

Code Example 3-4    DEFFILES to Define VSAM Datasets Used by CICS Components  
//IASCFILE JOB NOTIFY=&SYSUID

// EXEC PGM=IDCAMS

//*******************************************************************

//* DEFINE IAS4CICS VSAM FILES

//*******************************************************************

//SYSPRINT DD SYSOUT=*

//SYSIN DD *

/* ************************************************************* */

/* *** DELETE AND DEFINE OF THE CICS APPLTAB FILE *** */

/* ************************************************************* */

DELETE IAS.APPLTAB.CICS NOERASE CLUSTER

SET MAXCC=0

DEFINE CLUSTER( NAME(IAS.APPLTAB.CICS) -

INDEXED -

RECORDSIZE(359 359) -

KEY(64 0) -

REUSE -

SHR(2 3) -

SPEED -

VOLUME(SUNL01) ) -

DATA( NAME(IAS.APPLTAB.CICS.DATA) -

CISZ(8192) -

TRACKS(2 2)) -

INDEX( NAME(IAS.APPLTAB.CICS.INDEX) -

CISZ(1024) -

TRACKS(1 1))

/* ************************************************************* */

/* *** DELETE AND DEFINE OF THE CICS LOGGING FILE *** */

/* ************************************************************* */

DELETE IAS.LOGFILE.CICS ERASE CLUSTER

SET MAXCC=0

DEFINE CLUSTER( NAME(IAS.LOGFILE.CICS) -

INDEXED -

RECORDSIZE(65 32650) -

KEY(18 0) -

REUSE -

SHR(2 3) -

SPEED -

VOLUME(SUNL01) ) -

DATA( NAME(IAS.LOGFILE.CICS.DATA) -

CISZ(32768) -

CYLINDERS(4 1)) -

INDEX( NAME(IAS.LOGFILE.CICS.INDEX) -

CISZ(1024) -

TRACKS(3 1))


Update the CICS Resource Definitions by Running the Supplied CICSDEF

Update the CICS resource definitions by running the supplied CICSDEF from the installation library.

Refer to Code Example 3-5.

When using direct APPC connection from Windows NT, refer to Code Example 3-6 as a definition for CICS connection and sessions.

Code Example 3-5    CICSDEF to Define CICS Components 

//CICSDEF JOB CLASS=A,MSGCLASS=K

//*

//* SAMPLE JOB TO DEFINE THE IAS FOR CICS COMPONENTS TO CICS

//* CHECK THE DSN= PARAMETERS FOR THE STEPLIB AND DFHCSD DD CARDS

//* CHANGE 'CICSLIST' TO THE CICS STARTUP LIST NAME

//* SEE NOTES FOR EACH SECTION BELOW (FILES, PROGRAMS, ETC.)

//*

//CSDUP EXEC PGM=DFHCSDUP

//STEPLIB DD DSN=CICS.CICS.SDFHAUTH,DISP=SHR

//DFHCSD DD DSN=CICS.DFHCSD,DISP=SHR

//SYSPRINT DD SYSOUT=*

//SYSIN DD *

***

*** DEFINITIONS FOR APPLICATION TABLE AND LOG FILES

***

***

DEFINE FILE(SRVAPLT) GROUP(IAS)

DSNAME(IAS.APPLTAB.CICS) DISPOSITION(SHARE)

ADD(YES) BROWSE(YES) DELETE(YES) READ(YES) UPDATE(YES)

RECORDFORMAT(F) STATUS(ENABLED) OPENTIME(FIRSTREF)

JOURNAL(01) STRINGS(10) DATABUFFERS(11)

DESCRIPTION(IAS APPLICATION TABLE)

DEFINE FILE(SRVLOGF) GROUP(IAS)

DSNAME(IAS.LOGFILE.CICS) DISPOSITION(SHARE)

ADD(YES) BROWSE(YES) DELETE(YES) READ(YES) UPDATE(YES)

RECORDFORMAT(F) STATUS(ENABLED) OPENTIME(FIRSTREF)

JOURNAL(01) STRINGS(10) DATABUFFERS(11)

DESCRIPTION(IAS LOG/RECOVERY FILE)

***

*** DEFINITIONS FOR TRANSACTIONS

***

DEFINE TRANSACTION(SRVU) GROUP(IAS) PROGRAM(SRVMAINT)

DESCRIPTION(IAS APPLICATION TABLE MAINTENANCE)

DEFINE TRANSACTION(SRVW) GROUP(IAS) PROGRAM(SRVMMTSS)

DEFINE TRANSACTION(SRVR) GROUP(IAS) PROGRAM(SRVRCVM)

DEFINE TRANSACTION(SRVS) GROUP(IAS) PROGRAM(SRVGTBLS)

DEFINE TRANSACTION(SRVL) GROUP(IAS) PROGRAM(SRVLINK)

DEFINE TRANSACTION(SRVX) GROUP(IAS) PROGRAM(SRVXLINK)

DESCRIPTION(IAS X-LINK UNIT)

DEFINE TRANSACTION(SRLA) GROUP(IAS) PROGRAM(SRVRLAA)

DEFINE TRANSACTION(SRT1) GROUP(IAS) PROGRAM(SRVTEST1)

DESCRIPTION(IAS SAMPLE SERVICE - SCENARIO 1)

DEFINE TRANSACTION(SRT2) GROUP(IAS) PROGRAM(SRVTEST2)

DESCRIPTION(IAS SAMPLE SERVICE - SCENARIO 2)

DEFINE TRANSACTION(SRT3) GROUP(IAS) PROGRAM(SRVTEST3)

DESCRIPTION(IAS SAMPLE SERVICE - SCENARIO 3)

DEFINE TRANSACTION(SRTC) GROUP(IAS) PROGRAM(SRVTESTC)

DESCRIPTION(IAS SAMPLE CLIENT - ALL SCENARIOS)

***

*** DEFINITIONS FOR PROGRAMS

***

DEFINE PROGRAM(SRVRQRPC) GROUP(IAS) LANGUAGE(ASSEMBLER)

DEFINE PROGRAM(SRVRSRPC) GROUP(IAS) LANGUAGE(ASSEMBLER)

DEFINE PROGRAM(SRVRCVM) GROUP(IAS) LANGUAGE(ASSEMBLER)

DEFINE PROGRAM(SRVABND) GROUP(IAS) LANGUAGE(ASSEMBLER)

DEFINE PROGRAM(SRVSCURE) GROUP(IAS) LANGUAGE(ASSEMBLER)

DEFINE PROGRAM(SRVSTUP) GROUP(IAS) LANGUAGE(ASSEMBLER)

DEFINE PROGRAM(SRVMAINT) GROUP(IAS) LANGUAGE(ASSEMBLER)

DEFINE PROGRAM(SRVMNTSS) GROUP(IAS) LANGUAGE(ASSEMBLER)

DEFINE PROGRAM(SRVUMLOG) GROUP(IAS) LANGUAGE(ASSEMBLER)

DEFINE PROGRAM(SRVGTBLS) GROUP(IAS) LANGUAGE(ASSEMBLER)

DEFINE PROGRAM(SRVUTBLM) GROUP(IAS) LANGUAGE(ASSEMBLER)

DEFINE PROGRAM(SRVGTBLE) GROUP(IAS) LANGUAGE(ASSEMBLER)

DEFINE PROGRAM(SRVRLAA) GROUP(IAS) LANGUAGE(ASSEMBLER)

DEFINE PROGRAM(SRVLINK) GROUP(IAS) LANGUAGE(ASSEMBLER)

DEFINE PROGRAM(SRVXLINK) GROUP(IAS) LANGUAGE(ASSEMBLER)

DESCRIPTION(IAS X-LINK UNIT)

DEFINE PROGRAM(SRVUMAP) GROUP(IAS) LANGUAGE(ASSEMBLER)

DEFINE PROGRAM(SRVUMP1) GROUP(IAS) LANGUAGE(ASSEMBLER)

DEFINE PROGRAM(SRVTEST1) GROUP(IAS) LANGUAGE(ASSEMBLER)

DESCRIPTION(IAS SAMPLE SERVICE - SCENARIO 1)

DEFINE PROGRAM(SRVTEST2) GROUP(IAS) LANGUAGE(ASSEMBLER)

DESCRIPTION(IAS SAMPLE SERVICE - SCENARIO 2)

DEFINE PROGRAM(SRVTEST3) GROUP(IAS) LANGUAGE(ASSEMBLER)

DESCRIPTION(IAS SAMPLE SERVICE - SCENARIO 3)

DEFINE PROGRAM(SRVTESTC) GROUP(IAS) LANGUAGE(ASSEMBLER)

DESCRIPTION(IAS SAMPLE CLIENT - ALL SCENARIOS)

***

*** DEFINITIONS FOR APPC CONNECTIONS AND SESSIONS

***

*** NOTE THAT CICS SUPPORTS AUTOINSTALL FOR LU6.2. IF YOUR

*** SYSTEM IS CONFIGURED TO DO SO, THESE DEFINITIONS MAY

*** NOT BE REQUIRED.

***

*** THIS IS A SAMPLE DEFINITION, DEFINING THE CONNECTION

*** AND SESSIONS TO APPC/MVS. IT ASSUMES THE SAME NAMES

*** AS IN THE SUPPLIED (ABOVE) SAMPLES. IF ANY WERE

*** MODIFIED, THESE MUST BE REFLECTED BELOW.

***

*** THE CONNECTION AND SESSIONS FOR APPC/MVS ARE USED IN CASE IAS

*** IS CONNECTED OVER TCP/IP TO RELAY, AND RELAY USES APPC/MVS

*** TO CONNECT TO CICS.

*** IF YOU ARE CONNECTING IAS ON NT USING DIRECT APPC CONNECTION

*** TO CICS REFER TO SAMPLE MEMBER CICSDEF3 IN THIS LIBRARY.

***

DEFINE CONNECTION(MVS1) GROUP(IAS)

NETNAME(MVSLU01) ACCESSMETHOD(VTAM) PROTOCOL(APPC)

SINGLESESS(NO) INSERVICE(YES) AUTOCONNECT(YES)

DESCRIPTION(SAMPLE CONNECTION, TO APPC/MVS)

DEFINE SESSION(MVS1SESS) GROUP(IAS)

CONNECTION(MVS1) MODENAME(APPCMODE) PROTOCOL(APPC)

MAXIMUM(10,5) AUTOCONNECT(YES)

DESCRIPTION(SAMPLE CONNECTION, TO APPC/MVS)

***

*** ADD THE IAS GROUP, WITH THE DEFINITIONS, TO THE CICS STARTUP LIST

*** OR INSTALL GROUP(IAS) TO PUT DEFINITIONS IN EFFECT

***

ADD GROUP(IAS) LIST(CICSLIST)

/*

//


Note

The session definition contains the MODENAME which is also present in mode tables associated with APPC/MVS and the CICS definitions in VTAM. The same mode name should be used in all three instances.


Install a Resource Group for the APPC Connection">
Note

The session definition contains the MODENAME which is also present in mode tables associated with APPC/MVS and the CICS definitions in VTAM. The same mode name should be used in all three instances.


Install a Resource Group for the APPC Connection

Code 3-6 can be used for a direct APPC connection from Windows NT, and demonstrates definitions for CONNECTION and SESSIONS parameters in CICS.

Code Example 3-6    CICSDEF3 
//CICSDEF3 JOB

//*

//CSDUP EXEC PGM=DFHCSDUP

//STEPLIB DD DSN=CICS.CICS.SDFHAUTH,DISP=SHR

//DFHCSD DD DSN=CICS.DFHCSD,DISP=SHR

//SYSPRINT DD SYSOUT=*

//SYSIN DD *

***

*** DEFINITIONS FOR IAS/NT USING DIRECT APPC.

*** THESE DEFINITIONS MUST BE INSTALLED IN CICS RESOURCE DEFINITION

*** IN ADDITION TO, OR INSTEAD OF, CONNECTION AND SESSIONS FOR APPC/MVS

*** ENLISTED IN CICSDEF SAMPLE.

***

DEFINE CONNECTION(SKNT) GROUP(IASDAPPC)

NETNAME(SHMUELNT) ACCESSMETHOD(VTAM) PROTOCOL(APPC)

SINGLESESS(NO) INSERVICE(YES) AUTOCONNECT(YES)

DESCRIPTION(SAMPLE DIRECT/APPC CONNECTION TO IAS/NT)

DEFINE SESSIONS(SKNTAPPC) GROUP(IASDAPPC)

CONNECTION(SKNT) MODENAME(APPCMODE) PROTOCOL(APPC)

MAXIMUM(10,5) AUTOCONNECT(YES)

DESCRIPTION(SAMPLE DIRECT CONNECTION TO IAS/NT)

***

*** DEFINITIONS ARE PUT IN EFFECT BY ADDING TO CICS STARTUP LIST AS

*** DEMONSTRATED HERE, OR BY INSTALLING GROUP CONTAINING THESE DEFS

***

ADD GROUP(IASDAPPC) LIST(CICSLIST)

/*

//


Add the Product Load Library to CICS DFHRPL List

Add the product load library to the CICS DFHRPL list in the CICS startup JCL.

Code Example 3-7    Sample VTAM Major Node for CICS
Startup/JCL   //DFHRPL       DD   DSN=
         DD   DSN='

......

......

DD   DSN='IAS4CICS.V6R0M0.CICS.LOAD'.DISP=SHR*


Define the Necessary Entries in the Application Table VSAM File

Use the supplied CICS transaction SRVU created in Step 3 to make the necessary application table definitions in the CICS application table file as shown in Figure 3-7. Use the PF5 command to add the entries to the file.

Figure 3-7    Application Table Maintenance



Installing and Configuring the Relay

Installing and configuring the Relay is only necessary when you use TCP/IP to connect to the mainframe.

When using the Relay, configure the environment for the following:

  • VTAM

  • TCP/IP

  • APPC/MVS

  • Security

Proceed in the following order:


Create an Application Table Dataset for the Relay Component

You must create an application dataset for the Relay component.


To Create an Application Table Dataset for the Relay Component

  1. Run the DEFFILES REXX located in the Relay installation library.

    The REXX prompts you for the entries. See Step 2 through Step 5, below.

  2. Enter the application table name without quotes.

    Specify a name for the relay's application table. For example:

    IAS.APPLTAB.RELAY

  3. Enter the VOLSER (Volume Serial Name).

    Specify the name of the DASD on which this file should be created.

  4. Enter unit type, or press Enter for 3390.

    Specify the unit type.

  5. Enter MVS/APPC logmode.

    Enter the logmode that should be used to access CICS. The supplied name is APPCMODE.

    The message "You have successfully created an application table" appears when the table is created.


Configure APPC/MVS

This procedure is required only if APPC/MVS is not already configured on your system. If it is configured on the system, it is recommended that you read through these instructions and compare them to the existing configuration on your system. You can use wither one of the samples provide with the CICS Enterprise Connector to configure APPC/MVS.


To Configure APPC/MVS

  1. If APPC/MVS is not installed on your system, you can adapt and use the sample code given in Code Example 3-8 or the sample definition for APPC/MVS base LU given in Code Example 3-9.

    The member APPC/MVS in the Relay Installation library contains VTAM definitions for the base APPC/MVS LU.

    Code Example 3-8    Library Member APPCMVS

    *

    * SAMPLE MAJOR NODE FOR APPC/MVS

    *

    APPCMVS VBUILD TYPE=APPL

    MVSLU01 APPL ACBNAME=MVSLU01, *

    APPC=YES, *

    AUTOSES=10, *

    DDRAINL=NALLOW, *

    DMINWNL=20, *

    DMINWNR=20, *

    DRESPL=NALLOW, *

    DSESLIM=40, *

    EAS=509, *

    MODETAB=MTAPPC, *

    SECACPT=CONV, *

    SRBEXIT=YES, *

    VERIFY=NONE, *

    VPACING=2


    Note

    The iPlanet Application Server Enterprise Connector for CICS does not require ASCH.


    Code Example 3-9    APPCPM00 Member

    /* LIB: SYS1.PARMLIB(APPCPM00) */

    LUADD ACBNAME(MVSLU01) BASE NOSCHED

  2. Activate the APPC/MVS major node by using the following command:

    V NET,ID=APPCMVS,ACT

  3. Using the MVS commands, start APPC/MVS by using the following command:

    S APPC,SUB=MSTR,APPC=00


Create a TCP/IP Listener Started Task

The Listener listens to a TCP/IP port. The following sections describe both the prerequisites and the procedure for configuring and operating the Listener.

Note

Because the Listener and the Relay reside in the same address space, when referring to the Listener and Relay, the reference is to the same component.



To Create a TCP/IP Listener Started Task

The TCP/IP Listener can be executed as an MVS Started Task, or as a batch job. It is recommended to run it as an MVS Started Task.


Prerequisites

The following components must be installed before you can use the Listener:

  • The MVS Operating System version 4.3 or later, or any version of OS390

  • IBM TCP/IP version 3.1 or later


To Create and Configure the Listener

  1. Copy the member LISTEN, (the sample procedure in Relay installation library), into a system procedure library, for example,

    SYS1.PROCLIB.

  2. Ensure that the STEPLIB points to the load library, and that the SRVAPLF DD card points to the application table.

  3. Verify the SYSOUT class on the CPEOUT, CPEOUTRS, CPEOUTRO DD cards.

    The load library must be APF authorized.

  4. Place an entry for the load library in SYS1.PARMLIB member IEAAPFxx or PROGxx, depending on your site's standards.

  5. Update the following PROC statement parameters:

    Table 3-8    PROC Statement Parameters

    TCPIP  

    Name of the TCP/IP address space. TCPIP is the default.  

    PORT  

    An available port number.  

    MAXTASK  

    Maximum number of concurrent tasks. 20 tasks is the default.  

    PROGRAM  

    Name of the program to activate for incoming requests, must be `SRVRLNS'.  

    Refer to Code Example 3-10.

    Code Example 3-10    Listen PROC  
    //LISTEN PROC TCPIP=TCPIP,PORT=47000,MAXTASK=20,PROGRAM=SRVRLNS

    //*********************************************************************

    //* THIS PROCEDURE CAN BE USED FOR A TCP/IP LISTNER.

    //* MOST COMMONLY, IT IS USED AS A RELAY BETWEEN TCP/IP AND APPC.

    //* IT CAN BE RUN AS A STARTED TASK OR A JOB.

    //*

    //* BEFORE USING IT PLEASE PERFORM THE FOLLOWING CHANGES:

    //* 1. CHECK THE NAME OF THE STEPLIB. NOTE THAT THIS LIBRARY HAS TO BE

    //* AUTHORIZED.

    //* 2. CHECK THE NAME OF THE APPLICATION TABLE ON SRVAPLF

    //* 3. CHECK THE SYSOUT CLASS ON CPEOUT AND SYSUDUMP.

    //* 4. UPDATE THE PARAMETERS ON THE PROC STATEMENT :

    //* TCPIP = THE NAME OF THE TCP/IP ADDRESS SPACE (DEFAULTS TO TCPIP)

    //* PORT = AN AVAILABLE PORT NUMBER (DEFAULS TO 47000)

    //* MAXTASK = THE MAXIMUM NUMBER OF CONCURRENT TASKS (DEFAULTS TO 20)

    //* PROGRAM = THE NAME OF THE PROGRAM TO ACTIVATE ON INCOMING REQUEST

    //* - LEAVE BLANK TO PICK UP THE NAME IN THE APPLICATION TABLE

    //* - CODE 'SRVRLTA' FOR A RELAY

    //LISTEN EXEC PGM=SRVLISPR,PARM='&TCPIP,&PORT,&MAXTASK,&PROGRAM',

    // REGION=0M

    //STEPLIB DD DSN=IAS4CICS.V6R0M0.RELAY.LOAD,DISP=SHR

    //CPEOUT DD SYSOUT=X,HOLD=YES

    //CPEOUTRQ DD SYSOUT=X,HOLD=YES

    //CPEOUTRS DD SYSOUT=X,HOLD=YES

    //CPESNAP DD SYSOUT=X,HOLD=YES

    //SYSUDUMP DD SYSOUT=X,HOLD=YES

    //SRVAPLF DD DSN=IAS.APPLTAB.RELAY,DISP=SHR

    //SRVTCPI DD DUMMY

    // PEND


Verify the Security Server Definition

Verify that the user ID assigned to the Listener has an OMVS segment.


Start the Listener

The following description of how to start the Listener assumes that LISTEN is the name of the started task.

Use the following procedures to start, stop, and restart the Listener, and to determine and free the connection port.


To Start the Listener

  • Issue the MVS command: S LISTEN
    Note

    LISTEN can be included in the TCP/IP automatic startup list (AUTOLOG).



To Stop the Listener

  • Issue the MVS command: P LISTEN


To Stop the Listener After a Fixed Amount of Time

  • Issue the MVS command: F LISTEN,SHUTDOWN nnn

    where nnn is the number of seconds (default is 10 seconds) and allows open conversations to end.


Stop the Listener

In early releases of TCP/IP, it may occur that even though the Listener was stopped, its port is not freed. In such cases, determine the connection identification and free the port.


To Determine the Connection Identification

  • Issue the following command:

    NETSTAT ALLCONN (PORT xxxxx)

    where xxxxx is the port assigned to the Listener (Relay). Note the connection identification.


To Free the Port

  • Issue the following command which requires the issuing user to have the proper security authorization:

    NETSTAT DROP yyyyy

    where yyyyy is the connection identification obtained in the preceding NETSTAT command.



Installing the PhoneBook Application

The PhoneBook Sample installation is intended to verify that the iPlanet Application Server Enterprise Connector for CICS has been properly installed.
Note

The TELCO sample application including its installation is described in the appendix. The TELCO sample requires DB2 for OS/390 and is not part of installation verification.



To Install the Sample PhoneBook Application on CICS

  • Submit the PBINIT member located in the CICS installation library.

    Refer to Code Example 3-11.

    Code Example 3-11    PhoneBook Sample in the CICS Environment 

    //PBINIT JOB MSGCLASS=K

    //*=================================================================*

    //*

    //* THIS JOB CREATES THE VSAM FILE FOR THE IAS PHONEBOOK

    //* DEMO. IT CREATES, INITIALIZES THE VSAM PHONEBOOK DATASET, AND

    //* DEFINES IT TO CICS USING THE BATCH CSD UPDATE UTILITY.

    //*

    //*=================================================================*

    //* 1. DEFINE VSAM FILE

    //*

    //* CHECK THE NAME OF THE LIBRARY IN THE SYSEXEC CARD, IT SHOULD BE

    //* THIS LIBRARY

    //* CHECK THE VSAM DATASET NAME(S) IN THE SYSTSIN LINE 1 AND 3

    //* CHANGE THE VOLSER (VVVVVV) IN SYSTSIN LINE 4

    //*=================================================================*

    //STEP3 EXEC PGM=IKJEFT01,DYNAMNBR=40

    //SYSTSPRT DD SYSOUT=*

    //SYSUT1 DD DSN=&SYSUT1,UNIT=SYSDA,SPACE=(1700,(400,50))

    //SYSUT2 DD DSN=&SYSUT2,UNIT=SYSDA,SPACE=(1700,(400,50))

    //SYSUT3 DD DSN=&SYSUT3,UNIT=SYSDA,SPACE=(1700,(400,50))

    //SYSEXEC DD DSN=IAS4CICS.V6R0M0.CICS.INST,DISP=SHR

    //INPUT DD *

    ARIE NOA 262 12324

    FLINT ORIT 260 4377

    GALIL MOTI 1234 12345

    GALMIDI MOTI 123 1234

    GOLD KEREN 258 52960

    GRYNBAUM TAL 251 52960

    MICHEAL SHATZ 234 43456

    REICH SHANY 123 1234

    SHANI RAKEFET 252 1234

    SHIMON RICKY 259 43788

    SHORKEND MIKE 123 1234

    /*

    //SYSTSIN DD *

    DEL 'IAS.PHONBOOK.CICS'

    PBLOAD

    IAS.PHONBOOK.CICS

    VVVVVV

    3390

    /*

    //*=================================================================*

    //* 2. UPDATE CICS DEFINITIONS WITH PHONEBOOK APPLICATION DATA

    //*

    //* CHECK THE DSN= PARAMETERS FOR THE STEPLIB AND DFHCSD DD CARDS

    //* CHANGE 'CICSLIST' TO THE CICS STARTUP LIST NAME

    //* SEE NOTES FOR EACH SECTION BELOW (FILES, PROGRAMS, ETC.)

    //*

    //*=================================================================*

    //CSDUP EXEC PGM=DFHCSDUP

    //STEPLIB DD DSN=CICS.CICS.SDFHLOAD,DISP=SHR

    //DFHCSD DD DSN=CICS.DFHCSD,DISP=SHR

    //SYSPRINT DD SYSOUT=*

    //SYSIN DD *

    ***

    *** DEFINITIONS FOR PHONEBOOK FILES

    ***

    DEFINE FILE(PBVSAM) GROUP(IASPHB)

    DSNAME(IAS.PHONBOOK.CICS) DISPOSITION(SHARE)

    ADD(YES) BROWSE(YES) DELETE(YES) READ(YES) UPDATE(YES)

    RECORDFORMAT(F) STATUS(ENABLED) OPENTIME(FIRSTREF)

    JOURNAL(01) STRINGS(10) DATABUFFERS(11)

    DESCRIPTION(IAS PHONEBOOK APPLICATION TABLE)

    ***

    *** DEFINITIONS FOR TRANSACTIONS

    ***

    *** THE TRANSID VALUES MAY BE CHANGED.

    ***

    DEFINE TRANSACTION(PHBK) GROUP(IASPHB) PROGRAM(PHONBOOK)

    DESCRIPTION(IAS PHONEBOOK APPLICATION)

    ***

    *** DEFINITIONS FOR PROGRAMS

    ***

    DEFINE PROGRAM(PHONBOOK) GROUP(IASPHB) LANGUAGE(ASSEMBLER)

    DEFINE PROGRAM(PHONBOOX) GROUP(IASPHB) LANGUAGE(ASSEMBLER)

    ***

    *** ADD THE IAS GROUP, WITH THE DEFINITIONS, TO THE STARTUP LIST

    *** IF NEEDED (NOT DONE BEFORE

    ***

    ADD GROUP(IASPHB) LIST(CICSLIST)

    /*


To Operate the Sample PhoneBook Application on NT

  1. Select Start>Programs>iPlanet Application Server 6.0.

  2. Select CICS Connector 6.0 - Sample Applications.


To Operate the PhoneBook Sample Application on Solaris

  • Run Netscape or Microsoft browser with the following URL:

    http://<webserver instance name>/cicsSamples


Previous     Contents     Index     DocHome     Next     
Copyright © 2000 Sun Microsystems, Inc. Some preexisting portions Copyright © 2000 Netscape Communications Corp. All rights reserved.

Last Updated November 13, 2000