Ensuring transaction rollback under CICS

Conditions that occur while an application is executing under CICS® can potentially contaminate any database currently being used by the application. It is essential that a rollback (the backing out of any updates made by the failing application) be performed before further damage to the database can occur.

There are two ways to ensure that a transaction rollback occurs when an unhandled condition of severity 2 or greater is detected:

See z/OS Language Environment Programming Reference for an explanation of the ABTERMENC runtime option. For more information about using assembler user exits, see Using runtime user exits.