Coding transaction backout exits

You have access to all CICS® services, except terminal control services, during exit execution.

About this task

However, consider the following restrictions:
  • The exit programs must be written in assembler code.
  • They must be quasi-reentrant. They may use the exit programming interface (XPI) and issue EXEC CICS commands.
  • If an exit program acquires an area as a result of a file control request, it is the responsibility of the exit to release that area.
  • An exit must not attempt to make any file control requests to a file referring to a VSAM data set opened in non-RLS mode with a string number of 1, unless no action is specified for that file during the initialization exit.
  • Task-chained storage acquired in an exit should be released by the exit as soon as its contents are no longer needed.
  • If an exit is not used, the default actions are taken.
  • We strongly recommend that emergency restart global user exits do not change any recoverable resource. If you do try to use temporary storage, transient data, or file control, these resource managers may also be in a state of recovery. Access to these services will, therefore, at best cause serialization of the recovery tasks and, at worst, cause a deadlock.


dfht23h.html | Timestamp icon Last updated: Monday, 5 June 2017