Installing the Natural Web I/O Interface Server CICS Adapter under SMARTS on z/VSE

This document describes how to install the CICS connection for a Natural Web I/O Interface server (product code NWO) running under SMARTS on z/VSE.

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, Step 9405)

The Natural Web I/O Interface server sublibrary must be defined in the CICS Libdef search chain.

Customize the standard listener EZAL 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.

As of z/VSE Version 4.1, the CICS task related user exit must be active (transaction EZAT).

Start the standard listener using the CICS transaction EZAO.

The following CICS resource definitions are required:

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)
           RESTART(NO)
           TASKDATAKEY(USER)
           TASKDATALOC(ANY)
```
Define the programs NATCNRFE, NATLRGWO and NATUXRFE:
```
DEFINE PROGRAM(NATCNRFE) GROUP(NWOgroup)
LANGUAGE(C) DATALOCATION(ANY) EXECKEY(USER)
```
```
DEFINE PROGRAM(NATLRGWO) GROUP(NWOgroup)
LANGUAGE(C) DATALOCATION(ANY) EXECKEY(USER)
```
```
DEFINE PROGRAM(NATUXRFE) GROUP(NWOgroup)
LANGUAGE(C) DATALOCATION(ANY) EXECKEY(USER)
```
NATUXRFE must be defined with EXECKEY(CICS) because the transaction CSKL is defined with TASKDATAKEY(CICS) and the program NATUXRFE is part of the calling chain initiated by CSKL. This also applies if another transaction defined with TASKDATAKEY(CICS) is used to invoke NATUXRFE.

In addition, when using the CICS open transaction environment (OTE), set the following parameters for NATCNRFE and NATUXRFE:
```
API(OPENAPI)
CONCURRENCY(THREADSAFE)
```
This is required, for example, if the parameter OTE=YES is set for the configuration macro EZACICD with TYPE=CICS for the CICS region, or if the parameter is set with the transaction EZAC,ALTER,CICS.

The values of API, CONCURRENCY and EXECKEY for NATCNRFE must be the same as for the environment-dependent nucleus of Natural because Natural is called by NATCNRFE using standard linkage conventions (direct branch using a BASR instruction) instead of an EXEC CICS LINK command.

You need not adapt the program definition of NATLRGWO for CICS OTE.

Step 2 : 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 SMARTS on z/VSE. For this purpose, one sample JCL member (SMAI009 Step 9410) is available.

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

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

(Job I054, Step 9420)

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