Landmark Lighting D20R2-06/99 User Manual Page 55
- Page / 120
- Table of contents
- BOOKMARKS
Rated. / 5. Based on customer reviews
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
- Administrator’s 1
- Contents 3
- Using this Guide 5
- Related Documentation 6
- The Monitor for MVS 2.0 v 7
- Comments 8
- IVP Checklist 9
- IVP Steps 9
- The Monitor for MVS 2.0 1-3 11
- System Administrator’s Guide 11
- The Monitor for MVS 2.0 1-5 13
- The Monitor for MVS 2.0 1-7 15
- Resolving accidental access 17
- How Product Security Works 18
- The Monitor for MVS 2.0 2-3 19
- Tracing Security Problems 20
- Using External Security 20
- Considerations when 21
- External Security 23
- Simplified Sign-On 23
- Using User Exit Security 24
- Using Internal Security 25
- Supplied User IDs and 26
- Profiles 26
- TMON for DB2 27
- TMON for DBCTL 27
- Implementing Internal 28
- Security 28
- The Monitor for MVS 2.0 2-13 29
- Security Definitions Menu 30
- Fields CURRENT USERS 31
- User Profiles Directory 32
- USER NAME 33
- User Definition 34
- PASSWORD 35
- PROFILE NAME 35
- USER FULL NAME 36
- Secured Functions Directory 37
- DESCRIPTION 38
- FUNCTION 38
- PRIMARY/SECONDARY RESOURCE 38
- SECONDARY 39
- TYPE VALUES 39
- Function Code Table 40
- The Monitor for MVS 2.0 2-25 41
- The Monitor for MVS 2.0 2-27 43
- The Monitor for MVS 2.0 2-29 45
- The Monitor for MVS 2.0 2-31 47
- Profiles/Resources Directory 49
- Fields PRIMARY RESOURCE 50
- TMON for CICS, TMON for 51
- DBCTL, TMON for 51
- MQSeries, and TMON for 51
- MVS do not use secondary 51
- Detail Profile Definition 52
- The Monitor for MVS 2.0 2-37 53
- LO-ACCESS LEVELS-HI 54
- PRIMARY RESOURCE 54
- SECONDARY RESOURCE 55
- Function Access Level Table 57
- The Monitor for MVS 2.0 2-43 59
- The Monitor for MVS 2.0 2-45 61
- The Monitor for MVS 2.0 2-47 63
- The Monitor for MVS 2.0 2-49 65
- The Monitor for MVS 2.0 2-51 67
- The Monitor for MVS 2.0 2-53 69
- The Monitor for MVS 2.0 2-55 71
- Access Methods 73
- The Monitor for MVS 2.0 3-3 75
- Product Applid System 76
- The Monitor for MVS 2.0 3-5 77
- MAXDATA should not exceed 80
- The Monitor for MVS 2.0 3-9 81
- Using Explicit Pass-Through 82
- JUMP=code 83
- REMOTE=applid 83
- The Monitor for MVS 2.0 3-11 83
- Using Implicit Pass-Through 84
- Using NaviGate 85
- The Monitor for MVS 2.0 3-15 87
- The Monitor for MVS 2.0 3-17 89
- Remote Sessions Directory 90
- The Monitor for MVS 2.0 3-19 91
- Remote Session Definition 93
- PRIMARY TMP 94
- The Monitor for MVS 2.0 3-23 95
- Remote Sessions Logon 96
- The Monitor for MVS 2.0 4-1 99
- Year 2000 Compliance Warranty 100
- Product Support 100
- Before Contacting 101
- Landmark 101
- . You also can 103
- (the quickest method) or 104
- Product Maintenance 106
- Service System (ECS) 107
- Electronic Customer 107
- Proactive 108
- Maintenance Policy 108
- Submitting an 108
- Enhancement Request 108
- New or Replacement 109
- Processors 109
- The Monitor for MVS 2.0 A-1 111
- Numbers and Special 113
- Characters 113
© 2020, manymanuals.com. All rights reserved. | 0.577 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Comments to this Manuals