Domain: | SECURITY-ADMINISTRATION |
Privileges: | STD-PROCESSING, GUARD-ADMINISTRATION |
This command is used to remove co-owner protection rules from a rule container (guard of type: COOWNERP). Users may only remove rules from their own rule containers. Guard administrators may also delete rules from rule containers belonging to other user IDs. If there are no further rules in a container, the container itself is deleted.
REMOVE-COOWNER-PROTECTION-RULE (REM-COO-PRO-R) |
RULE-CONTAINER-GUARD = <filename 1..24 without-gen-vers with-wild(40)> ,PROTECTION-RULE = *ALL / <alphanum-name 1..12 with-wild(20)> ,DIALOG-CONTROL = *STD / *NO / *RULE-CONTAINER-CHANGE / *USER-ID-CHANGE / *CATALOG-CHANGE |
RULE-CONTAINER-GUARD = <filename 1..24 without-gen-vers with-wild(40)>
This operand designates the name of a rule container of type COOWNERP from which the rule is to be deleted.
If wildcards are used in the name of a rule container, a single command deletes the rule from multiple containers, provided that these are accessible.
The length of the name without wildcards, catalog ID and user ID must not exceed 8 characters.
Only a guard administrator can specify wildcards in the user ID.
The specification of the system default ID in the container name, e.g. $<filename> or $.<filename>, is not supported.
PROTECTION-RULE =
Specifies the rule which is to be deleted.
PROTECTION-RULE = *ALL
All the rules in the container are to be deleted. As a result, the entire container is also deleted.
PROTECTION-RULE = <alphanumeric name 1..12 with-wild(20)>
Name of the rule which is to be deleted. The name may contain wildcards.
DIALOG-CONTROL =
The user can use the command in a guided dialog and can define the type of dialog that is to be performed. Dialog control has no effect in batch mode and thus corresponds to the setting DIALOG-CONTROL=*NO.
DIALOG-CONTROL = *STD
For each selected rule container, the user can decide in interactive mode whether or not the command should be executed. However, dialog control is only performed if the name of the rule container is specified using wildcards.
It is possible to abort the command.
DIALOG-CONTROL = *NO
The command is executed for every selected rule container without any query being issued.
DIALOG-CONTROL = *RULE-CONTAINER-CHANGE
For each selected rule container, the user can decide in interactive mode whether or not the command should be executed. Dialog control is performed regardless of whether or not the name of the rule container is specified using wildcards.
It is possible to abort the command.
DIALOG-CONTROL = *USER-ID-CHANGE
This guided dialog can only be used by guard administrators.
For each selected user ID, a guard administrator can decide in interactive mode whether or not the command should be executed. However, dialog control is only performed if the user ID in the name of the rule container is specified using wildcards.
It is possible to abort the command.
DIALOG-CONTROL = *CATALOG-CHANGE
For each selected catalog ID, the user can decide in interactive mode whether or not the command should be executed. However, dialog control is only performed if the catalog ID in the name of the rule container is specified using wildcards.
It is possible to abort the command.
Command return codes
(SC2) | SC1 | Maincode | Meaning |
0 | CMD0001 | Command successfully executed | |
2 | 0 | COO3000 | The command was aborted at the user’s request. |
2 | 0 | COO3001 | A rule container was deleted because it contained no further rules. |
2 | 0 | COO3002 | During the processing of rule containers specified using wildcards, it was possible to process all the selected rule containers correctly. One or more rule containers were completely deleted. |
2 | 0 | COO3003 | During the processing of rule containers specified using wildcards, it was not possible to process all the selected rule containers correctly. |
2 | 0 | COO3004 | During the processing of rule containers specified using wildcards, it was not possible to process all the selected rule containers correctly and one or more rule containers were deleted. |
1 | COO3100 | An incorrect operand value was detected. | |
32 | COO3200 | An internal error has occurred. A SERSLOG entry has been generated to permit detailed analysis. | |
64 | COO3300 | The specified rule container does not exist. | |
64 | COO3302 | The user is not authorized to execute the function. | |
64 | COO3304 | No rule container has been selected. | |
64 | COO3306 | A specified guard is not of the required guard type. | |
64 | COO3308 | A user ID is unknown. | |
64 | COO3309 | Remote file access not supported. | |
64 | COO3310 | A rule was not found in the rule container. | |
64 | COO3313 | A specified public volume set is not available. | |
64 | COO3314 | Error in MRS communications resources. | |
64 | COO3315 | A specified public volume set is not known in the local GUARDS administration. | |
128 | COO3900 | There is no longer sufficient system storage space available. | |
128 | COO3901 | A guard which has to be processed is currently locked by another task and cannot be processed at the present time. | |
128 | COO3902 | A guard is temporarily unavailable because the GUARDS catalog is being changed or a master change is taking place in the computer network. |