Domain: | SECURITY-ADMINISTRATION |
Privileges: | STD-PROCESSING, GUARD-ADMINISTRATION |
Users can use this rule to display whether they are co-owners of a specified object name together with the rules in which their co-ownership is described.
Co-ownership rules can be specified for both files and job variables and entered in a separate, active rule container for each of these object types. For this reason, the RULE-CONTAINER-TYPE operand is used to define whether information is required concerning the co-ownership of files or job variables.
A separate step is required in order to display the access conditions which have to be satisfied. The condition guards named in the displayed rules can be displayed using the /SHOW-ACCESS-ADMISSION command.
For more detailed information on how to display access permissions, please refer to the description of the /SHOW-ACCESS-ADMISSION command.
Output of the co-ownership permissions corresponds to that produced by the /SHOW-COOWNER-PROTECTION-RULE command. However, it differs from this latter command in that only the subset of rules which are relevant to the specified user ID is output.
Rules which prohibit co-ownership are not displayed.
This command displays only those rules which are relevant to the caller. However, whether or not co-ownership is actually possible depends on further criteria.
SHOW-COOWNER-ADMISSION-RULE (SHO-COO-ADMIS-R) | ||||||||||||||||||||
|
OBJECT-NAME = <filename 1..54 without-gen-with-wild>
Name of the object about which the user wants to determine his or her co-owner status.
If wildcards are used then only the following specifications are permitted:
:<catid>:$<userid>.*
$<userid>.* or
*
Wildcards are not permitted in the catalog or user ID.
If a fully qualified object name specification is supplied, the first rule which is relevant to the user is displayed. This is also the rule which is consulted for the co-ownership check.
If the wildcard “*” is specified in the name part of the object name, all the rules which are relevant to the user are displayed. In this way, users can obtain information concerning the naming conventions and access conditions that have to be satisfied if they are to be co-owners of files belonging to a different user ID.
RULE-CONTAINER-TYPE =
Type of active rule container which is to be searched for a matching co-ownership rule
RULE-CONTAINER-TYPE = *FILE
The active rule container which contains rules for file co-ownership is to be searched (SYS.UCF[<n>])
RULE-CONTAINER-TYPE = *JV
The active rule container which contains rules for job variable co-ownership is to be searched (SYS.UCJ[<n>])
RULE-CONTAINER-TYPE = *CAPRI
The active rule container which contains rules for CAPRI co-ownership is to be searched (SYS.UCC[<n>])
See also the documentation of CAPRI at http://manuals.ts.fujitsu.com.
OUTPUT = list-poss(2):
This operand defines the destination of the output.
OUTPUT = *SYSOUT
Output is sent to the terminal if the command was issued in interactive mode. In batch mode, the output destination depends on the specifications in the job.
OUTPUT = *SYSLST(...)
Output is sent to the system file SYSLST.
SYSLST-NUMBER = *STD
Output is sent to the system file SYSLST.
SYSLST-NUMBER = <integer 1..99>
Two-digit number nn used to form the file name SYSLSTnn.
Output layout (admission rules)
Example 1
A user LUCIFER wants information about the rule which gives him co-owner access to the file PARADISE under the user ID $GABRIEL.
The user enters the following command:
|
Example 2
A user LUCIFER wants information about the rules which give him co-owner access to the files of the user ID $GABRIEL.
The user enters the following command:
|
The format of the output is not guaranteed.
Command return codes
(SC2) | SC1 | Maincode | Meaning |
0 | CMD0001 | Command successfully executed | |
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 | COO3302 | The user is not authorized to execute the function. | |
64 | COO3308 | A user ID is unknown. | |
64 | COO3309 | Remote file access not supported. | |
64 | COO3312 | No access rule was found for the specified object for access. | |
64 | COO3314 | Error in MRS communications resources. | |
64 | COO3316 | Co-owner access is not permitted. | |
64 | COO3321 | The active rule container is not accessible. | |
128 | COO3900 | There is no longer sufficient system storage space available. | |
128 | OPS0002 | Output of S variables has been aborted | |
130 | OPS0001 | It was not possible to output the S variables | |
32 | CMD2009 | System error during output of S variables |
Output in S variables
Output Information | Name of the S variable | T | Contents | Condition |
Name of the object | VAR(*LIST).OBJECT-NAME | S | <filename 1..54 | |
Type of active rule container | VAR(*LIST).CONTAIN-TYPE | S | *FILE | |
Name of the rule | VAR(*LIST). | S | <alphanumeric name | |
Object name of the rule | VAR(*LIST). | S | <filename 1..41 | |
Name of the condition guard in the | VAR(*LIST). | S | *NONE | |
Co-ownership of TSOS | VAR(*LIST). | S | *SYSTEM-STD |