
Across the Boards
Communications Device Drivers
Section 5 - General Configuration and Usage Information
Page 206
cfSOFTWARE Confidential,
2000
5.16 LU6.2 Configuration (continued)
Sample major node “PC001001”:
**P/390 VM****************************************PC001001/SYS4**
3172 (AWS3172) DEVICES (280) 06/02/98
*****************************************************************
09 TOKENRING STATIONS -- IDNUM=01001
LU 6.2 Node for PC
*****************************************************************
********
SYS4PC01 VBUILD TYPE=SWNET
********
PC001001 PU ADDR=C1 ***REVIEW***
IDBLK=05D ***REVIEW***
IDNUM=01001 ***REVIEW***
CONNTYPE=APPN
CPCP=YES
DYNLU=YES
LANSW=YES
LANSDWDW=(1,) ***REVIEW***
SAPADDR=4 ***REVIEW***
PUTYPE=2
MAXDATA=1456 ***REVIEW***
USSTAB=USSRPCS ***REVIEW***
DLOGMOD=HTPCMD2E ***REVIEW***
MODETAB=KGNMODE ***REVIEW***
*****************************************************************
NOTES
:
(1) You may prefer to code CPNAME instead of IDBLK/IDNUM
(2) The names on the VBUILD and PU statements are arbitrary and should meet your installation’s
standards.
(3) The items marked “
REVIEW
” should be altered to match your network requirements.
(4) Most LU6.2 connections will use modes #INTER or #BATCH. Ensure that the MODETAB
selected for the PU contains these modes as well as a definition for mode SVASVCMG (these
should be present in the IBM default table, usually named IESINCLM).
(5) Each PC does not have to be defined in its own major node, as many “PU” definitions as desired
may be placed in one major node. It is, however, usually desirable to limit the size of a major node
- a major node definition cannot be changed without inactivating the entire node. Limiting the
scope of a major node facilitates changing and debugging network definitions.
Once the new major node is defined, it can be activated. Once testing is completed it may be desirable to add
the new major node to the VTAM autostart list.
Comentários a estes Manuais