Use this subcommand to delete objects specified by a scope without performing a preview. Any previous preview object list is cleared on completion.
ccm soad|save_offline_and_delete -delete -scope scope_name [-so|-save_offline] [-path soad_path] [-pn|-package_name package_name] [-v|-verbose] [argument...]
If you have not saved a package previously, you must specify the path.
Arguments are required only if appropriate for the specified scope. For example, the scope "My working projects and products for a specified release" requires that you specify a release value, which is an argument.
You must specify the arguments in the order used in the scope definition.
The Save Offline and Delete (SOAD) utility deletes objects from a Synergy database by using a scope. The scope determines what objects are considered for deletion, which associated objects can also be deleted, and rules for when objects should not be deleted. Synergy ships with predefined scopes that represent typical reasons for deleting objects. Users can also create their own custom scopes. See the #soad_scope command for details.
You can delete objects from a Synergy database to:
These are examples of the types of data that you can delete:
SOAD also saves objects offline before they are deleted so that the objects can be restored in a Synergy database at a later date. Users in the ccm_admin role can use this feature in databases that are DCM initialized. The objects to be saved are stored in a save offline package that is similar to a DCM package. The objects are restored using a DCM receive operation. See CLI operation for details.
The scope defines which role a user must be in before they can use that scope. In addition, normal Synergy security rules apply about when an object can be deleted. You can delete any working-state project or object owned by you. If you are working as a build manager, you can also delete prep projects and objects. If you are in the ccm_admin role, you can delete objects in any non-working state or objects owned by other users. SOAD also has a number of built-in safety measures to prevent certain types of objects, such as type definitions and other administrative data, from being deleted.