This documentation describes the ETP Interface for CICS (ETC) for installing and running ETP with CICS.
ETP allows Adabas users to have duplicate, or replicate, database files in a single database or distributed network. The copies can be distributed throughout a network to provide quick, economical access at user locations.
This documentation is intended for those who are planning for distributed database processing, are looking for a solution that combines databases into a central database resource, or are installing or already using a distributed Adabas/Net-work system.
For a list of the ABEND codes that can occur during the operation of ETC, refer to the Entire Transaction Propagator Abend Codes in the Natural Messages and Codes documentation.
For installation instructions, refer to Installing the ETP Interface for CICS in the Installation for z/OS and Installation for z/VSE documentation.
This section covers the following topics:
This section describes the features, enhancements and corrections that apply to the Version 1.5.2 of the ETP Interface for CICS (ETC):
Error Corrections:
ETC Version 1.5.2 contains all Zaps applied to ETC Version 1.5.1 as
error corrections.
Database IDs:
ETC now supports DBIDs in the range of 1 to 65535. However, the value
of 255 remains excluded.
Databases Defined in ETCPARM:
The number of databases that can be defined in the parameter module
ETCPARM has been increased to 512.
PUSERTO Defined in ETCPARM:
The maximum value for the timeout of a PUSER slot has
been increased to 570. The default value for this parameter has been changed to
30.
With the next major release of ETC (following Version 1.5), the support of the following features will be discontinued:
Format buffer optimization (enabled by the parameter
FBOPT in the ETCPARM macro).
Adabas Support for SAP R/2 Application (enabled by the parameter
SAP in the ETCPARM macro).
When running the 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
parameter module 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 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.
The figure below shows how 3GL user application programs, Natural and ETC/ETP work together to use ETP services for logging Adabas database transactions.
