SNA Link/iX Node Managers Guide (30291-90009)
Table Of Contents
- 1 SNA Links Overview
- 2 SNA Node and Link Configuration
- 3 Logging Configuration
- 4 SNA Node Startup and Shutdown
- 5 SNA Link Troubleshooting
- 6 MPE Commands
- 7 SNA Link Installation Information
- A Messages
- SDLC Link Startup Error Messages
- SDLC Link Driver Error Messages
- SNACONTROL Error Messages
- SNA Transport Error Messages
- SNA Transport Logging Messages
- SDLC Link Shutdown Error Messages
- X.25 Link Failure Error Codes
- X.25 Link Module Configurator Error Codes
- X.25 Link QLLC Internal Error Codes
- NetView Alerts Error Messages
- Network Dump Manager Error Messages
- LAN Error Messages
- B Netview Alerts

Chapter 2 55
SNA Node and Link Configuration
Configuring the SNA Node and Link
• SNA/Token Ring: The IDBLK macro
must match this field; see Table 2-7.
AS/400 Configuration: The
EXCHID
parameter in the controller description
is required, and must match the entire
exchange identifier (this field combined
with ID NUM); see Table 2-8 and Table
2-10.
ID NUM Five hexadecimal digits that are
appended to ID BLK (see above) to form
the exchange identifier used with
exchange identification (XID) requests.
This composite identifier must be
unique within the SNA network.
NOTE
For communication with an IBM host, this parameter (
ID NUM
) is
ignored for nonswitched lines. For communication with an IBM AS/400,
this parameter is required for both switched
and
nonswitched lines.
Range: 00001-FFFFF (hexadecimal)
Default: FFFFF
Host Configuration:
• SNA/SDLC: The IDNUM operand of
the PU macro must match this field;
see Table 2-1.
• SNA/X.25(SVC): TheIDNUM operand
of the PU macro in the VTAM
switched major node must match
this field; see Table 2-3.
• SNA/Token Ring: The IDNUM
operand of the PU macro must match
this field; see Table 2-7.
AS/400 Configuration: The
EXCHID
parameter in the controller description
is required, and must match the entire
exchange identifier (this field combined
with ID BLK); see Table 2-8 and Table
2-10.
Local Control Point Name
(Token ring only) Required for APPC over token ring
link. The name by which the HP 3000 node is known to
the remote system.