ETSYNC - Issue Syncpoint upon End of Transaction/Backout Transaction

This Natural profile parameter determines whether or not an implicit syncpoint is issued whenever an END TRANSACTION or BACKOUT TRANSACTION statement is to be issued.

Possible settings	`ON`	Natural issues an implicit syncpoint `COMMIT` whenever an `END TRANSACTION` statement is to be issued. Natural issues an implicit syncpoint `ROLLBACK` whenever a `BACKOUT TRANSACTION` statement is to be issued. This is useful for the synchronization of database transactions that are performed from within 3GL programs.
Possible settings	`OFF`	Natural does not issue an implicit syncpoint when an `END TRANSACTION` or `BACKOUT TRANSACTION` statement is to be issued.
Default setting	`OFF`
Dynamic specification	yes
Specification within session	no

Notes:

To issue syncpoints, Natural uses

Resource Recovery Services (RRS) under TSO and in batch mode to commit or rollback the unit of recovery,
CICS commands SYNCPOINT and SYNCPOINT ROLLBACK under CICS,
system service calls CHECKPOINT (CHKP) and ROLLBACK (ROLB) under IMS TM.

The processing sequence is as follows:

an END TRANSACTION / BACKOUT TRANSACTION statement is issued to the database specified with the profile parameter ETDB,
the syncpoint COMMIT / ROLLBACK is issued,
END TRANSACTION or BACKOUT TRANSACTION statements are issued to the remaining databases.

Restrictions and Limitations:

This functionality is available under the z/OS operating system
- in batch mode,
- under the TP monitor CICS,
- under the TP monitor TSO,
- under the TP monitor IMS TM in a non-message driven BMP (in all other environments under IMS TM, only a ROLLBACK is executed, but no CHECKPOINT).
To synchronize Adabas transactions, the Adabas Transaction Manager (ATM) must be installed.
For transactions in batch mode or under TSO that update data stored in a DB2 database, you must configure Natural for DB2 and/or your 3GL application to use the RRSAF interface.
For transactions in batch mode that update data stored in a DL/I database, Resource Recovery Services are not supported due to a DL/I restriction. If, additionally, data stored in a DB2 database is updated in the same transaction, synchronization is performed by means of the DL/I synchronization mechanism.

As a consequence, if data stored in an Adabas database is updated in addition to data stored in DB2 and DL/I databases, no synchronization is possible, not even if the Adabas Transaction Manager is installed.