Black Box 5000 manual Matching Capability for Asynchronous Channels

Multiserver 5000

Note: The wild card (*) can be used to access a range of ports. To access any async port in the Multiserver identified by the name NEW_YORK, you would type the following:

NEW_YORK/*

2.The CLASS PASSWORD prompt will appear on the screen. If the destination port has been configured as part of a class, enter the class password.

3.If the port is not available, the screen will display one of the following configurable dialog messages:

Busy. The port is already connected to another user. Try again.

No Answer. There is no answer from the destination port. Causes include:

•Remote port did not respond to connection protocol.

•There was no response within the call time out period, although the port is known by the local Multiserver.

Unavailable. The resource exists, but is not in service (not operational), or receive inhibit is enabled.

Unassigned. The node, class, or port is unknown in the network. It could also mean that you have entered a class password incorrectly.

4.A connection message will appear on the screen when the connection is complete across the link.

Note: Matrix switching can be disabled on a per-channel basis.

To disconnect from a matrix connection, press the <break> key three times within six seconds. When the connection is broken, the disconnect message will be displayed on the screen of the calling port.

10.6Matching Capability for Asynchronous Channels

Feature matching automatically selects and sets the minimum feature set for connecting async ports during switching operations. The Multiserver does not match features in force-connected async channels.

Three features are automatically converted for asynchronous channels:

•Speed. Called and calling ports do not need to have the same speeds unless unbalanced rates are set to OFF. The Multiserver will flow-control the faster port to prevent overrunning the slower port.

•Flow Control/Buffer Control. Ports with different flow-control and buffer-control mechanisms will be converted through the Multiserver.

Note: Ports using no flow control connecting with those using character (DC1/DC3, DC2/DC4, and so forth) flow control may have problems if they use the complete ASCII code set, since the flow-control characters will not be stripped out of the data stream.

•Parity. Even, odd, mark, and space will be converted automatically at the receiving Multiserver to match the required parity. See Section 9.3, Asynchronous Channels, for configuration specifics. Parity conversion works on force-connected channels.

114