Visara LINCS Configuration - Manual (Page 58)

40
LINCS Configuration
707023-003
Steps in defining UCW/IOCP Definitions
When you set up the UCP/IOCP definition for a Local connection, you should specify only
one UCW/IOCP definition for each channel interface For example, if you are installing
LINCS with multiple channel addresses configured, do not define a separate UCW/IOCP
definition for each channel address; specify only one definition per channel interface. Two
UCW/IOCP definitions would be required for a dual channel LINCS node; one per channel
interface. Specifying multiple UCW/IOCP definitions for a single channel interface will
cause X-CLOCK hangs.
The only exception to the above statement is when configuring for Extended Non-SNA support.
With Extended Non-SNA, a separate UCW/IOCP definition must be defined for each group of
32 addresses. The first UCW/IOCP definition must be defined to handle the first 32 addresses.
A subsequent UCW/IOCP definition must be defined for each additional group of 32 addresses.
For example, if configuring 80 non-SNA device sessions, the first 32 addresses must always
be defined on the first UCW/IOCP definition, second 32 in the second definition, and the last
16 in the third definition.
Care should be taken to insure that all addresses defined within the LINCS configuration, that
will have real devices associated with them, also have a corresponding definition within the
host gen. Failure to do so, may result in LINCS generating an Asynchronous Status for a
device address not defined within the host gen. This may cause errors and poor response
times.
It is also not a good idea to have addresses defined in the host gen, that do not have
corresponding configuration on the LINCS platform. When the host attempts to activate the
non-existent device session, an error will be reported back to the host.
Line Options/HSC
Valid protocol selections for HSC lines are:
• None (default), which disables that line.
• SDLC - half- and full-duplex
• SDLC/DAP - half- and full-duplex
• Frame Relay
• X.25
The HSC boards have up to four available lines per board. They require communication
cables, consisting of an HSC Adapter cable and PLIM.
HSC Cabling
PLIM stands for Physical Layer Interface Module. It is the part of the cabling for the HSC
board that determines what type of connectors are available (RS 232/V.35 or X.21), and
whether the connector will act as a DTE or a DCE.
The HSC board assembly includes an HSC Adapter Cable (HAC). One end of the HAC