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

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. Secondary resources qualify security within the limits of
the primary resource. For example, you can restrict the user plans
that can be reviewed by DB2 subsystem name and by plan name
within DB2 subsystem using the PLANSUMM function. 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.
Chapter 2: Security Definitions Profiles/Resources Directory
The Monitor for MVS 2.0 2-35
System Administrator’s Guide