Activating a rule container

Although an unlimited number of rule containers can be created under a user ID, only one of them can be active and included in the co-owner check. You activate a rule container by using a name that complies with the naming convention (see “Naming convention” below).

If a rule container is to be activated, you can use GUARDS administration commands to rename or copy it in order to bring about compliance with the relevant naming convention (see “Naming convention” below and “Renaming rule containers” below).

If an active rule container has no more space for any more rules, the user can create secondary containers that continue on from it. In this way, an active container sequence is formed, consisting of a primary container and up to nine secondary containers, each with a prescribed name complying with the naming convention.

The correct sequence for the secondary containers is defined by a serial number in the name. There are no additional links. The end of a sequence is reached as soon as the numeric sequence is interrupted or the last possible secondary container is reached.

Naming convention

The name of an active rule container for co-owner protection must be structured as follows:

SYS.<scope><container type><object type>[<secondary identifier>]

The following values are permitted for the individual components:

• Scope:

  U: User-specific

• Container type:

  C: Co-owner protection

• Object type

  F: File

  J: Job variable

• Secondary identifier:

  1..9: Number of secondary container

  If no secondary identifier is specified, then the container is a primary container. A maximum of ten rule containers can be active (1 primary container and, optionally, up to 9 secondary containers).

This means that the following names are permitted:

SYS.UCF	Active, user-specific primary container for files
SYS.UCF<n>	Active, user-specific secondary container for files (n=1..9)
SYS.UCJ	Active, user-specific primary container for job variables
SYS.UCJ<n>	Active, user-specific secondary container for job variables (n=1..9)

Active, user-specific rule containers are expected to be stored under the user ID to whose objects co-owner protection is to apply. All rule containers must be located on the same pubset as the objects which are to be protected.

Example

Co-owner protection is specified for files which belong to the user ID OTTO and whose names start with ’SYS.’ or ’A’. The rules are contained in the primary rule container for files $OTTO.SYS.UCF.

Renaming rule containers

The GUARDS administration command /MODIFY-GUARD-ATTRIBUTES can be used to rename rule containers.

It is particularly necessary to rename rule containers when an active rule container has to be deactivated or an inactive rule container has to be activated.

Example

Active co-owner protection is to be provided in the guard UCF.BAK and then replaced by rules located in the rule container UCF.NEW.

/modify-guard-attributes guard-name=sys.ucf,new-name=ucf.bak

/modify-guard-attributes guard-name=ucf.new,new-name=sys.ucf