This document describes how to install the CICS connection for a Natural Web I/O Interface server (product code NWO) running under z/OS in batch mode.

The following topics are covered:

• Prerequisites

• Installation Procedure

---

Prerequisites

For details, refer to the section Prerequisites.

Installation Procedure

To install the Natural Web I/O Interface Server CICS Adapter, perform the following steps:

Step 1: Customize CICS

(Job I005, Steps 9405, 9406, 9410, 9411)

The Natural Web I/O Interface server load library must be defined in the CICS DFHRPL concatenation.

Customize the standard listener CSKL of the CICS socket interface using the CICS transaction EZAC,DISplay,LISTENER and, on the second screen, define NATUXRFE in the SECEXIT field of EZAL.

Specify AF=INET6 if IPv6 (Internet Protocol Version 6) is to be used.

The definition of SECEXIT=NATUXRFE is mandatory when the Natural Web I/O Interface server is started with impersonation (parameter SECURITY_MODE).

Start the standard listener using the CICS transaction EZAO.

The following CICS resource definitions are required:

1. Define the CICS transaction for the remote front-end. This transaction name is an arbitrary name which must be defined in the NWO configuration parameter RFE_CICS_TA_NAME. This document uses the transaction name NRFE.

   DEFINE TRANSACTION(NRFE) GROUP(NWOgroup)
   PROGRAM(NATCNRFE)
   TWASIZE(128)
   RESART(NO)
   TASKDATAKEY(USER)
   TASKDATALOC(ANY)

2. Define the programs NATCNRFE and NATLRGWO.

   DEFINE PROGRAM(NATCNRFE) GROUP(NWOgroup)
   LANGUAGE(C) DATALOCATION(ANY) EXECKEY(USER)
   *
   DEFINE PROGRAM(NATLRGWO) GROUP(NWOgroup)
   LANGUAGE(C) DATALOCATION(ANY) EXECKEY(USER)

   Define the program NATUXRFE.

   DEFINE PROGRAM(NATUXRFE) GROUP(NWOgroup)
   LANGUAGE(Le370) DATALOCATION(ANY) EXECKEY(CICS)

3. For DB2 access, a DB2 plan name must be defined. If you have not specified a DB2 plan name for pool threads in the DB2CONN resource definition, the transaction specified in RFE_CICS_TA_NAME and its associated DB2 plan name must be defined to CICS with a DB2TRAN and/or DB2ENTRY resource definition.

   Note:
   The dynamic plan selection provided by the Natural for DB2 interface must not be used.

4. For DB2 access, the authorization ID under which the NWO CICS transaction is accessing DB2 must have the necessary privileges for DB2 access. The authorization ID to be used is specified in the DB2ENTRY resource definition. If you choose the USERID option, the user ID of the CICS system will be used because the NWO CICS transactions are running under the user ID of the CICS system.

The sample JCL containing the following members defines all necessary CICS entries:

• NWOCONF

Step 2: Create member for CICS server

• Job I009, Step 9411, create member NWOCONFC for CICS server

Step 3: Link the object modules into the NWO load library

(Job I054, Step 8420)

The NWO object modules must be linked with the necessary runtime extensions of your CICS installations into executable load modules.

See sample job NWOI054 on data set NWOvrs.JOBS.

Step 4: Create startup procedure

• Job I200, Step 9416, create startup procedure for CICS server

Step 5: Customize the Natural Web I/O Interface Server

In order to dispatch the NWO Natural sessions in CICS, you must adapt the configuration file of your Natural Web I/O Interface server running under z/OS in batch mode. For this purpose, two sample JCL members (NWOI009C and NWOCONFC) are available.

Refer to Configuring the Natural Web I/O Interface Server CICS Adapter and to Configuring the Natural Web I/O Interface Server.