Visara LINCS Features - Manual (Page 54)

44
LINCS Features
707021-001
• One host attached to an SDLC/SNA line
• Two logical host circuits attached to a BSC line
• One host attached to an X.25/SNA line
• One host attached to a Token Ring
• One host attached through Ethernet through a LINCS gateway
• 128 devices
• 96 3270 devices and/or LAN terminals
• 32 ASCII devices
Line 0 and Line 1 share an SCC board that has two-connector capability. X.25 uses an additional
SCC board and must be the only line on the board. A TRC provides access to the Token Ring
LAN. LINCS is operating as a gateway from Host A to the workstations on the ring. LINCS
also functions as a downstream node from Host F on the ring.
Extended LU Support
LINCS supports up to 4048 (3270) LUs simultaneously. The maximum LU count is calculated
as 253 LUs per host circuit on 16 host circuits. LUs can be assigned to TN3270 Clients, IPX
SNA Clients, LU to PU mapped DSPUs, CUT Devices, and DFT devices in any combination.
Configuration - 3270 LUs may be defined on any of the following Configuration panels:
• 3270 Host Classes define LUs to be members of classes. Note that 3270 Host Classes are
required to define LUs that will be used by IPX SNA Clients.
• LU to PU Mapping Profiles specify LUs or classes to be used by DSPUs using the LU to
PU Mapping feature.
• TN3270 Client Definitions specify LUs or classes to be used by TN3270 Clients.
• The Device Profiles and/or Device Profile Assignments panels specify LUs or classes to be
used by CUT and DFT devices.
Feature memory may be required, depending upon the number of LUs which are defined.
Refer to the Feature Memory utility in the Configuration and Central Control document for
more information.
SNA Alerts
The SNA Alert feature is available on all SNA host circuits. LINCS generates alert messages
that can be viewed on NetView’s hardware monitor component. NetView or NPDA Version 3,
Release 1 or later is required at the host.
If the SNA Alert feature is enabled, unsolicited Alert messages will be sent to the host which
contain problem determination information about events or errors that have occurred within
the LINCS node. The messages may also be user-defined if the Operator Messages are allowed
in the configuration.
The following types of unsolicited Alert messages will be sent to the host:
• Machine checks (2nn, 3nn, 6nn event codes)
• Program checks (4nn, 7nn event codes)
• Communication checks (5nn event codes)