Resource state requirements

A model CDRSC must be active before it can be used to build clone CDRSCs. You can activate a model CDRSC as you activate other CDRSC definitions by doing one of the following actions:

Issue a VARY ACT command.
Include the major node in which the model CDRSC is defined in the configuration list that VTAM® uses when it is initialized.

By activating the model CDRSC, you ensure that the state of the model CDRSC is active, making it available to build clone CDRSCs.

Clone CDRSCs are different from dynamic (clone) applications in that you can choose to retain the clone CDRSC even when they are deactivated or are no longer being used for sessions. You can do this by specifying DELETE=NO on the model CDRSC definition or on a VARY INACT operator command. The specification of the DELETE operand on the VARY command overrides the specification of the DELETE keyword on the model CDRSC definition. This also means that you can issue VARY ACT against an inactive clone CDRSC, which is not possible for dynamic (clone) applications.

Guidelines:

Deleting the clone CDRSCs immediately could result in storage thrashing (freeing and getting clone CDRSCs).
Deleting the clone CDRSCs immediately could result in search thrashing (losing search history and then rebuilding it).
Not deleting the clone CDRSCs could consume system resources unnecessarily.

For example:

If a particular set of CDRSCs is located once a day, then you should code DELETE=YES.
If a particular set of CDRSCs is located many times a day for a short lived session, then you should code DELETE=NO.