Design overview

During the execution of any transaction, certain temporary-storage data, intrapartition destinations, and files are protected for dynamic backout. In addition, for a transaction that is defined as restartable, the following actions take place:
  • Any terminal input/output area (TIOA), command-level communication area, or terminal user area existing at task initiation is copied to the dynamic log.
  • Interval control automatic initiate descriptors (AIDs) used in the task are preserved by means of deferred work elements (DWEs) until the next syncpoint.
  • Data is maintained to show:
    • What terminal traffic has occurred during the task
    • Whether a syncpoint has been passed
    • Whether or not the current activation of the task is the result of a restart.

If a transaction abends, but before backout has been attempted, DFHREST may be invoked to decide whether or not the task is to be restarted. Even if DFHREST decides that the transaction can be restarted, CICS® may overrule the restart, for example because of a transaction backout failure.

DFHREST is invoked by DFHXMTA passing a parameter list via a COMMAREA that is mapped by the DFHXMRSD DSECT. DFHREST should return to DFHXMTA, indicating whether or not the transaction should be restarted. If DFHREST requests a restart, and CICS does not overrule this decision, the principal facility is not released and the principal facility owner reattaches a new task to restart the transaction.
Note:
  1. DFHREST can invoke CICS facilities such as file control and transient data, using the command-level interface.
  2. If an error occurs while linking to, or in, the transaction restart program, the restart is not attempted for this task.
  3. DFHREST runs before backout.


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