Previous Topic: Resources Longer than Eight CharactersNext Topic: Mixing MASK and NOMASK


Resource Masking Implications

Before altering an existing resource class from NOMASK to MASK (or the reverse):

Although the LIST command displays MASK and NOMASK resources as if the names were identical, the resource names of MASKABLE resources are stored differently from NONMASKABLE resources.

Once you have altered a resource class from NOMASK to MASK, ownerships and permissions entered under the NOMASK regime continue to be honored, but these resources cannot be altered through administration commands. Permissions that contain mask characters but which were entered under a NOMASK regime are not interpreted as masked permissions. You cannot enter what appear to be maskable permissions until the resource class was actually altered to ATTR(MASK). Such resource are flagged by the LIST statement with the following to signify that it will not be treated as a mask:

ATTRIB=NONMASK