VTAM handles network communications for MVS for direct VTAM and SNA gateway configurations. The VTAM programmer creates a mode table entry and a major node definition in VTAM for the StarSQL connection.
Consult your VTAM documentation for detailed instructions on configuring VTAM.
If you are using direct TCP/IP to connect to the host, this topic is not applicable.
The logmode table entry contains information governing how conversations take place in VTAM. It defines pacing, RU sizes and COS (class of service parameters).The mode entry can be placed in any mode table under VTAM — the default mode table or the one used in the APPL statement (see APPL Statement below) for DB2's LU definition.
One of the most important entries in the logmode table is the PSERVIC field, which identifies the LU traffic protocols. Set the value of PSERVIC value as follows:
If you are using an independent LU, set PSERVIC=X'060200000000000000002F00'.
If you are using dependent LUs, set PSERVIC=X'060200000000000000002C00'.
The LU dependent/independent status affects the value of the PSERVIC setting in the mode table entry. In general, independent LUs are preferable, since ODBC applications often require more than the one connection permitted by dependent LUs.
Record the LOGMODE name. In the example below the LOGMODE is LU62STAR. You will need to use the same name for DLOGMODE in the major node definition and again for SNA configuration.
This is an example of a mode table entry with an independent LU:
LU62STAR MODEENT LOGMODE=LU62STAR,
FMPROF=X'13',
TSPROF=X'07',
PRIPROT=X'B0',
SECPROT=X'B0',
COMPROT=X'50A1',
RUSIZES=X'8989',
TYPE=0,
PSNDPAC=X'03',
SRVCPAC=X'03',
SSNDPAC=X'02',
PSERVIC=X'060200000000000000002F00'
This is an example of a mode table entry with a dependent LU:
LU62STAR MODEENT LOGMODE=MLU62A,
FMPROF=X'13',
TSPROF=X'07',
PRIPROT=X'B0',
SECPROT=X'B0',
COMPROT=X'50A1',
RUSIZES=X'8989',
TYPE=0,
PSNDPAC=X'03',
SRVCPAC=X'03',
SSNDPAC=X'02',
PSERVIC=X'060200000000000000002C00'
The VTAM programmer creates a major node definition for the connection to the DB2/ MVS host from the desktop. You can use a switched, non-switched, or channel attach major node. Switched major nodes are most commonly used with StarSQL.
In the major node definition, the DLOGMOD must match mode table entry LOGMODE.
Record these major node configuration values: PU name, IDBLK, IDNUM, CPNAME, LU, DLOGMODE. You will need them later for SNA configuration.
This is an example of a major node definition with an independent LU:
STAR2 PU ADDR=02,
IDBLK=05D,
IDNUM=10092,
CPNAME=PC0IYG01,
DLOGMOD=LU62STAR,
MODETAB=MODELU62,
SSCPFM=USSSCS,
PUTYPE=2,
MAXDATA=521, MAXPATH=1, PASSLIM=4,
DISCNT-NO,
ANS=CONT,
PACING=0INDLOCAL LU LOCADDR=0, PACING=0, VPACING=0
This is an example of the configuration of a PU with dependent LUs:
STAR1 PU ADDR=01,
IDBLK=05D,
IDNUM=10092
SSCPFM=USSSCS,
ISTATUS=ACTI
MAXDATA=521
MAXOUT=7
PASSLIM=15,
DLOGMOD=D4C32782
MODETAB=ISTINCLM,
IRETRY=NO
RETRIES=(,4,3),
PUTYPE=2,
VPACING=0LOCALLU1 LU LOCADDR=2
USSTAB=USSTAB01,
DLOGMOD=MLU62A,
ID=LU1
MODETAB=MTSNALOCALLU2 LU LOCADDR=3
USSTAB=USSTAB01,
DLOGMOD=MLU62A,
ID=LU2
MODETAB=MTSNALOCALLU3 LU LOCADDR=4
USSTAB=USSTAB01,
DLOGMOD=MLU62A,
ID=LU3
MODETAB=MTSNALOCALLU4 LU LOCADDR=5
USSTAB=USSTAB01,
DLOGMOD=MLU62A,
ID=LU4
MODETAB=MTSNA