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 either of these ways:
via TCP/IP: either using IBM or CA (TCPaccess)
- The TCP/IP must be one of the versions currently supported by either IBM or CA.
Note TCPaccess is the current name of Interlink.
- The iPlanet Application Server can be installed on Windows NT or Solaris and 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
- The iPlanet Application Server can be installed on Windows NT and 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 "Installing the PhoneBook Sample Application".
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 FTP or a 3270 emulator file-transfer utility. If TCP/IP is not installed, follow the instructions in "Uploading MVS Library Files Using 3270 File Transfer".
Uploading MVS Library Files via TCP/IP
If you have TCP/IP configured on your mainframe you can use the installation program mfinst that is described in the following sections.Make sure that the FTP on the mainframe allocate data sets structured as follows: lrecl=80 blksize=3120 recfm=fb.
If the allocated data sets are not structured as described above allocate four (or five) data sets on MVS with 1recl=80, blksize=3120, recfm=fb.
- For example:
IAS.CICS.LOAD.XMIT
IAS.CICS.DBRM.XMIT (Only needed for running the TELCO sample described in Appendix A "Operating the TELCO Sample")
To Upload the Library Files on Windows NT
Run the mfinst.bat installation utility from the following directory:
- \iPlanet\iAS6\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, see Table 3-1
CICS Installation Dataset, see Table 3-2
CICS Load Dataset, see Table 3-3
Relay Installation Dataset, see Table 3-4
User and Host Information
Table 3-1 lists names and IDs used to connect to the CICS system.
Note All fields except Unit and Volume Name will be automatically filled in after you enter the Permanent Prefix and press Return.
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.
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
The temporary name assigned to the CICS Load dataset during upload.
.
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
.
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 Dataset
Variable
Definition
The temporary name assigned to the Relay Load dataset during upload
.
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
The temporary name assigned to the CICS DBRM dataset during upload.
.
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
.
Figure 3-4 shows an example of a completed installer dialog box.
Figure 3-4    Completed Installer Dialog Box. ![]()
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.
Select 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.
- 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) ![]()
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.
Allocate four data sets on MVS with 1recl=80, blksize=3120, recfm=fb.
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.
Issue the following TSO command:
At the prompt, enter the following:
Issue the following TSO command:
- DATASET(IAS4CICS.V6R0M0.CICS.LOAD)
- where IAS4CICS.V6R0M0.CICS.LOAD is the name of the product load library.
At the prompt, enter the following:
Issue the following TSO command:
- DATASET(IAS4CICS.V6R0M0.CICS.INST)
- where IAS4CICS.V6R0M0.CICS.INST is the name of the installation library.
At the prompt, enter the following:
Issue the following TSO command:
- DATASET(IAS4CICS.V6R0M0.RELAY.INST)
- where IAS4CICS.V6R0M0.RELAY.INST is the name of the installation library for the RELAY component.
At the prompt, enter the following:
Configuring CICS on the Mainframe
You need to configure the components to install the connection to the mainframe computer.
To Configure the CICS Components
Ensure APPC Logmode Entry is Present.
Verify CICS Applid Definitions.
Define a Remote PU for each NT Server Platform Connected Directly to CICS via APPC
Note Direct APPC only.
Changing Installation Parameters' Default Names (Optional)
Update the CICS Resource Definitions by Running the Supplied CICSDEF.
Note If you do not have special logmode needs you can use the IBM supplied logmode APPCSNA and go directly to "Verify CICS Applid Definitions".
"> Ensure APPC Logmode Entry is Present
Note If you do not have special logmode needs you can use the IBM supplied logmode APPCSNA and go directly to "Verify CICS Applid Definitions".
Code Example 3-1 displays a MODE entry in the MODE TABLE. The same Logmode must be associated with the CICS VTAM definition.If you perform the CICS command: cemt I mode(appcmode) you should get a positive result. If NOT FOUND is displayed, see "Update the CICS Resource Definitions by Running the Supplied CICSDEF" for the logmode that must be added to the CICS.
Verify CICS Applid Definitions
Code Example 3-2 is a sample VTAM definition for CICS. In most cases, CICS is already defined and running.
Note Do not add APPC=YES to the CICS VTAM definition.
If you choose to use logmode APPCSNA, MODETAB is not required.
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
Changing Installation Parameters' Default Names (Optional)
The default names of the installation parameter may be changed but it is not recommended.
To Change the CICS Installation Parameters
Run the INST REXX located in the CICS installation library.
Type in the library name, without quotes, and press enter. Figure 3-7 is displayed.
Figure 3-7    Installation Parameters ![]()
If you change "CICS CONNECTOR PREFIX" from SRV then you must also change "IAS LOAD LIBRARY" to your CICS load library. It must be the same as the "CICS LOAD DATASET PERMANENT NAME" shown in Figure 3-4.
You will get the following job.
Update the CICS Resource Definitions by Running the Supplied CICSDEF
Update the CICS resource definitions by running the supplied CICSDEF from the CICS 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.
Install a Resource Group for the APPC Connection">
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.
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*
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:
Proceed in the following order:
Create an Application Table Dataset for the Relay Component
Create a TCP/IP Listener Started Task
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
Run the DEFFILES REXX located in the Relay installation library.
Enter the application table name without quotes.
Enter the VOLSER (Volume Serial Name).
Enter unit type, or press Enter for 3390.
Enter MVS/APPC logmode.
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 either one of the samples provide with the iAS Enterprise Connector for CICS to configure APPC/MVS.
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.
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
Activate the APPC/MVS major node by using the following command:
Using the MVS commands, start APPC/MVS by using the following command:
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.
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.
To Create and Configure the Listener
Copy the member LISTEN, (the sample procedure in Relay installation library), into a system procedure library, for example,
Update the following PROC statement parameters:
Table 3-8    PROC Statement Parameters
The same (Relay) port specified in Table 2-1.
Maximum number of concurrent tasks. 20 tasks is the default.
Name of the program to activate for incoming requests must be `SRVRLNS'.
Ensure that the STEPLIB points to the load library.
Ensure that the SRVAPLF DD card points to the application table.
- The load library must be APF authorized.
- Place an entry for the load library in your paramfile library member IEAAPFxx or PROGxx, depending on your site's standards.
Verify the SYSOUT class on the CPEOUT, CPEOUTRS, CPEOUTRO DD cards.
- Refer to Code Example 3-10.
Verify the Security Server Definition
Verify that the user ID assigned to the Listener has an OMVS segment.Example: To add the listener, that is assigned to user-ID LISTEN, the OMVS segment should be added by issuing the following RACF command:
ADDUSER LISTEN OMVS(UID(1234...))
Operate 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.
Issue the MVS command: S LISTEN
Note LISTEN can be included in the TCP/IP automatic startup list (AUTOLOG).
To Stop the Listener After a Fixed Amount of Time
In early releases of TCP/IP, even though the Listener was stopped, its port may not be freed. In such cases, determine the connection identification and free the port.
To Determine the Connection Identification
Issue the following command which requires the issuing user to have the proper security authorization:
Installing the PhoneBook Sample 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
Edit the PBINIT member located in the CICS installation library according to the instructions in the member.
- Refer to Code Example 3-11.
Previous Contents Index DocHome Next
Copyright © 2001 Sun Microsystems, Inc. Some preexisting portions Copyright © 2001 Netscape Communications Corp. All rights reserved.
Last Updated September 13, 2001