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:
For details, refer to the section Prerequisites.
To install the Natural Web I/O Interface Server CICS Adapter, perform the following steps:
(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 and 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)
RESART(NO)
TASKDATAKEY(USER)
TASKDATALOC(ANY)
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)
Note:
If CICS runs with storage protection, NATCNRFE must be
defined with EXECKEY=(CICS).
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.
(Job I054, Step 9420)
The NWO object modules must be linked with the necessary runtime extensions of your CICS installations into executable load modules.