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, from which the default values are then taken. A rule container is activated when its name complies with a naming convention (see “Naming convention” below). A corresponding naming convention also applies to the activation of pubsetglobal rule containers, which are always expected under the user ID TSOS.

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 see "Naming convention” and “Renaming a rule container” 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 default 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

  P: Pubset global

• Container type:

  D: Default 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.UDF	Active, user-specific primary container for files
SYS.UDF<n>	Active, user-specific secondary container for files (n=1..9)
SYS.UDJ	Active, user-specific primary container for job variables
SYS.UDJ<n>	Active, user-specific secondary container for job variables (n=1..9)
SYS.PDF	Active, pubset-global primary container for files
SYS.PDF<n>	Active, pubset-global secondary container for files (n=1..9)
SYS.PDJ	Active, pubset-global primary container for job variables
SYS.PDJ<n>	Active, pubset-global 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 default protection is to apply. Active, pubset-global rule containers are expected to be stored under $TSOS. All rule containers must be located on the same pubset as the objects to which default values are to be assigned.

Example

It is necessary to specify that certain default protection attributes should apply to files which belong to the user ID OTTO and whose names start with ’SYS.’ or ’A’. To do this, it is necessary to create the rule container $OTTO.SYS.UDF under the user ID. This rule container contains the corresponding rules:

Renaming rule containers

The GUARDS administration command /MODIFY-GUARD-ATTRIBUTES is available for renaming 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 default protection is to be provided in the guard UDF.BAK and then replaced by rules which are located in the rule container UDF.NEW.

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

/modify-guard-attributes guard-name=udf.neu,new-name=sys.udf