The Entire Transaction Propagator Interface for CICS (product code: ETC) is a separate Software AG Selectable Unit to support the operation of the Entire Transaction Propagator (product code: ETP) for 3GL programs running in a CICS/TS or CICS/VSE environment. ETC is not needed when running Natural application programs alone with CICS. ETC is provided in your installation library only if the ETC selectable unit has been ordered for your site.
This document covers the following topics:
For a description of the ETC ABEND codes that can occur when ETC is active, refer to ETP Abend Codes (in the Natural Messages and Codes documentation).
The figure below shows how 3GL user application programs, Natural and ETC/ETP work together to use ETP services for logging Adabas database transactions.
This section describes the operating system and companion software needed to run ETC, and describes the modules contained on the ETC release (distribution) tape.
ETP Version 1.5.2 and a CICS installation is required to install ETC. The prerequisite versions of
z/OS and CICS/TS;
or z/VSE and CICS/VSE;
other Software AG products
are listed in the current Natural Release Notes for Mainframes.
The ETC distribution tape contains the following datasets:
| Dataset Name: | Description: |
|---|---|
ETCvrs.LIBR |
On z/VSE system tapes only. z/VSE LIBR backup format of the
ETC product sub-library. This sub-library also contains the assembler macro
ETCPARM for parameter module generation and an example for calling
the ETCPARM macro.
|
ETCvrs.LIBJ |
On z/VSE system tapes only. Example installation jobs. |
ETCvrs.LOAD |
On z/OS system tapes only. z/OS load library. |
ETCvrs.SRCE |
On z/OS system tapes only. Assembler macro
ETCPARM for parameter module generation and an example for calling
the ETCPARM macro.
|
- where vrs is the respective ETC version/release/SM. For more information, see the Report of Tape Creation delivered with the distribution tape.
This document describes how to install ETC. The headings in each section are keyed to the corresponding job and step numbers of Software AG's System Maintenance Aid (SMA)-generated installation. This information is shown in brackets.
The Entire Transaction Propagator Interface for CICS (ETC) provides the functionality for Natural as well as 3GL applications running with ETP in a CICS environment. When running only Natural with ETP and CICS, however, only ETP is required.
When running ETC, the following restrictions apply;
No changes can be made to the database ID or file number in the
Adabas Control Block by Adabas or ADALNC user exits;
You cannot specify a database as an ETP database in the Natural
NATPARM file using the NTDB macro or
dynamically at Natural startup; Natural calls to the Adabas database are also
trapped by ETC, which can cause unpredictable results when processed twice by
ETP.
ETC may be linked with any combination of
RMODE and AMODE values. You must
not link ETC as a reentrant module.
ETC expects that the Adabas parameter list is passed in the CICS TWA; Adabas parameter lists in the COMMAREA are not supported.
Natural or 3GL applications running with ETC cannot run in a z/OS
Parallel Sysplex environment where z/OS image switching is to be supported. Set
the Natural profile parameter ADAMODE (see the
Parameter Reference documentation) to 0 or
3 to guarantee that Adabas calls issued by the user application
are correctly processed. CICS Plex support is limited to a single z/OS
image.
ETC cannot be used to log Adabas database transactions issued by the Natural Development Server CICS Adapter.
ETC cannot run in a threadsafe CICS environment, that is,
CONCURRENCY(QUASIRENT) must be set in the CICS program definition.
Using CONCURRENCY(THREADSAFE) will lead to unpredictable
results.
ETC cannot handle the new control block format as available with Adabas Version 8; if such a control block is encountered, an error is returned to the application that issued the database call.
If the Adabas Bridge for VSAM is installed, AVBUSER
MODE=ET should be specified.
Proceed with ETC Installation Procedure.
