Landmark Lighting D20R2-06/99 User Manual Page 78
- Page / 120
- Table of contents
- BOOKMARKS
Rated. / 5. Based on customer reviews
Product Description
TMON for MQSeries Specify the SLUCOUNT startup
parameter in member TMQSPARM of the
data set identified by ddname
TMQSPRMS in the TMON for MQSeries
startup JCL.
TMON for MVS Specify the SLUCOUNT startup
parameter in member TMVSPARM of the
data set identified by ddname
TMVSPRMS in the TMON for MVS startup
JCL.
Use the following template when coding your SLU definitions. A
sample of an SLU definition can be found in member TCEVTAM
(TMON for CICS/ESA), TMON8VTM (TMON for CICS/MVS),
TMDBVTAM (TMON for DB2), TDBCVTAM (TMON for DBCTL),
TMQSVTAM (TMON for MQSeries), or TMONAPPL (TMON for
MVS) in the sample JCL library.
label VBUILD TYPE=APPL
sluidnnn APPL AUTH=(ACQ,PASS,VPACE),VPACING=5,EAS=1,
DLOGMOD=SLUTYPE2,MODTAB=LMRKMTB
sluidnnn APPL AUTH=(ACQ,PASS,VPACE),VPACING=5,EAS=1,
DLOGMOD=SLUTYPE2,MODTAB=LMRKMTB
sluidnnn APPL AUTH=(ACQ,PASS,VPACE),VPACING=5,EAS=1,
DLOGMOD=SLUTYPE2,MODTAB=LMRKMTB
“label” indicates the SYS1.VTAMLST member name used to store
the SLU definitions and “sluidnnn” indicates the name of the SLU
you are defining. The “sluid” part of the name is the SLU session
ID prefix and must be a constant string from one to five characters
long. The “nnn” part must be a number starting with 001 and
sequentially increment with each APPL macro.
For example, if you use TMON as a session ID prefix and define the
following SLUs to VTAM, only TMON001, TMON002, and
TMON003 are used. TMON006 is not used because TMON004 and
TMON005 are missing.
TMON001 APPL AUTH=(ACQ,PASS,VPACE),VPACING=5,EAS=1,
DLOGMOD=SLUTYPE2,MODTAB=LMRKMTB
TMON002 APPL AUTH=(ACQ,PASS,VPACE),VPACING=5,EAS=1,
DLOGMOD=SLUTYPE2,MMODTAB=LMRKMTB
TMON003 APPL AUTH=(ACQ,PASS,VPACE),VPACING=5,EAS=1,
DLOGMOD=SLUTYPE2,MODTAB=LMRKMTB
TMON006 APPL AUTH=(ACQ,PASS,VPACE),VPACING=5,EAS=1,
DLOGMOD=SLUTYPE2,MODTAB=LMRKMTB
You must use different SLU prefixes on different processor
complexes and for different products running in the same
processor complex.
Setting Up Landmark Product Communication Chapter 3: Landmark Product Communication
3-6
- 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.075 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Comments to this Manuals