Preparing the CICS Environment

The following diagram shows the basic flow of a CICS transaction. It illustrates how the client application communicates with the adapter.

The communication to the NATURAL CICS Transactions region depends upon the platform the adapter is running on. If you are using UNIX or Microsoft Windows, you can use a communication transport of TCP 62 (AnyNET) for DPL programs or LU6.2 for APPC programs. If you are using z/OS, a direct NATURAL CICS Transactions External Call Interface is used for DPL programs (use of LU6.2 for APPC programs from z/OS is not supported in this release of the server).

To provide for transparent execution of NATURAL CICS Transactions programs, metadata describing the program input and output areas is held on the server. For DPL programs, the Natural Data Area describing DFHCOMMAREA is used as a source for metadata creation. For APPC-based programs, the Natural Data Area describing the storage layout for NATURAL CICS Transactions SEND and RECEIVE calls is used as a source for metadata creation: RECEIVE for input; SEND for output.

You can use the Web Console or the Data Management Console for configuration and to create/maintain the metadata associated with the programs to be executed. You can also use the Web Console to add or change adapter communication parameters.


iWay Software