This section deals with both backward and forward recovery of temporary storage.
Temporary storage queues that are to be recoverable by CICS® must be on auxiliary temporary storage.
Define temporary storage queues as recoverable using temporary storage model resource definitions as shown in the following example define statements:
CEDA DEFINE DESCRIPTION(Recoverable TS queues for START requests) TSMODEL(RECOV1)
GROUP(TSRECOV) PREFIX(DF) LOCATION(AUXILIARY) RECOVERY(YES)
CEDA DEFINE DESCRIPTION(Recoverable TS queues for BMS) TSMODEL(RECOV2)
GROUP(TSRECOV) PREFIX(**) LOCATION(AUXILIARY) RECOVERY(YES)
CEDA DEFINE DESCRIPTION(Recoverable TS queues for BMS) TSMODEL(RECOV3)
GROUP(TSRECOV) PREFIX($$) LOCATION(AUXILIARY) RECOVERY(YES)
CICS continues to support temporary storage tables (TST) and you could define recoverable TS queues in a TST, as shown in the following example:
DFHTST TYPE=RECOVERY,
DATAID=(DF,**,
$$(,character-string)...)
The DATAID DF makes the temporary storage queues used on CICS start requests recoverable.
The DATAIDs ** and $$ make the temporary storage queues used by BMS recoverable.
The DATAID character string represents the leading characters of each temporary storage queue identifier that you want to be recoverable. For example, DATAID=(R,ZIP) makes recoverable all temporary storage queues that have identifiers starting with the character "R" or the characters "ZIP".
For more information on allocation and space requirements, see theCICS Operations and Utilities Guide.
If you want forward recovery of temporary storage: