Installing the Natural Development Server CICS Adapter under SMARTS on z/VSE

This document describes how to install the CICS connection for a Natural Development Server (NDV) 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 Development Server CICS Adapter, perform the following steps:

Step 1: Customize CICS

(Job I005, Step 8405)

The Natural Development 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.

The definition of SECEXIT=NATUXRFE is mandatory when the NDV server ist started with impersonation (parameter SECURITY_MODE).

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 NDV configuration parameter RFE_CICS_TA_NAME. This document uses the transaction name NRFE.
```
DEFINE TRANSACTION(NRFE) GROUP(ndvgroup)
           PROGRAM(NATCNRFE)
           TWASIZE(128)
           RESTART(NO)
           TASKDATAKEY(USER)
           TASKDATALOC(ANY)
```
Define the programs NATCNRFE, NATLRGWO and NATUXRFE:
```
DEFINE PROGRAM(NATCNRFE) GROUP(ndvgroup)
LANGUAGE(C) DATALOCATION(ANY) EXECKEY(USER)
```
```
DEFINE PROGRAM(NATLRGWO) GROUP(ndvgroup)
LANGUAGE(C) DATALOCATION(ANY) EXECKEY(USER)
```
```
DEFINE PROGRAM(NATUXRFE) GROUP(ndvgroup)
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 the CICS OTE.

Step 2: Link the object modules into the NDV load library

(Job I054, Step 8420)

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

Step 3: Customize the Development Server

In order to dispatch the NDV Natural sessions in CICS, you must adapt the configuration file of your development server running under SMARTS on z/VSE. For this purpose, one sample JCL member (SMAI009 Step 8410) is available.

Refer to Configuring the Natural Development Server CICS Adapter and to Configuring the Natural Development Server.