Defining class names for Db2 objects in multiple-subsystem scope

When you select this model, the RACF access control module places the Db2 subsystem name in the resource name.

Class names that you define must have the following format:
abbbbxxz
where:
a
Is M for member class or G for grouping class
bbbb
Is the &CLASSNMT value (the default value is DSN)
xx
Is the type of Db2 object (see Db2 object types for valid values)
z
Is the &CHAROPT value (ignored if &CLASSNMT='DSN')

In multiple-subsystem scope, profile names of resources in the Db2 object classes are prefixed with the Db2 subsystem name, or group attachment name, but the class names are not. See the following figure.

Figure 1. Multiple-subsystem scope classes
Begin figure description. This figure is described in the surrounding text. End figure description.

If you use the multiple-subsystem scope and the default &CLASSNMT value (DSN), you can use the classes provided in the supplied class descriptor table (ICHRRCDX). Any subsystem sharing the RACF access control module can share the same set of classes. You are not required to define a separate set of classes for each subsystem.

You can change &CLASSNMT if you do not want to use the default (DSN) value. However, if you set &CLASSNMT to a value other than DSN, you must define classes in the class descriptor table (CDT). You can define two classes for each object type if you want both member and grouping classes. If only one class is defined for each object type, the class name must begin with M (not G).