Chapter 2   Installing the Mainframe Component


This chapter is divided into the following four subject categories:

• Overview

• Installing and Configuring CICS

• Installing and Configuring the Relay

• Installing the PhoneBook Application

Overview

---

The installation steps in this chapter present two alternative scenarios of connecting iPlanet Application Server to CICS backend. The two sceneries are:

• Scenario 1 - iPlanet Application Server on NT or Solaris is connected via TCP/IP to a Relay component on OS/390 (MVS). The Relay communicates over the APPC with CICS.

• Scenario 2 - iPlanet Application Server on NT is connected via direct APPC connection to CICS on OS/390 (MVS)

Figure 2-1    Scenarios for connection iPlanet Application Server Enterprise Server to CICS backend.

When you have completed the installation of either the TCP/IP or APPC installation, the phonebook sample application is available for end-to-end installation verification of iPlanet Application Server Enterprise Connector for CICS.

Installing and Configuring CICS

---

The CICS components are supplied as downloaded PC files on the iPlanet Application Server Enterprise Connector for CICS installation media. Regardless of the media, you must upload the required partitioned datasets (PDS) to MVS.

If you have TCP/IP configured on your mainframe, you can use the supplied installation program from within the installer to tailor and send up the libraries. If TCP/IP is not installed then follow the instructions in the section, "Transferring in the Absence of TCP/IP" on page 54.

Uploading the Libraries

1. On NT: Run the mfinst.bat installation utility from:

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

   OR

   On Solaris: Run the mfinst.sh installation utility from:

   <instdir>/nas/APPS/adapters/cics/backend

   The following window will appear:
   
   

Figure 2-2    Empty Installer Mainframe Dialog Box

2. Type in your User and Host Information that includes:
   • Host Name

   • Userid - This will be the prefix for temporary files on the mainframe, and also JOB name prefix. The userid needs to be a TSO userid with sufficient authority to create iAS prefix datasets.

   • Password

   • Permanent Prefix - this is for installation libraries.

3. Press the tab key; the following fields will be automatically displayed:
   • CICS Installation library

   • CICS Load library

   • Relay Installation library

   • Relay Load library

   • CICS DBRM library - this is needed for TELCO sample application described in the iPlanet Application Server Enterprise Connector for CICS Developer's Guide.

4. You must type in the unit name and the volume name in the Unit and Volume text boxes of the following Installer dialog box.
   
   

Figure 2-3    Completed Installer on Mainframe Dialog Box

5. Press the OK button to continue.

6. Go to configure CICS.

Transferring in the Absence of TCP/IP

The following procedure applies to users that do not utilize TCP/IP in their connection to the mainframe.

If you have TCP/IP installed go to, "Configuring CICS" on page 55.

Installing the CICS Components on 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: LOAD.XMT, INSTALL.XMT, RELINST.XMT, and RELLOAD.XMT. These files are found in <instdir>\IAS\APPS\adapters\cics\backend on NT.

   Use the MVS/TSO binary transfer type and fixed-file option.

3. Issue the TSO command: RECEIVE INDATASET(IAS.CICS.LOAD.XMIT).At the prompt, enter DATASET(IAS4CICS.V6R0M0.CICS.LOAD), where IAS4CICS.V6R0M0.CICS.LOAD is the name of the product load library.

4. Issue the TSO command: RECEIVE INDATASET(IAS.CICS.INSTALL.XMIT). At the prompt, enter DATASET(IAS4CICS.V6R0M0.CICS.INST), where IAS4CICS.V6R0M0.CICS.INST is the name of the installation library.

5. Issue the TSO command: RECEIVE INDATASET(IAS.RELAY.INSTALL.XMIT). At the prompt, enter DATASET(IAS4CICS.V6R0M0.RELAY.INST), where IAS4CICS.V6R0M0.RELAY.INST is the name of the installation library for the RELAY component.

6. Issue the TSO command: RECEIVE INDATASET(IAS.RELAY.LOAD.XMIT); at the prompt, enter DATASET(IAS4CICS.V6R0M0.RELAY.LOAD) where IAS4CICS.V6R0M0.RELAY.LOAD is the name of the load library for the RELAY component.

Receiving Files for TELCO Sample

1. Allocate one data set on MVS with 1recl=80, blksize=3120, recfm=fb, for example IAS.CICS.DBRM.XMIT.

2. Use the 3270 emulation program to transfer the file DBRM.XMT to the respective MVS data set.

   Use the MVS/TSO binary-transfer-type and fixed-file option.

3. Issue the TSO command: RECEIVE INDATASET(IAS.CICS.DBRM.XMIT). At the prompt, enter DATASET(IAS.V6R0M0.DBRM.LIB), where IAS.V6R0M0.DBRM.LIB is the name of the Sample-2 (TELCO) DBRM library.

Configuring CICS

Configuring the CICS Components

1. Create the VTAM mode table MTAPPC.

2. Ensure that the needed CICS VTAM definition parameters are specified.

3. Define a remote PU for each NT connected directly to CICS (for each application server).

4. Create the VSAM datasets using the supplied DEFFILES member.

5. Update the CICS resource definition using the supplied CICSDEF.

6. Install the new resource group.

7. Add the product load library to CICS DFHRPL list.

8. Define the necessary entries in the application table VSAM file created in step 3.

Showing Details and Samples for the Installation

1. Use the following MTAPPC to define VTAM mode table for APPC.

   The MTAPPC is located in the CICS installation library.

2. Refer to the following Code Example 2-1.

   This sample demonstrates definitions of APPC mode entry in the MODE TABLE associated with CICS in CICS VTAM definition. Code Example 2-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)

   
   

   ---

   Note	Make sure that the mode table associated with CICS includes mode entry APPCMODE.

   ---

   
   

3. Ensure that the needed CICS VTAM definition parameters are specified.
   Refer to Code Example 2-2. Code Example 2-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.

---

4. Define a remote PU for each NT connected directly to CICS.

If your application server is connected directly to CICS (using APPC connections), define the remote PU (the application server machine) to VTAM and CICS (see step 5 for definitions in CICS).

Refer to the following illustration. Code Example 2-3 Sample PU and LU6.2 Definition for NT

---

*/*

SWSHMUEL VBUILD TYPE=SWNET

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

CPNAME=SHMUELNT

SHMUELNT LU LOCADDR=0

5. Create the VSAM datasets using DEFFILES member in CICS installation library, as shown in the following Code Example 2-4. Code Example 2-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))

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

   Refer to the following Code Example 2-5.

   If you are using direct APPC connection from NT, refer to Code Example 2-6 as definition for CICS connection and sessions. The following sample job defines the iPlanet Application Server Connector components to CICS. Code Example 2-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)

   /*

   //

This code, to be used for direct APPC connection for NT, demonstrates definitions for CONNECTION and SESSIONS in CICS. Code Example 2-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)

/*

//

7. Add the product load library to CICS DFHRPL list.

   //DFHRPL       DD   DSN='...........................

          DD   DSN='...........................

         ......

         ......

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

8. Define the necessary entries in the application table VSAM file (created in step 3).

   Use the supplied CICS transaction SRVU to make the necessary application table definitions in the CICS application table file as shown in (use PF5 to add the entries to the file).

Figure 2-4    Application Table Maintenance

Installing and Configuring the Relay

---

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

If you are using the Relay, configure the environment for it — VTAM, TCP/IP, and APPC/MVS.

Proceed in the following order:

1. Creating an application table dataset for the Relay component.

2. Configuring APPC/MVS (optional).

3. Creating a TCP/IP Listener started task.

Creating 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 following entries described in step 2 through step 6, below.

2. Enter the application table name without quotes.

   Specify a name for the relay's application table: IAS.APPLTAB.RELAY

3. Enter volser.

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

4. Enter unit type or hit 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 if the table was created.

Configuring APPC/MVS

This step is needed only if APPC/MVS is not already configured on your system. If it is, it is recommended that you read through these instructions and compare them to the existing configuration on your system.

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

   Copy these definitions into SYS1.VTAMLST. Refer to Code Example 2-7. Code Example 2-7 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

2. Copy APPCPM00 from Relay Installation library into SYS1.PARMLIB.

   
   

   ---

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

   ---

   
   

   The member is listed as shown in Code Example 2-8. Code Example 2-8 APPCPM00 member
   

   ---

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

   LUADD ACBNAME(MVSLU01) BASE NOSCHED

3. Activate the APPC/MVS major node.

   Use command F NET,ID=APPCMVS,ACT

4. Using the MVS commands, start APPC/MVS:

   S APPC,SUB=MSTR,APPC=00

Creating a TCP/IP Listener Started Task

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

Configuring Listener

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

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

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.

Customizing the Listener

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

2. Check that the STEPLIB points to the load library. Check that the SRVAPLF DD card points to the application table.

3. Verify the SYSOUT class on the CPEOUT DD.

4. The load library must be APF authorized. Place an entry for it in SYS1.PARMLIB member IEAAPFxx or PROGxx, depending on your site's standards.

5. Update the parameters on the PROC statement.
   

   TCPIP	The name of the TCP/IP address space. Default is TCPIP).
   PORT	An available port number.
   MAXTASK	The maximum number of concurrent tasks. Default is 20.
   PROGRAM	The name of the program to activate for incoming requests must be `SRVRLNS'.

   Refer to the following code example: Code Example 2-9 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

Operating the Listener

Assuming the name of the started task is LISTEN, use the following procedures to start and stop the Listener.

Starting the Listener

Issue the MVS command: S LISTEN.

Stopping the Listener

Issue the MVS command: P LISTEN.

Stopping the Listener After a Fixed Amount of Time

Issue the MVS F LISTEN,SHUTDOWN nnn command, where nnn is the number of seconds (default is 10 seconds) and allows open conversation to end.

Resetting the Listener

On early releases of TCP/IP it may happen that even though Listener was stopped, its port is not freed. In such cases, the following procedure is suggested using TCP/IP command from TSO prompt.

Determining the Connection Identification

Issue the following command where xxxxx is the port assigned to the Listener (Relay):

NETSTAT ALLCONN (PORT xxxxx

Note the connection identification.

Freeing 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 steps ar described to verify the iPlanet Application Server Enterprise Connector for CICS installation.

---

Note	The TELCO sample application including its installation is described in the Developer's Handbook. The TELCO sample requires DB2 for OS/390 and is not part of installation verification.

---

Installing the Sample PhoneBook Application on the CICS

Submit the PBINIT located in the CICS installation library.
Refer to Code Example 2-10. . Code Example 2-10 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)

DEFINE TRANSACTION(PHBX) GROUP(IASPHB) PROGRAM(PHONBOOX)

DESCRIPTION(IAS PHONEBOOK APPLICATION - X-LINK)

***

*** 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)

/*

Operating the Sample PhoneBook Application

Operating the PhoneBook Sample Application on NT

1. Click Start

2. Click Programs.

3. Click iPlanet Application Server.

4. Click iAS for CICS Sample Applications

Operating the PhoneBook Sample Application on Solaris

1. Run Netscape or Microsoft browser with the following URL

   http//<host.name of Solaris>/cicsSamples/index.html

   Where <host.name of Solaris> is the IP host name of the Solaris server where WebServer and iPlanet Application Server are installed.