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

VTAM Logon
Mode Table
Considerations The DLOGMOD parameter of the APPL macro specifies the name
of the entry in the VTAM logon mode table that contains the
parameters used in a session. If you have SNA type-2 logical units
and your logon mode table is working, continue to use it. If you
have problems, however, create your own logon mode table with
the following entry. The following sample of a logon mode table
can be found in member LMRKMTB in the Strategic Services
sample JCL library.
LMRKMTB MODETAB
MODEENT LOGMODE=SLUTYPE2,FMPROF=X’03’,TSPROF=X’03’,
PRIPROT=X’B1’,SECPROT=X’90’,COMPROT=X’3080’,
RUSIZES=X’87C7’,PSERVIC=X’028000000000185018507F00
MODEEND
END
In this entry, the name defined by the LOGMODE operand
(SLUTYPE2 in the sample LMRKMTB above) can be any
8-character name. The FMPROF, TSPROF, PRIPROT, SECPROT,
and COMPROT operand settings are fixed by the SNA architecture
to support SNA type-2 logical units. The RUSIZES operand
specifies the maximum length of data that the primary logical unit
(PLU) and the secondary logical unit (SLU) can send. These first
two hexadecimal digits define the size for the SLU; the second two
hexadecimal digits define the size for the PLU. The actual sizes
designated by a setting of RUSIZES=X’87C7’ are 1024 bytes for the
SLU (’87’ = 8 times 2 to the seventh power) and 1536 bytes for the
PLU (’C7’ = 12 times 2 to the seventh power).
Finally, the PSERVIC operand defines the presentation services for
the logical unit. The PSERVIC setting must be as shown above for
the SLU sessions to properly function as SNA type-2 logical units.
The values are defined in the section on BIND command session
parameters in IBM’s 3174 Subsystem Control Unit Functional
Description.
If you decide to use the sample logon mode table, LMRKMTB, you
must assemble it to some library that you have concatenated to
SYS1.VTAMLIB in your VTAM startup procedure.
If you define your own logon mode table or use LMRKMTB, you
must supply the name of the logon mode table by adding the
MODTAB option to your APPL macro. You also must change
“dlogmod” in your SLU definitions to reflect the correct
LOGMODE entry. The following example shows two SLU
definitions in member SAMPLE. TMDB001 uses IBM default
parameters provided by SNX32702; TMDB002 uses the parameters
specified by the SLUTYPE2 entry in LMRKMTB.
SAMPLE VBUILD TYPE=APPL
TMDB001 APPL AUTH=(ACQ,PASS,VPACE),VPACING=5,EAS=1,DLOGMOD=SNX32702
TMDB002 APPL AUTH=(ACQ,PASS,VPACE),MODTAB=LMRKMTB,VPACING=5,EAS=1,
DLOGMOD=SLUTYPE2
Chapter 3: Landmark Product Communication Setting Up Landmark Product Communication
The Monitor for MVS 2.0 3-7
System Administrator’s Guide