Landmark Lighting D20R2-06/99 - Manual (Page 55)

beginning with the characters “PROD.” If you specify an asterisk
alone, all values of the primary resource are used.
If you want to specify more primary resources than this screen
allows (even after using pattern matching), add other definitions
for the profile using the other primary resources. Only the access
levels specified for the first profile/resource definition are used in
security for system functions (functions that do not use resources),
but all of the different primary resources in the other definitions are
included in the security for resource functions.
TMON for MQSeries example You can use the QMGRAUTH function to limit the queue managers
monitored by a given user ID. In this example, access levels are
defined for system functions based on the settings in the
$EXAMPLE profile with CSQ* resource. The access levels defined
for system functions in the $EXAMPLE profile with the CSQ*
resource are ignored. They are ignored because the CSQ* resource
is defined before the OTH* resource and, consequently, is
encountered first by Internal Security.
Profile ID Primary Resource
$EXAMPLE CSQ*
OTH*
PROFILE
Displays the 1- to 8-character product profile ID you selected on
the Profiles/Resources Directory screen. Change this ID if you
want to add a new profile definition.
SECONDARY RESOURCE
Shows the name of the auxiliary resource for this profile definition.
TMON for CICS, TMON for
DBCTL, TMON for
MQSeries, and TMON for
MVS do not use secondary
resources. TMON for DB2 secondary resources are DB2 plan or package
names. If you restrict TMON for DB2 by secondary resources, you
must first specify a primary and secondary resource pair in the
profile using an asterisk (*) for the secondary resource. You then
can specify a second primary and secondary resource pair in the
profile using the transaction ID for the secondary resource. This
step is necessary because TMON for DB2 security needs to know
what default security to use for DB2 subsystem names that match
the primary resource but DB2 plan or package names that do not
match the secondary resource.
An asterisk (*) in the field shows that pattern matching is being
used. For example, PROD* identifies all secondary resources
beginning with the letters “PROD.” If you specify an asterisk
alone, all values of the secondary resource are used.
If you want to specify more secondary resources than this screen
allows (even after using pattern matching), add other definitions
for the profile using the same primary resource and other
secondary resources. Only the access levels specified for the first
profile/primary resource/secondary resource definition are used in
security for system functions, but all of the defined secondary
Chapter 2: Security Definitions Detail Profile Definition
The Monitor for MVS 2.0 2-39
System Administrator’s Guide