CLOD System Task

The CLOD task invokes the load area cleanup task. This task erases logically deleted load modules from the specified dictionary load areas (DDLDCLOD and DDLCATLOD). Logically deleted load modules get created when you regenerate, for example, an existing subschema, CA ADS dialog, or access module.
idmscu19
The CLOD task invokes the load area cleanup task. This task erases logically deleted load modules from the specified dictionary load areas (DDLDCLOD and DDLCATLOD). Logically deleted load modules get created when you regenerate, for example, an existing subschema, CA ADS dialog, or access module.
Syntax
►►─── CLOD ─┬───────────────────┬─────────────────────────────────────────────►◄             └─ 
dictionary-name
 ─┘
Parameter
  • dictionary-name
    The name of the dictionary whose load areas are to be processed.
    By default, if you do not specify a dictionary, DC/UCF processes the load areas of the default dictionary for the system.
Usage
Areas must be available for update
In order to purge load modules from a load area, the area must be available in update mode. Only areas available in update mode are processed.
When to use CLOD
All load areas are cleaned up as part of normal startup operations. This should be sufficient for production systems. For active development systems, CLOD may need to be run periodically to purge logically deleted load modules.
Example
CLOD dictionary-name
IDMS DC295005 V55 0000 LOGICALLY DELETED LOAD MODULES ERASED - DICT=DEFAULT AREA= IDMS DC295005 V55 0000 LOGICALLY DELETED LOAD MODULES ERASED - DICT=DEFAULT AREA= Vnnn ENTER NEXT TASK CODE:      CA IDMS release nn.n tape volser node nodename