rmpolicy
Lists policies
Applicability
Product |
Command type |
---|---|
VersionVault |
cleartool subcommand |
Platform |
---|
UNIX |
Linux |
Windows |
Synopsis
- rmpolicy [ –c/omment comment | –cfi/le pname | –cq/uery | –cqe/ach | –nc/omment ]
- policy-selector ...
Description
The rmpolicy removes policies from the current VOB.
Restrictions
Authorization
- read-info on VOB object
- read-name on policy
- delete on policy
Locks
An error occurs if one or more of these objects are locked: VOB, policy.
Mastership
(Replicated VOBs only). The policy must be mastered by the VOB at which this command is issued.
Additional restriction
A policy cannot be removed if it is implemented by a rolemap.
Options and arguments
Event records and comments
- Default
- Creates one or more event records, with commenting controlled by your .versionvault_profile file (default: –cqe). See the comments reference page. Comments can be edited with chevent.
- –c/omment comment | –cfi/le comment-file-pname |–cq/uery | –cqe/ach | –nc/omment
- Overrides the default with the option you specify. See the comments reference page.
Specifying the policy
Default: None.
- policy-selector
- The policy that is to be removed.
Examples
The UNIX system and Linux examples in this section are written for use in csh. If you use another shell, you might need to use different quoting and escaping conventions.
The Windows examples that include wildcards or quoting are written for use in cleartool interactive mode. If you use cleartool single-command mode, you might need to change the wildcards and quoting to make your command interpreter process the command appropriately.
In cleartool single-command mode, cmd-context represents the UNIX system and Linux shells or Windows command interpreter prompt, followed by the cleartool command. In cleartool interactive mode, cmd-context represents the interactive cleartool prompt.
- Remove a policy; do not prompt
for confirmation.
cmd-context cleartool rmpolicy -force DeveloperVobPolicy