Format { ALL } { FIELD } PURGE { RECORD } [ qualifier ] ... element-name ,... . { } { GENERIC type-name }
1 – Parameters
1.1 – type-name
Specifies the type of the generic element you are purging.
1.2 – element-name
Specifies the element that you are purging. You can use wildcard characters in this parameter.
2 – Qualifiers
2.1 /DESCENDANTS
Format options: /DESCENDANTS /NODESCENDANTS (default) Specifies whether CDO also purges children. When you specify the /DESCENDANTS qualifier, and your element is controlled, CDO deletes all children that are not also children of additional elements outside the area defined by your top collection. If the element is uncontrolled, CDO deletes all children that are not also children of any other elements.
2.2 /LOG
Format options: /LOG /NOLOG (default) Specifies whether CDO displays text confirming that the element was purged.
3 – Description
The PURGE command deletes all but the first and last version of an element. You cannot delete the first version, and intermediate versions are not purged if a branch line descends from them, or if they are children in a dependency relationship. You can only purge one line of descent at a time. Purge branch lines before main lines. You must specify a name of an element, or if you are using the PURGE ALL command, use the asterisk (*) wildcard character.
4 – Examples
1.CDO> PURGE RECORD REGION.INVENTORY.PART. In this example, the PURGE command deletes all but the first and highest numbered versions of the REGION.INVENTORY.PART record element. 2.CDO> PURGE ALL GREF*. In this example, the PURGE command deletes all but the first and highest versions of each element that begins with the letters GREF. 3.CDO> PURGE FIELD FIRST_NAME. . . . CDO> PURGE RECORD /DESCENDANTS FULL_NAME. In this example, the first PURGE command fails because the FIRST_NAME field element is a child of the FULL_NAME record element. By purging the descendants of FULL_NAME, you can accomplish the desired purge.