Restart of started transactions
Non-terminal START transactions that are defined with RESTART(YES) are eligible for restart in certain circumstances only.
The effect of RESTART(NO) and RESTART(YES) on started transactions is shown in Table 1.
| Description of non-terminal START command | Events | Effect of RESTART(YES) | Effect of RESTART(NO) |
|---|---|---|---|
| Specifies either recoverable or nonrecoverable data | Started task ends normally, but does not retrieve data. | START request and its data (TS queue) are discarded at normal end. | START request and its data (TS queue) are discarded at normal end. |
| Specifies recoverable data | Started task abends after retrieving its data | START request and its data are recovered and restarted, up to n¹ times. | START request and its data are discarded. |
| Specifies recoverable data | Started task abends without retrieving its data | START request and its data are recovered and restarted, up to n¹ times. | START request and its data are discarded. |
| Specifies nonrecoverable data | Started task abends after retrieving its data | START request is discarded and not restarted. | Not restarted. |
| Specifies nonrecoverable data | Started task abends without retrieving its data | Transaction is restarted with its data still available, up to n¹ times. | START request and its data are discarded. |
| Without data | Started task abends | Transaction is restarted up to n¹ times. | — |
¹ n is defined in the transaction restart program, DFHREST, where the CICS®-supplied default is 20.
Note: Channel data
is not recoverable, therefore channels are not available on restart.
Transactions with large channels, for example, greater than 32 KB,
cannot be restarted.