IBM SC34-7012-01 manual TDINTRA=NOEMPTY the default, Trigger levels for Terminal and System only

Temporary storage

Auxiliary temporary storage queue information (for both recoverable and non-recoverable queues) is retrieved from the warm keypoint. Note that TS READ pointers are recovered on a warm restart (which is not the case on an emergency restart).

CICS opens the auxiliary temporary storage data set for update.

Temporary storage data sharing server

Any queues written to a shared temporary storage pool, even though non-recoverable, persist across a warm restart.

Transient data

Transient data initialization on a warm restart depends on the TDINTRA system initialization parameter, which specifies whether or not TD is to initialize with empty intrapartition queues. The different options are discussed as follows:

TDINTRA=NOEMPTY (the default)

All transient data resource definitions are installed from the global catalog, including any definitions that were added dynamically during the previous run. TD queues are always installed as enabled.

CICS opens any extrapartition TD queues that need to be opened—that is, any that specify OPEN=INITIAL.

Note: If, during the period when CICS is installing the TD queues, an attempt is made to write a record to a CICS-defined queue that has not yet been installed (for example, CSSL), CICS writes the record to the CICS-defined queue CXRF.

The recovery manager returns log records and keypoint data associated with TD queues. CICS applies this data to the installed queue definitions to return the TD queues to the state they were in at normal shutdown. Logically recoverable, physically recoverable, and non-recoverable intrapartition TD queues are recovered from the warm keypoint data.

Trigger levels (for TERMINAL and SYSTEM only):

After the queues have been recovered, CICS checks the trigger level status of each intrapartition TD queue that is defined with FACILITY(TERMINALSYSTEM) to determine whether a start request needs to be rescheduled for the trigger transaction.

If a trigger transaction failed to complete during the previous run (that is, did not reach the empty queue (QZERO) condition) or the number of items on the queue is greater than the trigger level, CICS schedules a start request for the trigger transaction.

This does not apply to trigger transactions defined for queues that are associated with files (FACILITY(FILE)).

TDINTRA=EMPTY

If you specify this option, the transient data queues are cold started, but the resource definitions are warm started.

The following processing takes place:

Chapter 5. CICS warm restart 55