Filter
Top Products
Multiserver 5000
160
Enter the channel to be tested. Press <cr>.
These tests are performed only on async ports from
the user terminal. The menu options are the same
as the Async Channel Loopback in Command
Mode. Section 12.3, Async Channel Loopback in
Command Mode, explains each of these tests.
NOTE: If you request a remote test (either echo or
fox), the terminal does not require
connection to a remote port (unlike the
remote tests for the Async Channel
Loopback in the Command Mode).
ASYNC CHANNEL OUTPUT
This option permits the Command Facility terminal
to place an async port on the local node (local
Multiserver and attached feeder muxes) into a test
mode. This option is useful for testing unattended
terminals or devices that do not have a keyboard,
such as printers. See Figure 12-3.
NOTE: While under test, this port may be called or
force-connected via the Command Facility.
No connections will be made while the port
is testing (even though the calling side
receives the CONNECTED message). When
the test is terminated, the port will be
connected.
When accessing this test, you will be prompted:
Enter the channel to be tested. Press <cr>. The
following menu appears:
LOCAL
MULTISERVER
FOX
1 2
LOCAL
TERMINAL
REMOTE
TERMINAL
COMMAND
FACILITY
TERMINAL DATA
INPUT HERE.
MODEM MODEM
FEEDER MUX
FOX
1
2
LEGEND:
FOX TEST (ONLY ONE LOCAL OR REMOTE NODE/CHANNEL MAY BE SELECTED).
INPUT MESSAGE (ONLY ONE LOCAL OR REMOTE NODE/CHANNEL MAY BE SELECTED).
INPUT DATA APPEARS ON COMMAND FACILITY SCREEN.
FOX MESSAGE GENERATOR
THE REMOTE TEST OUTPUTS TO A REMOTE TERMINAL.
THE LOCAL TEST OUTPUTS TO THE LOCAL TERMINAL.
Figure 12-3. Async Channel Output.
ENTER NODE-ID/CHANNEL #
(^X TO ABORT):
ENTER CHANNEL# (^X TO ABORT):