BNS 19
Data Networking Products
SYNC8 Module Reference
255-100-212
Issue 2
 Copyright 1997 Lucent Technologies
All Rights Reserved
Printed in USA
Datakit, Merlin, and StarKeeper are registered trademarks of Lucent Technologies Inc.
Dataphone is a registered trademark of AT&T.
IBM is a registered trademark of International Business Machines, Inc.
The information in this document is subject to change without notice.
Lucent Technologies assumes no responsibility for any errors that may appear in this document.
________________
Contents
Preface
Document Organization
Related Documentation
SYNC8 Overview
Physical Description
Features
Support
SYNC8 Installation
Switch Settings for I/O Boards
Inserting and Removing the I/O Board
Inserting and Removing the SYNC8
SYNC8 Cabling
Cabling SYNC8 Directly to Host, Cluster Controller, or V.35 DTE Device
Cabling SYNC8 to Host, Cluster Controller, or DTE Device via 110
Patch Panel
Cabling SYNC8 to Host, Cluster Controller, or V.35 DTE Device via
Modem, DSU, or FOM
Cabling SYNC8 to R-VDM via VDM Cabinet
Cabling SYNC8 to R-VDM via VDM Stand-Alone Shelf
Cabling SYNC8 to R-VDM via Model 045CS VDM
Cabling SYNC8 to R-VDM via D4 Channel Bank and VDM Cabinet
Cabling SYNC8 to R-VDM via D4 Channel Bank and VDM Stand-Alone
Shelf
Cabling SYNC8 to R-VDM via D4 Channel Bank and Model 045CS
VDM
SYNC8 Administration
StarKeeper II NMS Administration
Command Set
Parameter Considerations
Administrative Procedures
Reports
Data Networking Products SYNC8 Module Reference, Issue 2
ix
ix
x
1-1
1-3
1-3
1-6
2-1
2-4
2-4
2-5
3-1
3-5
3-6
3-7
3-9
3-11
3-12
3-13
3-15
3-16
4-1
4-4
4-4
4-5
4-9
4-14
iii
________________
SYNC8 Troubleshooting
Problem Indicators
Problem Areas
SYNC8 Diagnostics
5-1
5-3
5-4
5-8
SYNC8 Commands
6-1
Appendix A. SYNC8 Database Entry Forms
A-1
Appendix B. Host and Terminal Interfaces
B-1
Appendix C. Multipoint Control Unit Configuration
Using AT&T Dataphone II Modems
Dataphone II 2048C Modem Options
Dataphone II 2048A Modem Options
Index
iv
C-1
C-2
C-2
I-1
Data Networking Products SYNC8 Module Reference, Issue 2
________________
Figures
1-1.
Typical SYNC8 Network
1-5
3-1.
SYNC8 I/O Board Interfaces
3-4
C-1. Dataphone II 2048 Modem Configuration
Data Networking Products SYNC8 Module Reference, Issue 2
C-1
v
________________
Tables
2-1.
2-2.
SYNC8 and I/O Board Correspondence
Switch Settings for I/O Boards AWJ17 and AWJ18
2-3
2-4
3-1.
3-2.
Number of Ports Provided by SYNC8 I/O Board Interface
Ordering Information: Host, Cluster Controller, or V.35 DTE Device
Connections
Ordering Information: Host, Cluster Controller, or DTE Device via 110
Patch Panel Connections
Ordering Information: Host, Cluster Controller, or DTE Device via
Modem, DSU or FOM Connections
Ordering Information: R-VDM via VDM Cabinet Connections
Ordering Information: R-VDM via VDM Stand-Alone Shelf
Connections
Ordering Information: R-VDM via VDM Model 045CS VDM
Connections
Ordering Information: R-VDM via D4 Channel Bank and VDM Cabinet
Connections
Ordering Information: R-VDM via D4 Channel Bank and VDM StandAlone Shelf Connections
Ordering Information: R-VDM via D4 Channel Bank and Model
045CS VDM Connections
3-4
3-17
4-1.
4-2.
4-3.
SYNC8 BSC3270 Commands
Logoff Commands
Available Reports for SYNC8
4-5
4-5
4-14
5-1.
5-2.
Command Output
SYNC8 Problems
3-3.
3-4.
3-5.
3-6.
3-7.
3-8.
3-9.
3-10.
B-1. RS-232 Leads Supported by the SYNC8 Module (DTE)
B-2. RS-232 Leads Supported by the SYNC8 Module (DCE)
B-3. V.35 Leads Supported by the SYNC8 Module (DTE)
vi
Data Networking Products SYNC8 Module Reference, Issue 2
3-6
3-7
3-9
3-10
3-12
3-13
3-14
3-16
5-4
5-5
B-1
B-2
B-3
________________
Procedures
2-1.
2-2.
2-3.
2-4.
Inserting the I/O Board
Removing the I/O Board
Inserting the SYNC8
Removing the SYNC8
4-1.
4-2.
4-3.
4-4.
4-5.
4-6.
Entering a SYNC8 (bsc3270) Logoff Sequence
Entering a SYNC8 in the Database
Making Minor Database Changes
Making Extensive Database Changes
Moving Database Information to Another Module Address
Copying Database Information to Another Module Address
4-9
4-10
4-11
4-11
4-12
4-13
5-1.
5-2.
5-3.
5-4.
5-5.
5-6.
5-7.
5-8.
5-9.
Correcting SYNC8 Download Failure
Correcting SYNC8 Link Failure
Correcting SYNC8 Timing Problems
Running the Internal Port Test
Running the External Port Test
Running the Local Modem Test
Running the Remote Modem Test
Running the SYNC8 Off-line Test
Running the SYNC8 Off-line Test with VDM
5-6
5-6
5-8
5-9
5-9
5-10
5-10
5-11
5-12
Data Networking Products SYNC8 Module Reference, Issue 2
2-4
2-5
2-5
2-5
vii
________________
Preface
The Data Networking Products SYNC8 Module Reference provides the information needed to
install, configure, and administer the Synchronous Module 8-port (SYNC8) modules. Procedures
for routine operations, maintenance, and troubleshooting are also included.
Document Organization
The SYNC8 Module Reference is divided into six chapters that explain all aspects of module
hardware, software, and troubleshooting:
SYNC8 Overview
includes a physical description of a SYNC8 and an overview of
SYNC8 features.
SYNC8 Installation
explains input/output (I/O) board and module installation and
removal.
SYNC8 Cabling
furnishes reference information regarding the cables and adapters
required to connect compatible devices and equipment to a
SYNC8.
SYNC8 Administration
discusses the implications of choosing certain options and
provides procedures for initial and routine administration.
SYNC8 Troubleshooting provides the information and procedures needed to troubleshoot a
SYNC8.
SYNC8 Commands
provides a detailed reference of the commands needed to
administer, control, and maintain a SYNC8. Included are
command syntax sections, explanations of parameter options,
input/output examples, report field definitions, and system
responses. This chapter also includes the same coverage for the
logoff commands.
In addition, three appendixes provide database entry forms, Electronic Industries Association
(EIA) lead states, and Dataphone II 2048 modem configurations. Tables of contents and an
index help to locate information quickly.
Data Networking Products SYNC8 Module Reference, Issue 2
ix
________________
Preface
Related Documentation
Documents required for use with this reference guide include the following:
Data Networking Products Planning Guide
BNS-2000 Node Reference
Data Networking Multipurpose Concentrator Reference—if the SYNC8 is installed in a
BNS-2000 Multipurpose Concentrator (MPC)
Data Networking Products Messages Reference
Data Networking Products Terminology lists and defines many technical terms found within this
document. In addition, vendor documents might be necessary for end devices connected to this
and other modules.
x
Data Networking Products SYNC8 Module Reference, Issue 2
________________
SYNC8 Overview
Physical Description
1-3
Features
1-3
1-3
1-4
1-5
1-5
1-6
Diagnostic Capabilities
Switched Synchronous Service
Throughput
Configurable Options
Integrated Voice Data Modem Interface
Support
1-6
Data Networking Products SYNC8 Module Reference, Issue 2
________________
SYNC8 Overview
The SYNC8 (Synchronous Module 8-port) is an 8-port interface module for switched binary
synchronous services for devices operating under the 3270 Bisync protocols. The SYNC8 is also
known as the Binary Synchronous Communication 3270 (BSC3270) Module. It uses
downloadable software and can be used with four different I/O distribution boards that permit
configuration of the module as either DTE or DCE. The SYNC8 reside in a node or BNS-2000
MPC. Billing information can be collected for the SYNC8 ports.
Physical Description
The SYNC8 (MC1D089A1) is a removable circuit pack that slides into the card guides of a
BNS-2000 VCS, BNS-1000, BNS-2000 Series M1 Shelf, or BNS-2000 MPC, making contact
with a pin field on the front side of the node backplane. The SYNC8 functions in conjunction
with an input/output (I/O) board that plugs into the rear of the backplane. The I/O board
provides two receptacles for transmit and receive leads.
The module faceplate contains three light-emitting diodes (LEDs), a reset push button, a threestate mode switch, and a latch. When pressed, the reset push button reinitializes the module and
clears the connections. The Mode switch states (enable, diagnose, and disable) plus the green,
yellow, and red LEDs indicate the module’s current mode of operation and its service state. The
latch is used to remove or insert the module, and to secure it in place.
In addition to the LEDs on the module faceplate, the I/O board has two red LEDs that indicate
whether the module is in loopback mode for diagnostic testing. The I/O board also has an SW1
switch that toggles board operation from loopback mode (up position) to the standard operating
mode (down position).
Features
The SYNC8 offers an array of features—such as diagnostic capabilities, BSC3270 protocol
support for switched synchronous services, and options that are configurable via the bsc3270
command set.
Diagnostic Capabilities
The module’s diagnostic capabilities include hardware logic tests and local and remote loopback
tests. The hardware logic tests verify the module command decoder; the loopback tests verify
the integrity of the transmission path from the SYNC8 to its I/O board and cables.
Data Networking Products SYNC8 Module Reference, Issue 2
1-3
________________
SYNC8 Overview
Switched Synchronous Service
The SYNC8 resides in a node or BNS-2000 MPC and provides switched synchronous service
supporting the Bisynchronous 3270 terminal protocol. By emulating bisynchronous hosts, the
module provides connections for IBM 3270 and comparable terminals and their related control
units (CUs); and by emulating bisynchronous terminal lines, the module provides connections to
IBM hosts. When the module is configured to communicate with terminals and CUs it is called a
Bisynchronous Terminal Interface Module (BTIM); When the module is configured to
communicate with a host it is called a Bisynchronous Host Interface Module (BHIM). See
below:
BTIM
interfaces with the cluster controllers
performs the function of the front end processor (FEP)
originates all polls and selects
contains physical terminal database definitions (which should match the physical cluster
controllers and physcial terminals and printers on the line. An exception is that a basic
termial with a screen size of 1920 may be entered as a printer.)
BHIM
interfaces to the FEP
performs the function of cluster controllers
responds to all polls and selects locally Polls and selects are not passed through to the BTIM.
contains virtual terminal database definitions (which must match the FEP gen).
1-4
Data Networking Products SYNC8 Module Reference, Issue 2
________________
SYNC8 Overview
Overview
Mainframe
1
Mainframe
2
Mainframe
3
FEP
1
FEP
2
BHIM
Host Module
CU 1
CU 2
CU 3
CU 4
CU 5
CU 6
CU 7
CU 6
CU 7
CU 8
BTIM
Terminal Module
FEP
CU 1
FIGURE 1-1.
CU 2
CU 3
CU 4
CU 5
Typical SYNC8 Network
Throughput
The SYNC8 supports line speeds of 19.2 Kbps on RS-232-C ports and up to 64 Kbps on V.35
ports.
Configurable Options
The enter bsc3270 command allows you to specify module, port, control unit, and terminal
options. Special considerations regarding a connected voice/data multiplexer (VDM) are also
specified.
Data Networking Products SYNC8 Module Reference, Issue 2
1-5
________________
SYNC8 Overview
Integrated Voice Data Modem Interface
Integrated voice data modems, such as the AT&T Voice Data Multiplexer (VDM) and hard-wired
modems have permanently connected data paths from the remote terminal or host. No dialing is
required. For these types of modems, use the node terminal or host interface required by the
device connected to the remote modem. The node will view the modem connection as a hardwired connection to the DTE.
When attaching integrated voice data modems to the node, the node port assumes the DTE role
while the VDM assumes the DCE role. Even though the node views the interface as a hard-wired
device, it still requires the same cabling and connectors as those used for a modem.
NOTE:
The node VDMs connect through TY12, SAM, SYNC8, and TSM8 modules. The
diagnostics for the VDMs are supported through these modules.
The EIA flow control option for TY12 and SAM modules cannot be used with standard
integrated voice data modems.
Support
The Switched Bisynchronous service supports all multipoint specifications in the IBM document
General Information Binary Synchronous Communications, IBM GA27-3004 with the following
exceptions:
System Request and Test Request Key are not supported.
Six Bit Transcode is not supported.
BTIM does not support conversational mode; however, BHIM does support conversational
mode.
The service supports all 3270 compatible devices. It also supports all 3270 commands except
3270 Copy command
3270 Read Modified command
3270 Read Modified ALL command
NOTE:
1-6
The BHIM responds to the above commands with an EOT.
Data Networking Products SYNC8 Module Reference, Issue 2
________________
SYNC8 Installation
Switch Settings for I/O Boards
2-4
Inserting and Removing the I/O Board
2-4
Inserting and Removing the SYNC8
2-5
Data Networking Products SYNC8 Module Reference, Issue 2
________________
SYNC8 Installation
SYNC8 installation consists of a few simple precautions and procedures, as follows:
Ensure protection from electromagnetic interference (EMI, see inside front cover) and
electrostatic discharge (ESD). Wear an ESD wrist strap to prevent module damage; see the
BNS-2000 Node Reference for grounding locations and other details.
Verify that you have the correct I/O board for your application; see Table 2-1.

TABLE
2-1. SYNC8 and I/O Board Correspondence
_____________________________________________________________________________
 Module Type
 Designation
 I/O Board
 Comments

_____________________________________________________________________________




 SYNC8
 MC1D089A1
 AWJ5
 1 V.35 DTE or 3 RS-232-C DCE*








 AWJ6
 1 V.35 DTE or 3 RS-232-C DTE*



 AWJ17
 8 RS-232-C DTE



 AWJ18
 8 RS-232-C DCE

_____________________________________________________________________________




∗ Use the bottom connector for the V.35 option.
Ensure that the correct slot is designated for the module. See the Data Networking Products
Planning Guide, the BNS-2000 Node Reference, and the Data Networking Products
Multipurpose Concentrator Reference for module placement in the node and the BNS-2000
MPC.
CAUTION:
To prevent damage to module circuitry, always insert the I/O board before
inserting its corresponding module. Never remove the I/O board before
removing the module.
Verify that the SW1 toggle switch on the I/O board is in the down position.
Check the rocker switch settings on the I/O board; see the section that follows.
Insert the I/O board; see Table 2-1 and Procedure 2-1. Inserting the I/O Board.
Insert the SYNC8; see the section that follows.
Cable the I/O board ports to support external devices; see Table 2-1 and SYNC8 Cabling.
Examine the LEDs on the I/O board. If the LEDs are lit, refer to SYNC8 Troubleshooting.
The following sections give more detail on inserting the I/O board and the SYNC8, and directions
for removing the SYNC8 module and its I/O board.
Data Networking Products SYNC8 Module Reference, Issue 2
2-3
________________
SYNC8 Installation
Switch Settings for I/O Boards
The directions in this section apply when you are holding the I/O board with the backplane
connector to your left, the interface connectors to your right, and the switches facing you. A slide
switch is moved in the specified direction. A rocker switch is pushed in on the specified side.
NOTE:
I/O boards AWJ5 and AWJ6 do not have rocker/slide switches.

TABLE
2-2. Switch Settings for I/O Boards AWJ17 and AWJ18
_____________________________________________________________________________
 Switch
 Function
 Default


Comments
_____________________________________________________________________________





 U: Connects Pin 205 to ground (magic enabled) 
 S1.2
 PERENA
Down

 D: Open circuit (magic disabled)

_____________________________________________________________________________






Down

 U: Connects Pin 106 to Pin 105 (magic enabled) 
 S1.3
 BRESET


 D: Open circuit (magic disabled)

_____________________________________________________________________________
Inserting and Removing the I/O Board
The I/O board plugs into the rear of the node shelf backplane or BNS-2000 MPC; it is held in
place by shrouds on the backplane pin field and secured with two screws. Always insert the I/O
board before inserting its corresponding SYNC8.
Remove the I/O board only for relocation, replacement, or part number confirmation. Never
remove the I/O board before removing its corresponding SYNC8.

PROCEDURE
2-1. Inserting the I/O Board
1. Verify that a module board does not reside in the corresponding slot.
2. Align the I/O board’s backplane connector with the backplane pin field at the rear of the
cabinet, and align the screws with the screw holes. Slip the backplane connector onto the
pins.
The board should seat easily. If seating is difficult, the board might be canted or some pins
might be bent.
3. Insert the screws and tighten them securely.
2-4
Data Networking Products SYNC8 Module Reference, Issue 2
________________
SYNC8 Installation
PROCEDURE 2-2.
Removing the I/O Board
1. Unseat the SYNC8 board; refer to Procedure 2-4. Removing the SYNC8.
2. Disconnect all cabling to I/O board ports, labeling the cable ends if appropriate.
3. Remove the screws holding the I/O board in place.
4. Rock the board carefully as you pull it out.
Inserting and Removing the SYNC8
The SYNC8 board (MC1D089A1) is inserted into a slot at the front of the cabinet. To prevent
damage to module circuitry if the node is powered up, insert the I/O board at the rear of the slot
before the SYNC8 board.
You can remove and replace the SYNC8 in an operating node without damaging the module itself
or without disrupting calls on other modules. Only calls to the SYNC8 are disrupted when the
module is removed.

PROCEDURE
2-3. Inserting the SYNC8
1. Confirm that the I/O board is installed and is residing in the appropriate slot.
2. Set the Mode switch on the module to DISABLE.
3. With the module latch extended, carefully push the module all the way into the slot. The
backplane pins will slip into the module receptacle.
4. Close the latch to lock the module into position.
5. Move the Mode switch on the module faceplate to ENABLE.

PROCEDURE
2-4. Removing the SYNC8
1. Verify that there are no existing calls/circuits made to this module.
2. If the Mode switch on the SYNC8 board is in the ENABLE position, move it to DISABLE to
take down all calls in progress on the SYNC8.
3. Open the latch on the module faceplate.
4. Pull the module straight out of the slot, using the latch as a handle.
Data Networking Products SYNC8 Module Reference, Issue 2
2-5
________________
SYNC8 Cabling
Shielding Requirements for Cabling
3-5
Cabling SYNC8 Directly to Host, Cluster Controller, or
V.35 DTE Device
3-5
Cabling SYNC8 to Host, Cluster Controller, or DTE
Device via 110 Patch Panel
3-6
Cabling SYNC8 to Host, Cluster Controller, or V.35 DTE
Device via Modem, DSU, or FOM
3-7
Cabling SYNC8 to R-VDM via VDM Cabinet
3-9
Cabling SYNC8 to R-VDM via VDM Stand-Alone Shelf
3-11
Cabling SYNC8 to R-VDM via Model 045CS VDM
3-12
Cabling SYNC8 to R-VDM via D4 Channel Bank and
VDM Cabinet
3-13
Cabling SYNC8 to R-VDM via D4 Channel Bank and
VDM Stand-Alone Shelf
3-15
Cabling SYNC8 to R-VDM via D4 Channel Bank and
Model 045CS VDM
3-16
Data Networking Products SYNC8 Module Reference, Issue 2
________________
SYNC8 Cabling
The SYNC8 is an 8-port interface module for switched binary synchronous services for devices
operating under the 3270 Bisync protocols. The SYNC8 module can be cabled for low-speed
connections up to 19.2 Kbps, or for medium-speed connections from 48 to 64 Kbps, depending
on the I/O board used.
Low-speed connections use the RS-232-C interfaces on the I/O boards.
Medium-speed connections use the CCITT V.35 interface available on certain I/O boards to
support speeds up to 64 Kbps via the V.35 interface.
The SYNC8 module consists of a MC1D089A1 main circuit pack and uses one of four available
I/O boards. By selecting the appropriate I/O board, the SYNC8 can be configured as DCE or
DTE using standard signaling. The following options are available:
An AWJ5 I/O board offers three DCE RS-232-C ports for lines operating at speeds up to 19.2
Kbps, and one DTE V.35 port for a line operating at a speed up to 64 Kbps. The I/O board
has two 50-pin connectors. The top 50-pin connector handles three DCE ports, while the
bottom connector handles one V.35 port.
An AWJ6 I/O board offers three DTE RS-232-C connections for lines operating at speeds up
to 19.2 Kbps, and one DTE V.35 connection for a line operating at a speed up to 64 Kbps.
The I/O board has two 50-pin connectors. The top 50-pin connector handles three DTE ports,
while the bottom connector handles one V.35 port.
An AWJ17 I/O board offers eight DTE RS-232-C ports for lines operating at speeds up to
19.2 Kbps. The I/O board has two 50-pin connectors; each connector handles four DTE ports.
An AWJ18 I/O board offers eight DCE RS-232-C ports for lines operating at speeds up to
19.2 Kbps. The I/O board has two 50-pin connectors; each connector handles four DCE ports.
Data Networking Products SYNC8 Module Reference, Issue 3
3-3
________________
SYNC8 Cabling
The following figure illustrates the SYNC8 I/O boards and their configurations.
AWJ5
AWJ6
AWJ17
AWJ18
I/O
Board
I/O
Board
I/O
Board
RS-232
I/O
Board
RS-232
V.35
DTE(1)
FIGURE 3-1.
RS-232
DCE(3)
V.35
DTE(1)
RS-232
DTE(3)
DTE(4)
DTE(4)
DCE(4)
DCE(4)
SYNC8 I/O Board Interfaces
Table 3-1 lists the I/O boards and the number of ports provided by the SYNC8 interface module.

TABLE
3-1. Number of Ports Provided by SYNC8 I/O Board Interface
_____________________________________________________________________________


______________________________________________________________

Number of Ports Provided of Each Interface Type




V.35
RS-232-C
 I/O Board
______________________________________________________________




DTE
DTE
DCE


_____________________________________________________________________________








AWJ5
1
—
3
_____________________________________________________________________________




_____________________________________________________________________________


AWJ6
1
3
—







AWJ17
—
8
_____________________________________________________________________________






AWJ18
—
—
8
_____________________________________________________________________________



3-4
Data Networking Products SYNC8 Module Reference, Issue 3
________________
SYNC8 Cabling
Shielding Requirements for Cabling
The first 25 feet of data cabling connected to a node shelf or BNS-2000 MPC must be shielded to
meet Federal Communications Commission (FCC) electromagnetic interference (EMI)
requirements. If longer cable runs are needed for a given configuration, unshielded cables may be
used after the first 25 feet.
When Lucent Technologies cables and other components are specified, no other cables and
components can be used. Otherwise, Lucent Technologies is not liable for failure to meet FCC
regulations.
Cabling SYNC8 Directly to Host, Cluster Controller,
or V.35 DTE Device
Using one of the DCE I/O boards listed in Table 3-1, a DTE device can be directly connected to a
node shelf or BNS-2000 MPC as follows:
The SYNC8 module consists of an MC1D089A1 main circuit pack with an associated I/O
board as follows:
– AWJ5 (three RS-232-C DCE or one V.35 DTE)
– AWJ6 (three RS-232-C DTE or one V.35 DTE)
– AWJ17 (eight RS-232-C DTE)
– AWJ18 (eight RS-232-C DCE)
For RS-232-C connections, connect a B25FS-1MOD cable to the 50-pin connectors on the I/O
board.
NOTE:
If the AWJ5 or AWJ6 is being used, only Port J1 may be used for RS-232-C
connections.
Connect a SYNC4-F or SYNC4-M cable to the other end of the B25FS-1MOD as required.
These cables are identical except for the gender of the 25-pin connectors.
Each of the 25-pin connectors on the SYNC4-type cable may be connected directly to the end
device, or they may be extended using M25A and M25B cables.
For V.35 connections, a C25AS-MOD cable is connected to Port J2 of the AWJ5 or AWJ6
I/O board.
A modem eliminator/driver must then be used to connect directly to a V.35 DTE device.
Data Networking Products SYNC8 Module Reference, Issue 3
3-5
________________
SYNC8 Cabling
NOTE:
On the AWJ5 and AWJ6 I/O board, Port J2 may be used for V.35 or Port J1 may be
used for RS-232-C, however; both ports cannot be used at the same time.

TABLE
3-2. Ordering Information: Host, Cluster Controller, or V.35 DTE Device
Connections
_____________________________________________________________________________




Cable or
ED5P055-31
_____________________________________________________________________________



Adapter Name
Description
Group Number




B25A
50-pin 90-M
G(106), G(F)




50-pin 90-F
_____________________________________________________________________________







B25FS-1MOD
50-pin 180-M
G(262), G(C)




50-pin 90-M
_____________________________________________________________________________



SYNC4-F
50-pin 90-F
G(161), G(R)




_____________________________________________________________________________

4 25-pin-F






SYNC4-M
50-pin 90-F
G(160), G(R)




4 25-pin-M
_____________________________________________________________________________



M25A
25-pin-M
G(107), G(P)




_____________________________________________________________________________



25-pin-F




M25B
25-pin-M
G(108), G(P)




25-pin-M
_____________________________________________________________________________







C25AS-MOD
50-pin 180-M
G(202), G(C)
_____________________________________________________________________________



V.35-M
Cabling SYNC8 to Host, Cluster Controller,
or DTE Device via 110 Patch Panel
Using one of the DCE I/O boards listed in Table 3-1, a DTE device can be connected to a node
shelf or BNS-2000 MPC through a 110 patch panel, as follows:
The SYNC8 module consists of an MC1D089A1 main circuit pack with an associated I/O
board as follows:
– AWJ5 (three RS-232-C DCE or one V.35 DTE)
– AWJ6 (three RS-232-C DTE or one V.35 DTE)
– AWJ17 (eight RS-232-C DTE)
– AWJ18 (eight RS-232-C DCE)
3-6
Data Networking Products SYNC8 Module Reference, Issue 3
________________
SYNC8 Cabling
Attach a B25FS-1MOD cable to the appropriate 50-pin connector on the I/O board at the rear
of a node shelf or BNS-2000 MPC.
The other end of the B25FS-1MOD cable connects to the 110 patch panel.
A SYNC4-F or SYNC4-M cable, which splits into four RS-232-C legs, connects to the patch
panel. The 50-pin connector side of the SYNC4-type cable may be extended with a B25A
cable, if necessary.
The SYNC4-type cables may be connected directly to host computers, cluster controllers, or
other DTE devices. M25A or M25B cables may be used to extend the RS-232-C legs of the
SYNC4-type cables, if necessary.
If RS-232-C I/O ports are wired directly from the patch panel via 6-pair "D" wire, an M25B
cable can be used to connect to the DTE device.

TABLE
3-3. Ordering Information: Host, Cluster Controller, or DTE Device via 110
Patch Panel Connections
_____________________________________________________________________________




Cable or
ED5P055-31
_____________________________________________________________________________



Adapter Name
Description
Group Number




B25A
50-pin 90-M
G(106), G(F)




50-pin 90-F
_____________________________________________________________________________







B25FS-1MOD
50-pin 180-M
G(262), G(C)




50-pin 90-M
_____________________________________________________________________________



SYNC4-F
50-pin 90-F
G(161), G(R)




4 25-pin-F
_____________________________________________________________________________







SYNC4-M
50-pin 90-F
G(160), G(R)




4 25-pin-M
_____________________________________________________________________________



M25A
25-pin-M
G(107), G(P)




_____________________________________________________________________________



25-pin-F




M25B
25-pin-M
G(108), G(P)




25-pin-M
_____________________________________________________________________________



Cabling SYNC8 to Host, Cluster Controller, or V.35 DTE
Device via Modem, DSU, or FOM
Using one of the DTE I/O boards listed in Table 3-1, a DCE device (or other equipment with a
DCE interface) can be connected to a node shelf or BNS-2000 by a direct connection, as follows:
Data Networking Products SYNC8 Module Reference, Issue 3
3-7
________________
SYNC8 Cabling
The SYNC8 module consists of an MC1D089A1 main circuit pack with an associated I/O
board as follows:
– AWJ5 (three RS-232-C DCE or one V.35 DTE)
– AWJ6 (three RS-232-C DTE or one V.35 DTE)
– AWJ17 (eight RS-232-C DTE)
Attach a B25FS-1MOD shielded cable to the appropriate 50-pin connectors on the I/O board
at the rear of a node shelf or BNS-2000 MPC.
A SYNC4-type cable connects to the other end of the B25FS-1MOD cable to provide four
RS-232-C connections.
– Selection of the proper SYNC4-type cable depends on the gender of the RS-232-C
connector on the modem, subrate DSU, or FOM.
– The SYNC4-M cable provides four male connections.
– The SYNC4-F cable provides four female connections.
The SYNC4-type cable then connects directly to the modem, subrate DSU, or FOM. An
M25A or M25B cable may be used to extend the RS-232 connections, if necessary.
NOTE:
A subrate DSU is one with a speed of 19.2 Kbps or lower.
At the remote end modem, subrate DSU, or FOM, the final connection to a host computer,
cluster controller, or other DTE device will be made using an M25A or M25B cable, as
required.
For V.35 connections, a C25AS-MOD cable is connected to Port J2 of the AWJ5 or AWJ6
I/O board.
The other end of the C25AS-MOD cable is then connected to a V.35 modem or DSU.
At the remote end modem or DSU, the final connection to a V.35 DTE device is made with a
V.35 or V.35-MM cable. Selection of the proper terminating cable will depend on the gender
of the V.35 connectors on the modem or DSU and the end device.
3-8
Data Networking Products SYNC8 Module Reference, Issue 3
________________
SYNC8 Cabling
Ordering Information: Host, Cluster Controller, or DTE Device via
Modem, DSU or FOM Connections
TABLE 3-4.
_____________________________________________________________________________




Cable or
ED5P055-31




Adapter Name
Description
Group Number
_____________________________________________________________________________



B25A
50-pin 90-M
G(106), G(F)




50-pin 90-F
_____________________________________________________________________________







B25FS-1MOD
50-pin 180-M
G(262), G(C)




50-pin 90-M
_____________________________________________________________________________



SYNC4-F
50-pin 90-F
G(161), G(R)




_____________________________________________________________________________



4 25-pin-F




SYNC4-M
50-pin 90-F
G(160), G(R)




4 25-pin-M
_____________________________________________________________________________



M25A
25-pin-M
G(107), G(P)




_____________________________________________________________________________



25-pin-F




M25B
25-pin-M
G(108), G(P)




25-pin-M
_____________________________________________________________________________







C25AS-MOD
50-pin 180-M
G(202), G(C)
_____________________________________________________________________________



V.35-M




V.35
34-pin-M
G(170), G(T)




34-pin-F
_____________________________________________________________________________







V.35-MM
34-pin-M
G(220), G(T)
_____________________________________________________________________________



34-pin-M

Cabling SYNC8 to R-VDM via VDM Cabinet
The cabling from a node shelf or BNS-2000 MPC SYNC8 module to a Remote Voice/Data
Multiplexer (R-VDM) via a VDM cabinet can be configured as follows:
VDM cabinet backplanes each provide four 50-pin data-interface connectors that support six
circuits each. A fully populated VDM cabinet with 12 shelves and 288 circuits requires 48
data interface cables.
The SYNC8 module for this application consists of an MC1D089A1 main circuit pack with
an AWJ17 I/O board.
A B25FS-1MOD cable connects to each port of the I/O board and to a SYNC4-M cable
providing four RS-232-C connections.
A SYNC6-M cable is then connected to the RS-232-C connectors on the SYNC4-M cables.
The 50-pin connector end of the SYNC6-M cable is then connected to the VDM backplane.
Data Networking Products SYNC8 Module Reference, Issue 3
3-9
________________
SYNC8 Cabling
NOTE:
The SYNC6-M cable provides six RS-232-C connections, therefore, each SYNC6M cable will mate with one and one-half SYNC4-M cables.
When determining cable lengths, it should be noted that the B25FS-1MOD shielded cables
connect a node shelf and the VDM cabinet. The SYNC4-M and SYNC6-M cables reside
within the VDM cabinet. Lucent Technologies recommends an overall cable length of six feet
for these cables; the length of each cable leg is five feet and the length from the 50-pin
connector to the butt (i.e., the point at which the cable branches out into the cable legs) is
one foot.
For each VDM circuit in a central office (CO), a corresponding R-VDM is required at the
customer or end user equipment location. The connection between the VDM cabinet in the
CO and the R-VDM at the customer or end user equipment location is provided as follows:
– The VDM voice and voice/data circuits are connected to the CO Main Distribution Frame
(MDF) with an A25RX cable. Each of the 50-pin A25RX cables provides voice and
voice/data connections for 12 circuits.
– The connectorized end of the A25RX cable connects to one of the 50-pin plugs on the
VDM backplane. The butt end is then connected to the MDF.
– Voice channels are wired from the MDF to the CO voice switch.
– Voice/data channels are wired from the MDF to the R-VDM over 2-wire unloaded loop
(maximum length is 18,000 feet) or via a Subscriber Loop Carrier (SLC 96) system.

TABLE
3-5. Ordering Information: R-VDM via VDM Cabinet Connections
_________________________________________________________
_________________________________________________________
Cable or Adapter Name  Description  ED5P055-31 Group Number 




 B25A
 50-pin 90-M  G(106), G(F)

_________________________________________________________
 50-pin 90-F 

 B25FS-1MOD
 50-pin 180-M  G(262), G(C)

_________________________________________________________
 50-pin 90-M 





 SYNC4-M
 50-pin 90-F  G(160), G(R)

_________________________________________________________
 4 25-pin-M


 SYNC6-M
 6 25-pin-F
 G(164), G(E)


 50-pin 180-M 

_________________________________________________________



 A25RX
 50-pin 180-F  G(115), G(A)

_________________________________________________________
 single-ended 

3-10
Data Networking Products SYNC8 Module Reference, Issue 3
________________
SYNC8 Cabling
Cabling SYNC8 to R-VDM via VDM Stand-Alone Shelf
The cabling from a node shelf or BNS-2000 MPC SYNC8 module to an R-VDM via a VDM
Stand-Alone Shelf can be configured as follows:
The VDM Stand-Alone Shelf supports up to 18 VDM circuit packs. The backplane for the
Stand-Alone Shelf is equipped with 18 DB25 connectors for RS-232-C connections.
The SYNC8 module for this application consists of an MC1D089A1 main circuit pack with
an AWJ17 I/O board.
A B25FS-1MOD cable connects to each port of the I/O board and to a SYNC4-M cable
providing four RS-232-C connections.
All four legs of the SYNC4-M cable can connect to receptacles on the VDM Stand-Alone
Shelf.
For each VDM circuit in a CO, a corresponding R-VDM is required at the customer or end
user equipment location. The connection between the VDM Stand-Alone Shelf in the CO and
the R-VDM at the customer or end user equipment location is provided as follows:
– The VDM Stand-Alone Shelf voice and voice/data circuits are connected to the CO Main
Distribution Frame (MDF) with an A25RXM cable. Each of the 50-pin A25RXM cables
provides voice and voice/data connections for 12 circuits.
– The connectorized end of the A25RXM cable connects to one of the 50-pin plugs on the
VDM backplane. The butt end is then connected to the MDF.
– Voice channels are wired from the MDF to the CO voice switch.
– Voice/data channels are wired from the MDF to the R-VDM over 2-wire unloaded loop
(maximum length is 18,000 feet) or via a Subscriber Loop Carrier (SLC 96) system.
Data Networking Products SYNC8 Module Reference, Issue 3
3-11
________________
SYNC8 Cabling
TABLE 3-6.
Ordering Information: R-VDM via VDM Stand-Alone Shelf Connections
_____________________________________________________________________________




Cable or
ED5P055-31




Adapter
Name
Description
Group
Number
_____________________________________________________________________________



B25A
50-pin 90-M
G(106), G(F)




50-pin 90-F



_____________________________________________________________________________




B25FS-1MOD
50-pin 180-M
G(262), G(C)




50-pin 90-M
_____________________________________________________________________________



SYNC4-M
50-pin 90-F
G(160), G(R)




4 25-pin-M



_____________________________________________________________________________




A25RXM
50-pin 180-M
G(167), G(A)




single-ended

_____________________________________________________________________________


Cabling SYNC8 to R-VDM via Model 045CS VDM
The cabling from a node shelf or BNS-2000 MPC SYNC8 module to an R-VDM via a Model
045CS VDM can be configured as follows:
The Model 045CS VDM is a single circuit assembly housed in a plastic enclosure with the
modulating circuitry of the VDM cabinet circuit pack. The Model 045CS VDM is equipped
with one DB25 connector for the data interface.
The SYNC8 module for this application consists of an MC1D089A1 main circuit pack with
an AWJ17 I/O board.
A B25FS-1MOD cable connects to each port of the I/O board and to a SYNC4-M cable
providing four RS-232-C connections.
One leg of the SYNC4-M cable connects to the Model 045CS VDM.
For each VDM circuit in a CO, a corresponding R-VDM is required at the customer or end
user equipment location. The connection between the Model 045CS VDM in the CO and the
R-VDM at the customer or end user equipment location is provided as follows:
– The Model 045CS VDM voice and voice/data circuits are connected to the CO Main
Distribution Frame (MDF) through D6AM modular cables and 635B connecting blocks.
Each pair of the D6AM modular cables provides one voice and one voice/data connection.
– One end of each of the D6AM modular cables connects to the TEL and LINE receptacles
on the Model 045CS VDM. The other end of these cables connects to receptacles on a
635B connecting block that, in turn, is connected to the CO MDF.
– Voice channels (from the TEL receptacle) are wired from the MDF to the CO voice switch.
3-12
Data Networking Products SYNC8 Module Reference, Issue 3
________________
SYNC8 Cabling
– Voice/data channels (from the LINE receptacle) are wired from the MDF to the R-VDM
over 2-wire unloaded loop (maximum length is 18,000 feet) or via a Subscriber Loop
Carrier (SLC 96) system.
TABLE

3-7. Ordering Information: R-VDM via VDM Model 045CS VDM Connections
_________________________________________________________
_________________________________________________________
Cable or Adapter Name  Description  ED5P055-31 Group Number 




 B25A
 50-pin 90-M  G(106), G(F)

_________________________________________________________
 50-pin 90-F 

 B25FS-1MOD
 50-pin 180-M  G(262), G(C)

_________________________________________________________
 50-pin 90-M 





 SYNC4-M
 50-pin 90-F  G(160), G(R)

_________________________________________________________
 4 25-pin-M


 D6AM
 6-pin mod
 G(144), G(H)


 6-pin mod


_________________________________________________________



Cabling SYNC8 to R-VDM via D4 Channel Bank
and VDM Cabinet
The cabling from a node shelf or BNS-2000 MPC SYNC8 module to an R-VDM via D4 channel
bank and the VDM cabinet in a Foreign Serving Office (FSO) can be configured as follows:
Each VDM cabinet shelf used for synchronous service in this application must be configured
with an ED2P497-30, G(7) (Model 10F) shelf with 24 RS-232-C DB25 connectors. This
configuration supports up to 24 circuits (one circuit per data connector) per shelf, and requires
up to 24 data cables to the D4 DSU-II dataport. Each shelf also has two 50-pin connectors for
voice and voice/data connections to the Main Distribution Frame (MDF).
Connections to the D4 RS-232-C DSU-II dataport, used for CO-LAN Foreign Serving Office
(FSO) arrangements of the VDM and the node, may be made via a DB25 connection on the
faceplate of the DSU-II dataport plug-in unit or via direct connections to the backplane of the
D4 channel bank.
The SYNC8 module for this application consists of an MC1D089A1 main circuit pack with
an AWJ17 I/O board.
A B25FS-1MOD cable connects to each port of the I/O board and to a SYNC4-M cable
providing four RS-232-C connections.
An M25AS-DSU cable connects each leg of the SYNC4-M cable to one D4 DSU-II dataport.
Data Networking Products SYNC8 Module Reference, Issue 3
3-13
________________
SYNC8 Cabling
A D4 DSU-II dataport plug-in supports one circuit with a female DB25 RS-232-C connector.
At the remote end D4 DSU-II dataport, a M25B-DSU cable is connected from each D4 DSUII dataport to a port in the VDM cabinet.
For each VDM circuit in a CO, a corresponding R-VDM is required at the customer or end
user equipment location. The connection between the VDM cabinet in the CO and the RVDM at the customer or end user equipment location is provided as follows:
– The VDM voice and voice/data circuits are connected to the CO Main Distribution Frame
(MDF) with an A25RXM cable. Each of the 50-pin A25RXM cables provides voice and
voice/data connections for 12 circuits.
– The connectorized end of the A25RXM cable connects to one of the 50-pin plugs on the
VDM backplane. The butt end is then connected to the MDF.
– Voice channels are wired from the MDF to the CO voice switch.
– Voice/data channels are wired from the MDF to the R-VDM over 2-wire unloaded loop
(maximum length is 18,000 feet) or via a Subscriber Loop Carrier (SLC 96) system.
TABLE

3-8. Ordering Information: R-VDM via D4 Channel Bank and VDM Cabinet
Connections
_____________________________________________________________________________




Cable or
ED5P055-31
_____________________________________________________________________________



Adapter Name
Description
Group Number




B25A
50-pin 90-M
G(106), G(F)




50-pin 90-F
_____________________________________________________________________________







B25FS-1MOD
50-pin 180-M
G(262), G(C)




50-pin 90-M
_____________________________________________________________________________



SYNC4-M
50-pin 90-F
G(160), G(R)




4 25-pin-M
_____________________________________________________________________________







M25AS-DSU
25-pin-F
G(169), G(AL)




25-pin-M
_____________________________________________________________________________



M25B-DSU
25-pin-M
G(166), G(AM)




_____________________________________________________________________________



25-pin-M




A25RXM
50-pin 180-M
G(167), G(A)




single-ended
_____________________________________________________________________________



3-14
Data Networking Products SYNC8 Module Reference, Issue 3
________________
SYNC8 Cabling
Cabling SYNC8 to R-VDM via D4 Channel Bank
and VDM Stand-Alone Shelf
The cabling from a node shelf or BNS-2000 MPC SYNC8 module to an R-VDM via D4 channel
bank and the VDM Stand-Alone Shelf in a Foreign Serving Office (FSO) can be configured as
follows:
The VDM Stand-Alone Shelf supports up to 18 circuits. Female DB25 RS-232-C connectors
are provided for each circuit, requiring 18 data cables per shelf.
Connections to the D4 RS-232-C DSU-II dataport, used for CO-LAN Foreign Serving Office
(FSO) arrangements of a VDM and a node, may be made via a DB25 connection on the
faceplate of the DSU-II dataport plug-in unit or via direct connections to the backplane of the
D4 channel bank.
The SYNC8 module for this application consists of an MC1D089A1 main circuit pack with
an AWJ17 I/O board.
A B25FS-1MOD cable connects to each port of the I/O board and to a SYNC4-M cable
providing four RS-232-C connections.
An M25AS-DSU cable connects each leg of the SYNC4-M cable to one D4 DSU-II dataport.
A D4 DSU-II dataport plug-in supports one circuit with a female DB25 RS-232-C connector.
At the remote end D4 DSU-II dataport, an M25B-DSU cable connects the D4 DSU-II dataport
to the VDM Stand-Alone Shelf.
For each VDM circuit in a CO, a corresponding R-VDM is required at the customer or end
user equipment location. The connection between the VDM Stand-Alone Shelf in the CO and
the R-VDM at the customer or end user equipment location is provided as follows:
– The VDM Stand-Alone Shelf voice and voice/data circuits are connected to the CO Main
Distribution Frame (MDF) with an A25RXM cable. Each of the 50-pin A25RXM cables
provides voice and voice/data connections for 12 circuits.
– The connectorized end of the A25RXM cable connects to one of the 50-pin plugs on the
VDM backplane. The butt end is then connected to the MDF.
– Voice channels are wired from the MDF to the CO voice switch.
– Voice/data channels are wired from the MDF to the R-VDM over 2-wire unloaded loop
(maximum length is 18,000 feet) or via a Subscriber Loop Carrier (SLC 96) system.
Data Networking Products SYNC8 Module Reference, Issue 3
3-15
________________
SYNC8 Cabling
Ordering Information: R-VDM via D4 Channel Bank and VDM StandAlone Shelf Connections
TABLE 3-9.
_____________________________________________________________________________




Cable or
ED5P055-31




Adapter Name
Description
Group Number
_____________________________________________________________________________



B25A
50-pin 90-M
G(106), G(F)




50-pin 90-F
_____________________________________________________________________________







B25FS-1MOD
50-pin 180-M
G(262), G(C)




50-pin 90-M
_____________________________________________________________________________



SYNC4-M
50-pin 90-F
G(160), G(R)




4 25-pin-M
_____________________________________________________________________________







M25AS-DSU
25-pin-F
G(169), G(AL)




25-pin-M
_____________________________________________________________________________



M25B-DSU
25-pin-M
G(166), G(AM)




_____________________________________________________________________________



25-pin-M




A25RXM
50-pin 180-M
G(167), G(A)




single-ended
_____________________________________________________________________________



Cabling SYNC8 to R-VDM via D4 Channel Bank
and Model 045CS VDM
The cabling from a node shelf or BNS-2000 MPC SYNC8 module to an R-VDM via D4 channel
bank and the Model 045CS VDM in a Foreign Serving Office (FSO) can be configured as
follows:
The Model 045CS VDM supports one circuit. A female DB25 RS-232-C connector is
provided, requiring one data cable per VDM.
Connections to the D4 RS-232-C DSU-II dataport, used for CO-LAN Foreign Serving Office
(FSO) arrangements of a VDM and a node, may be made via a DB25 connection on the
faceplate of the DSU-II dataport plug-in unit or via direct connections to the backplane of the
D4 channel bank.
The SYNC8 module for this application consists of an MC1D089A1 main circuit pack with
an AWJ17 I/O board.
A B25FS-1MOD cable connects to each port of the I/O board and to a SYNC4-M cable
providing four RS-232-C connections.
An M25AS-DSU cable connects each leg of the SYNC4-M cable to one D4 DSU-II dataport.
A D4 DSU-II dataport plug-in supports one circuit with a female DB25 RS-232-C connector.
3-16
Data Networking Products SYNC8 Module Reference, Issue 3
________________
SYNC8 Cabling
At the remote end D4 DSU-II dataport, an M25B-DSU cable connects the D4 DSU-II dataport
to the Model 045CS VDM.
For each VDM circuit in a central office (CO), a corresponding R-VDM is required at the
customer or end user equipment location. The connection between the Model 045CS VDM in
the CO and the R-VDM at the customer or end user equipment location is provided as
follows:
– The Model 045CS VDM voice and voice/data circuits are connected to the CO Main
Distribution Frame (MDF) through D6AM modular cables and 635B connecting blocks.
Each pair of the D6AM modular cables provides one voice and one voice/data connection.
– One end of each of the D6AM modular cables connects to the TEL and LINE receptacles
on the Model 045CS VDM. The other end of these cables connects to receptacles on a
635B connecting block that, in turn, is connected to the CO MDF.
– Voice channels (from the TEL receptacle) are wired from the MDF to the CO voice switch.
– Voice/data channels (from the LINE receptacle) are wired from the MDF to the R-VDM
over 2-wire unloaded loop (maximum length is 18,000 feet) or via a Subscriber Loop
Carrier (SLC 96) system.
TABLE

3-10. Ordering Information: R-VDM via D4 Channel Bank and Model 045CS
VDM Connections
_____________________________________________________________________________




Cable or
ED5P055-31




Adapter Name
Description
Group Number
_____________________________________________________________________________



B25A
50-pin 90-M
G(106), G(F)




50-pin 90-F
_____________________________________________________________________________







B25FS-1MOD
50-pin 180-M
G(262), G(C)




50-pin 90-M
_____________________________________________________________________________



SYNC4-M
50-pin 90-F
G(160), G(R)




4 25-pin-M
_____________________________________________________________________________







M25AS-DSU
25-pin-F
G(169), G(AL)




25-pin-M
_____________________________________________________________________________



M25B-DSU
25-pin-M
G(166), G(AM)




_____________________________________________________________________________



25-pin-M




D6AM
6-pin mod
G(144), G(H)




6-pin mod
_____________________________________________________________________________



Data Networking Products SYNC8 Module Reference, Issue 3
3-17
________________
SYNC8 Administration
StarKeeper II NMS Administration
4-4
Command Set
4-4
Parameter Considerations
4-5
4-6
4-7
4-7
4-7
4-8
4-8
4-8
4-8
4-9
4-9
Module Addresses
Port Numbers
Download Server
Code Set
Port Duplex
Logoff method
Message Chaining
Terminal Type
Screen Size
Attention String
Administrative Procedures
Reports
4-9
4-14
Data Networking Products SYNC8 Module Reference, Issue 2
________________
SYNC8 Administration
SYNC8 modules support BSC3270-type terminals with switched access to multiple 3270-type
hosts. The SYNC8 modules, which contain downloadable software, can be installed directly into
the node shelf or BNS-2000 MPC.
A SYNC8 module and its components must be entered in a hierarchical order—that is, the
module is followed by the port, control unit (CU), and terminal. A module can be in service
when ports, CUs, and terminals are entered. However, a port must be out of service to add a CU
and/or terminal on the line. A SYNC8 module cannot be brought into service without at least one
port configured; a port cannot be brought into service unless at least one CU is configured for that
port and at least one terminal is configured for each CU on the port. Similarly, a CU cannot be
brought into service without at least one terminal configured for that CU.
A SYNC8 module port can be configured for terminal or host service. When configured for a
particular service, all ports on the module must provide this service. If the SYNC8 module is
configured for terminal service, the database maintains information about the physical terminals
supported. If the SYNC8 module is configured for host service, the database maintains
information about the virtual terminal or control unit that the host expects.
Before SYNC8 administration can begin, use enter group to enter into the database the
appropriate groups with which the particular ports can be associated. The group for a SYNC8
port must be a receiving group. In addition, round-robin service can be administered on a permodule basis (not a per-port basis) with the same iteration of enter group. With round-robin
administered, the system continually cycles through all available modules until a free module is
found for the next incoming call. This group search sequence repeatedly connects an end user to
a free, in-service module.
Besides groups, all appropriate addresses must be entered into the database with the enter
address command before SYNC8 administration can begin. See the BNS-2000 Node Reference
or the Data Networking Products Multipurpose Concentrator Reference for the appropriate
procedures and commands.
The logoff commands enable you to customize logoff sequences and to associate these sequences
with BSC3270 host virtual terminals.
A logoff sequence can consist of several messages, each up to 25 characters long. A message is
made up of an Attention Identification (AID) byte and, optionally, a cursor address, a data
address, and logoff sequence data. The AID byte represents the transmit key associated with a
message; the cursor address is the screen address of the cursor when the logoff sequence is sent to
the host; the data address is the screen address where the logoff sequence is entered on the screen.
Data Networking Products SYNC8 Module Reference, Issue 2
4-3
________________
SYNC8 Administration
StarKeeper II NMS Administration
SYNC8 administration via StarKeeper II NMS is accomplished by using the cut-through mode
of StarKeeper II NMS. SYNC8 commands are entered and executed almost as they would be
entered and executed on the direct console connection. StarKeeper II NMS does not allow all of
the same abbreviations nor does it validate input information. Refer to the following sections on
SYNC8 administration and to the appropriate StarKeeper II NMS documentation for information
on accessing the cut-through mode for your node.
Command Set
SYNC8 module and port information is entered with the enter bsc3270 command. (The SYNC8
supports the BSC3270 protocol, hence the bsc3270 nomenclature in the command names for the
SYNC8.) With this command, you will also specify the download server and software version,
the number of user channels, and the receiving group.
SYNC8 information is thereafter manipulated and checked with the change bsc3270, delete
bsc3270, and verify bsc3270 commands. These commands are used frequently during initial
and routine administration. The enter and change commands have a parameter prompting
sequence in which configurable options are specified in the database. Once specified, these
options can be checked with the verify command and removed with the delete command.
The restore bsc3270 and remove bsc3270 commands control the service state of the module and
its ports; these commands, which affect hardware performance and call processing, are often used
with administration and maintenance procedures. The remove and restore commands can be
verified by using verify oosmods, which lists all out-of-service modules or verify oosports,
which lists all out-of-service ports.
For the SYNC8, the diagnose bsc3270 command is used for module maintenance and
troubleshooting, along with other maintenance and status related commands such as dmeas
bsc3270 and dstat bsc3270.
Refer to Table 4-1 for the SYNC8 command set for BSC3270; complete details are given in
SYNC8 Commands. Information for related command objects can be found in the BNS-2000
Node Reference or the Data Networking Products Multipurpose Concentrator Reference, as
applicable.
Refer to Table 4-2 for the Logoff command set associated with the SYNC8; complete details are
given in SYNC8 Commands.
4-4
Data Networking Products SYNC8 Module Reference, Issue 2
________________
SYNC8 Administration
TABLE 4-1.
SYNC8 BSC3270 Commands
____________________________________________________________________________





Administration
Related Objects
 Operation
 Maintenance 

____________________________________________________________________________
 restore bsc3270  diagnose bsc3270  connections

 enter bsc3270
oosmods





oosports
 remove bsc3270  dmeas bsc3270  group*

 change bsc3270
schedule

 dstat bsc3270
 measurements

 verify bsc3270
delete bsc3270

 module

traffic†

____________________________________________________________________________

 * Enter this object before configuring a SYNC8 in the database


† BNS-2000 only
____________________________________________________________________________


TABLE
4-2. Logoff Commands
_____________________________



Administration  Related Objects 
_ ____________________________
 enter logoff


bsc3270



 change logoff


 verify logoff


delete logoff
_____________________________


Parameter Considerations
Some parameter specifications made during an iteration of enter bsc3270 or change bsc3270 do
not affect other parameters or database elements entered, or the general performance of the
network or node. Other parameters require special consideration because of the nature of the
hardware configuration or the application being supported. These parameters are explained in
this section.
Database configuration for a SYNC8 (BSC3270) module comprises four levels of definition:
1. module
2. port
3. CU (control unit)
4. terminal
Each module can have one to eight ports, and each port can have one to 32 CUs. Up to 32
terminals can attach to each CU. The CU is also called a cluster controller. The service type is
specified at the port level and depends on whether the module is acting as a bisynchronous host
Data Networking Products SYNC8 Module Reference, Issue 2
4-5
________________
SYNC8 Administration
interface module (service type host), or a bisynchronous terminal interface module (service type
terminal). All ports on one module must have the same service type— either host or terminal.
When the module is configured as host, it connects directly to the bisynchronous host line and the
database contains information about the virtual terminals supported. When the module is
configured as terminal, it connects directly to the cluster controller and the database contains
information about the physical terminal supported.
All SYNC8 (BSC3270) terminals must be associated with an existing originating or receiving
group.
The syntax of enter bsc3270 and the database entry forms provided in Appendix A. SYNC8
Database Entry Forms give the correct prompting sequence. In addition, the parameter
definitions provided in enter bsc3270 supplement the following sections.
Module Addresses
The MODULE ADDRESS parameter is used to identify the location of a particular piece of
hardware known as a module. The address of the module depends on its physical placement in a
slot in a node or a supported concentrator. When a module is installed directly into a node slot, its
address is typically represented as:
<module>
Where: module represents the number of the node slot that the module occupies.
If the module is installed in a concentrator, the concentrator is then connected to the node by a
link interface module (LIM) and to the link itself. When a module is installed in a concentrator
slot, its address is represented as:
<concentrator/module>
Where: concentrator is a number indicating the number of the node slot that the LIM
occupies; and module is a number indicating the number of the concentrator slot that the
module occupies. (See the appropriate concentrator reference.)
Depending on the particular command, module addresses can be identified with a single address
entry or with multiple address entries.
If a single address entry is allowed, only one module address can be specified. This addressing
method is indicative of the dmeas and diagnose commands, and many of the enter and change
commands. For example:
dmeas bsc3270 27/2
A slight variation of this addressing method is demonstrated with the verify command, which
allows you to specify either one module address or, with the word all, every module address.
For example:
verify bsc3270 all
4-6
Data Networking Products SYNC8 Module Reference, Issue 2
________________
SYNC8 Administration
Multiple address entries can be specified for like modules only if the modules reside in the same
node or in the same concentrator; they cannot be specified for like modules residing in both a
node and a concentrator.
For multiple, but not all, address entries, you can enter the module address as a single number (x),
a range of numbers (x-y), a series of numbers (x,y,z), or a combination (x-y,z). Some examples
are:
restore bsc3270 module 27-30
(module addresses for four SYNC8s installed into the same node)
restore bsc3270 module 27/13,14
(module address for two SYNC8s installed in the same concentrator)
restore bsc3270 module 27/2,12-14
(modules addresses for SYNC8s installed in the same concentrator)
Port Numbers
The PORT NUMBER parameter is a number from 1 to 8 that identifies a physical port on a
SYNC8. The port number or port numbers can be entered as a single port number entry or as a
multiple port number entry. For a single port number entry, enter only one port number:
PORT NUMBER [1-8: +(1-8)]: 1
For a multiple port number entry, enter a series of numbers (x,y,z), a range of numbers (x-z), or a
combination of both (w,x-z):
PORT NUMBER [1-8: +(1-8)]: 4,6,8
PORT NUMBER [1-8: +(1-8)]: 5-8
PORT NUMBER [1-8: +(1-8)]: 1,5-8
When entering multiple port numbers, the parameter specifications made apply to all port
numbers input at the PORT NUMBER prompt. Single port number entries must be specified when
adding CUs or terminals.
Download Server
The download software resides in the download server. When a SYNC8 module is restored to
service, this software is downloaded to the module. The software that governs the SYNC8’s
functionality can reside on the controller or a host on the network, in case there is more than one
version of downloadable software available on the controller or the host. The SOFTWARE
VERSION prompt is used to specify the version to download when the module is restored to
service.
Code Set
The node provides for conversion of the code set between a physical terminal and the virtual
terminal to which it establishes a connection. The transmission code can be set to asciicrc,
asciiodd, ebcdic, crc2, odd2, or ebc2. The entry of crc2 configures the port for the asciicrc code
Data Networking Products SYNC8 Module Reference, Issue 2
4-7
________________
SYNC8 Administration
set and two EOTs; entry of odd2 configures the port for the asciiodd code set and two EOTs; and
entry of ebc2 configures the port for the ebcdic code set and two EOTs.
Port Duplex
Specify half for multidrop lines; full for point-to-point lines.
Logoff method
A logoff sequence ensures that a host disconnects an existing session when a new user is at the
virtual terminal connected to the host. The host thereby maintains session security, ensuring that
a new user cannot connect to a previous user’s session. The network administrator can specify
that a logoff sequence be used. The sequence can be one of three standard sequences or a
customized sequence previously entered into the database with the enter logoff command. No
sequence can also be specified. The logoff sequence is sent from the BHIM to the host.
Message Chaining
This parameter should be set to yes only when a terminal requires that the attached host chain
messages to it. Multiple messages are sent without reselecting the terminal. Chained messages
are sent from the front-end processor to the host module, and from the terminal module out to the
device. In order to accomplish this, the host module waits (after receiving an End of Text [ETX])
for the next host transmission to determine if the chain is complete. An indication of whether the
message is complete is sent to the terminal module with the previous message. The terminal
module will then retransmit the messages to the connected device in the same way they were
received.
If the parameter is set to no, the host module sends messages to the terminal module after the
ETX is received. Before sending each new message, the terminal module selects the appropriate
terminal, waits for an acknowledgement, and then sends the message.
NOTE:
Message chaining increases response time, because the host module always waits for
one extra message before sending the message to the terminal module. It should be
enabled only if required by the host.
You must coordinate this option with the host administrator.
Terminal Type
Choose the value color or basic for a terminal that uses four colors; basic terminal type does not
support transparent Bisync. Choose color, extended, or color extended to support features
requiring the use of transparent Bisync, like blinking text, inverse video, underlining, and eight
colors. If the host sends transparent Bisync, the terminal must be able to support it. You must
coordinate this option with the host administrator.
4-8
Data Networking Products SYNC8 Module Reference, Issue 2
________________
SYNC8 Administration
Screen Size
The values set indicate the total characters that can be displayed on a terminal screen. Choose
1920 for a Model 2 BSC3270 terminal, with a screen size of 80 characters x 24 lines; 2560 for a
Model 3, 80 x 32; 3440 for a Model 4, 80 x 43; or 3564 for a Model 5, 132 x 27.
Attention String
This parameter allows you to set up to four characters that can be entered by the terminal user to
disconnect a terminal session or place the terminal in command mode (depending on what you
enter at the ATTENTION ACTION parameter).
When configuring this signal, make sure that it is specified in the case (uppercase or lowercase)
you intend the terminal user to enter it in. You will have to know what type of BSC3270 terminal
is connected to specify this correctly. Some BSC3270 terminals have a switch that causes all data
to be displayed on the screen in uppercase, regardless of whether it was entered in uppercase or
lowercase. Users at these terminals would ordinarily enter data in lowercase, so your signal
should be lowercase. Some older BSC3270 models, however, have only uppercase entries and
signals for these should be in uppercase.
Administrative Procedures
The initial administration of a SYNC8 is not hardware-dependent; that is, the module does not
have to be physically installed before its database information is configured. However, for
routine administration and operations procedures, such as removing and restoring modules to
service or displaying module hardware status, module installation is required.
For minor database changes, such as modifications to a few parameters, follow Procedure 4-3.
For database changes involving extensive configuration adjustments, follow Procedure 4-4.

PROCEDURE
4-1. Entering a SYNC8 (bsc3270) Logoff Sequence
A logoff sequence signals a SYNC8 (bsc3270) host that a new end user is at a virtual terminal.
The logoff sequence, a series of commands that attempt to log off the host, is sent to the host
(from the host module) either when the next call is made or when the first call is disconnected.
The host uses this sequence to maintain security, ensuring that a new user does not enter the
previous user’s session.
The enter logoff command configures a customized sequence. This sequence is then identified
during port administration for service type host with the enter bsc3270 command. (A standard
sequence, or no sequence at all, can be specified instead; see Procedure 4-2. Entering a SYNC8
in the Database, below.)
If you are configuring customized sequences, keep the following considerations in mind:
A default maximum of 50 logoff sequences can be administered per node.
Data Networking Products SYNC8 Module Reference, Issue 2
4-9
________________
SYNC8 Administration
PROCEDURE 4-1.
Entering a SYNC8 (bsc3270) Logoff Sequence (continued)
There is a limit of 4,000 bytes of data for all logoff sequences on a node. As you input the
sequence information, a message appears to let you know how many bytes are available.
INFO: There are <num> of bytes remaining.
Each logoff sequence can be made up of several messages, each as long as 25 characters.
The maximum size of a logoff sequence is 245 bytes.
You will have to coordinate node administration with the host administrator, because the
sequence you enter depends on host applications.
To enter a logoff sequence, follow the steps below:
1. Input enter and choose logoff from the OBJECTS
prompt.
2. Follow the prompts to administer the customized logoff sequence.
3. Input verify logoff to check your entries.
4. If you made any errors or have to change parameter specifications, input change logoff. If
you need to start over, input delete logoff to eliminate all entries made; then, begin again
with enter logoff.
PROCEDURE

4-2. Entering a SYNC8 in the Database
1. Input verify group to determine if the appropriate group names have been entered and exist
as a receiving group. If they do not appear in the database as required (they were deleted;
they have changed; they are misspelled), refer to the BNS-2000 Node Reference or the Data
Networking Products Multipurpose Concentrator Reference, as applicable, for procedures on
how to make the necessary changes. Also verify there are only SYNC8 ports associated
with this group. The Delete key can be used to terminate the enter bsc3270 command
without saving the information to the database.
2. Input enter bsc3270 to begin module administration. Have your completed database entry
forms handy and remember that default values can be specified by pressing Return or
+ , as shown in the prompted entry examples for SYNC8 in SYNC8 Commands. You
will be prompted for the download server and software version.
3. Input enter bsc3270 again to begin port administration. You will be prompted for
comments, baud rate, and other port-specific parameters.
4. Input enter bsc3270 again to begin control unit administration. You will be prompted for
the port number and other port-specific parameters.
4-10
Data Networking Products SYNC8 Module Reference, Issue 2
________________
SYNC8 Administration
PROCEDURE 4-2.
Entering a SYNC8 in the Database (continued)
5. Input enter bsc3270 again to begin terminal administration. You will be prompted for the
port number and other port-specific parameters, including the logoff sequence identifier. A
customized sequence is configured separately using the enter logoff command (see
Procedure 4-1).
6. Input verify bsc3270 to check your entries.
7. If you made any errors or have to change parameter specifications, input change bsc3270.
If you need to start over, input delete bsc3270 to eliminate all entries made; then, begin
again with enter bsc3270.
8. If the module has been installed, input restore bsc3270 to bring the module and the port(s)
into service.

PROCEDURE
4-3. Making Minor Database Changes
A minor database change constitutes a change to only a few parameter options.
1. If changes involve groups, make the needed changes with iterations of the group
command. Input verify group to check additions/modifications. See the BNS-2000 Node
Reference or Data Networking Products Multipurpose Concentrator Reference for details.
2. Remove the module ports, then the module from service with remove bsc3270.
NOTE:
The comment parameter of a module or port can be changed without removing it
from service.
3. Make modifications with change bsc3270.
4. Check changes with verify bsc3270.
5. Return the module to service with restore bsc3270.

PROCEDURE
4-4. Making Extensive Database Changes
An extensive database change constitutes a change made to most of the parameter options on one
or more modules.
1. If changes involve groups, make the needed changes with iterations of the group command.
Input verify group to check additions/modifications. See the BNS-2000 Node Reference or
Data Networking Products Multipurpose Concentrator Reference for details.
2. Input verify bsc3270 to get a report of the existing parameter options specified. And if you
feel the need to, complete the database planning forms furnished in Appendix A. SYNC8
Database Entry Forms.
Data Networking Products SYNC8 Module Reference, Issue 2
4-11
________________
SYNC8 Administration
PROCEDURE 4-4.
Making Extensive Database Changes (continued)
3. Remove the module ports, then the module from service with remove bsc3270.
4. Eliminate all database information with delete bsc3270.
5. Re-enter all information with enter bsc3270.
6. Check changes with verify bsc3270.
7. Return the module to service with restore bsc3270.

PROCEDURE
4-5. Moving Database Information to Another Module Address
Module information can be moved to another module address with the move command or with a
combination of delete and enter.
Method 1:
1. Remove the module ports, then the module, from service with remove bsc3270.
2. Input verify module to ensure that a database entry has not been made for the new module
address. (If a database entry does exist for the specified module address, the command
fails.)
3. Input move module to transfer database information from one module address to another.
4. Physically move the hardware.
5. Using the new module address, put the module, and then its ports, back into service with
restore bsc3270.
Method 2:
1. If move module is not appropriate for the situation, input verify bsc3270 to get a report of
the configuration data.
2. Input remove bsc3270 to remove the module from service.
3. Input delete bsc3270 to eliminate all information at the existing module address.
4. Input enter bsc3270 to add the information to the new address.
5. Check information entered at the new address with verify bsc3270.
6. Physically move the hardware.
7. Using the new module address, put the module, and then its ports, back into service with
restore bsc3270.
4-12
Data Networking Products SYNC8 Module Reference, Issue 2
________________
SYNC8 Administration
PROCEDURE 4-6.
Copying Database Information to Another Module Address
If an additional SYNC8 must be installed that requires exactly the same parameter specifications
as a currently installed and configured module, module information can be duplicated from one
module address to another module address with the copy command or with a combination of
verify and enter.
Method 1:
1. Input remove bsc3270 to take the module ports, and then the module, out of service.
2. Input verify module to ensure that a database entry has not been made for the new module
address. (If a database entry does exist for the specified module address, the command
fails.)
3. Input copy module to duplicate the database information from one module address to
another.
4. Input restore bsc3270 to put the module, and then its ports, back into service.
Method 2:
1. If copy module is not appropriate for the situation, input verify bsc3270 to get a report of
the existing parameter options specified. If you wish, complete the database entry forms
furnished in Appendix A. SYNC8 Database Entry Forms.
2. Enter the information for the new module with enter bsc3270.
3. Check information entered with verify bsc3270.
Data Networking Products SYNC8 Module Reference, Issue 2
4-13
________________
SYNC8 Administration
Reports
Besides the specific procedures associated with routine administration, report gathering and
analysis play a vital role when tracking module/network performance, accommodating system
expansion, or troubleshooting. The following table explains the reports available to assist with
these routine tasks.

TABLE
4-3. Available Reports for SYNC8
_______________________________________________________________________________________




Report Topic
Command
Description
_______________________________________________________________________________________



 connection data
 display connections  Lists established connections for modules, groups,

_______________________________________________________________________________________

 or hosts. Group names are included.

 traffic data
 display traffic†
 Lists established connections for modules, groups, or



 hosts. Segment counts are included.



 See the BNS-2000 Node Reference.

_______________________________________________________________________________________



 database size
 dbaudit
 Shows where database space expenditures occur.



 If dbresize is used, the database tables



 are readjusted automatically. See the BNS-2000 Node Reference 


 or Data Networking Products Multipurpose

_______________________________________________________________________________________

 Concentrator Reference.

 module status data
 dstat bsc3270
 Lists hardware/software module data. Module must


 dstat module
 be installed. For dstat module see the BNS-2000 Node Reference 


 or Data Networking Products Multipurpose



 Concentrator Reference.

_______________________________________________________________________________________



 module/channel set data
 verify bsc3270
 Lists hardware/software module/channel set data and


 verify module
 port data as it currently appears in the configuration



 database. Module does not have to be installed.



 For verify module see the BNS-2000 Node Reference or



 Data Networking Products Multipurpose

_______________________________________________________________________________________

 Concentrator Reference.

 out-of-service modules
 verify oosmods
 Lists all installed modules that are currently



 out of service. See the BNS-2000 Node Reference or



 Data Networking Products Multipurpose





_______________________________________________________________________________________

 Concentrator Reference.

 out-of-service ports
 verify oosports
 Lists all administered ports that are currently



 out of service. See the BNS-2000 Node Reference or



 Data Networking Products Multipurpose

_______________________________________________________________________________________

 Concentrator Reference.

† BNS-2000 only
4-14
Data Networking Products SYNC8 Module Reference, Issue 2
________________
SYNC8 Troubleshooting
Problem Indicators
5-3
Problem Areas
5-4
5-6
Procedures for Correcting SYNC8 Problems
SYNC8 Diagnostics
On-line Diagnostics
Off-line Diagnostics
Data Networking Products SYNC8 Module Reference, Issue 2
5-8
5-8
5-11
________________
SYNC8 Troubleshooting
For information about a generalized, systematic approach to troubleshooting, refer to the BNS2000 Node Reference. Using the method outlined there, you can diagnose problems affecting the
entire node and isolate local problems to a specific interface module. Once the problem is
isolated to a particular module, such as an SYNC8, the reference documentation for the module is
needed.
This chapter helps identify and further isolate problems related to the SYNC8, its I/O board, and
cables. It provides problem indicators that are SYNC8-specific, a checklist of problem areas, and
detailed procedures or further references to remedy the problem.
This chapter does not explain problem indicators that are common to all modules such as module
faceplate LEDs. Common problem indicators are explained in the BNS-2000 Node Reference and
the Data Networking Products Multipurpose Concentrator Reference, as applicable. This chapter
does not provide problem isolation techniques or procedures for end users or their connected end
devices. Refer to the BNS-2000 Node Reference or Data Networking Products Multipurpose
Concentrator Reference for this information. In addition, this chapter does not explain how to
verify the integrity of the host boards or run host diagnostics. Only the SYNC8, its I/O board,
and the connecting cables are tested from the node or BNS-2000 MPC. Refer to the appropriate
host documentation to test host boards.
Problem Indicators
Module faceplate indicators, I/O board LEDs, and the output of certain commands are often
problem indicators that are specific to the SYNC8.
The lights associated with the faceplate are green (on-line), yellow
(off-line), and red (fault). When the red (fault) light is lit, the module circuitry has detected an
on-board fault.
Faceplate Indicators.
When pressed, the reset push button clears the module buffers and registers, and restarts the
module application program. The module is taken out of service and connections are terminated.
In addition to the LEDs on the front of the SYNC8, the I/O board has two red LEDs. The upper
red LED (loopback) is on when running diagnostics; the lower red LED (mute) is on when a
module fault occurs.
The I/O board also has a two-position toggle switch (SW1) that is used to move from loopback
mode (the up position) to standard operating mode (the down position). The loopback mode
position of the switch is used only to loop data back to the host when running host diagnostics.
Therefore, this switch should always be in the down position, even when running SYNC8
diagnostics.
Command Output.
The output of some operations commands—such as diagnose bsc3270
Data Networking Products SYNC8 Module Reference, Issue 2
5-3
________________
SYNC8 Troubleshooting
and those listed in the following table—can indicate an existing or potential problem.

TABLE
5-1. Command Output
______________________________________________________________________________
______________________________________________________________________________



Command
Description
Further Reference
 diagnose bsc3270
 Enables you to initiate an off-line or on-line diagnostic  See SYNC8 Diagnostics in 

 test for a SYNC8 module or port. Off-line
 this chapter. See diagnose 

 diagnostics, which check module hardware, include
 bsc3270 in SYNC8


 boot diagnostics, memory tests, and downloaded
 Commands.


 diagnostics. On-line diagnostics check the



 communications path, one port at a time.


______________________________________________________________________________



 display connections  Shows established connections for modules, groups,
 See Procedure 5-2.


 or hosts. Group names are included.
 Correcting SYNC8 Link

______________________________________________________________________________

 Failure.

 display traffic*
 Shows established connections for modules, groups,
 See Procedure 5-3. Solving 
 (BNS-2000 only)
 or hosts. Segment counts are included.
 Terminal and/or Data

______________________________________________________________________________

 Device Problems.

 dmeas bsc3270
 Generates on-demand reports for a SYNC8
 See dmeas bsc3270 in


 component. The reports contain traffic, performance,  SYNC8 Commands.


 and utilization measurements for the module or port. 

______________________________________________________________________________



 dstat module
 Provides useful hardware and software
 See the BNS-2000 Node


 troubleshooting information, such as the number of
 Reference or Data


 module resets, parity errors, and sanity errors that
 Networking Products


 occurred during a five-minute interval; and module
 Multipurpose Concentrator 

 service state and mode state information as
 Reference.


 determined by status packet data. Output can be



 compared to that of verify bsc3270 and module


______________________________________________________________________________
 faceplate indicators.


 dstat bsc3270
 Displays information on the status of a SYNC8
 See dstat bsc3270 in SYNC8 

 module, port, or terminal. Provides useful hardware
 Commands.


 and software troubleshooting information, such as the 


 number of module resets, parity errors, sanity errors



 and the last hardware and software alarms. Provides 

______________________________________________________________________________
 status of the port, Control Units, and terminals.


 verify bsc3270
 Shows all parameter options configured for a specified  See verify bsc3270 in

 verify module
 SYNC8.
 SYNC8 Commands.

______________________________________________________________________________



Problem Areas
Once you determine that the problem is not with the node, its critical modules, or any connected
end device, the problem can be isolated to the SYNC8. Check for alarm messages or the red LED
being lit to spot module problems. Table 5-2 shows problems specific to a SYNC8.
The table lists "Symptoms/Indicators" to show how you may detect a lack or degradation of usual
service. The column "Possible Causes" suggests areas in which troubleshooting should begin;
5-4
Data Networking Products SYNC8 Module Reference, Issue 2
________________
SYNC8 Troubleshooting
the column "Actions" refers you to useful troubleshooting procedures or to other sources. Each
suggested action is a point of departure for isolating and diagnosing problems.
TABLE

5-2. SYNC8 Problems
________________________________________________________________________________




√
Symptom/Indicator
Possible Causes
Actions
________________________________________________________________________________




 ____ Module will not download or
 Faulty module
 Perform Procedure 5-1.

 restore

 Correcting SYNC8

________________________________________________________________________________

 Download Failure.

 ____ Link does not come up
 Module or Port out of service. External  Perform Procedure 5-2.


 equipment powered off or not
 Correcting SYNC8 Link


 connected.
 Failure at BTIM or BHIM 


 seeing the problem.

________________________________________________________________________________




 ____ Link comes up, but no data is
 Timing problem
 Perform Procedure 5-3.

 passed

 Correcting SYNC8 Timing 
________________________________________________________________________________

 Problems.

 ____ User does not get
 Module or port or terminal is out of
 Perform Procedure 5-2.

 DESTINATION: prompt
 service. Incorrect port or term
 Correcting SYNC8 Link


 configuration.
 Failure at BTIM.

________________________________________________________________________________




 ____ Call does not get set up
 Receive module or port or terminal out  Perform Procedure 5-2.


 of service. Incorrect port or terminal
 Correcting SYNC8 Link

________________________________________________________________________________
 configuration.
 Failure at BTIM and BHIM. 




 ____ Call is set up but no data is
 If host line was just started, response
 Look for alarms. See the

 received from host
 time will be poor because host has to
 Data Networking Products 

 select all devices initially.
 Messages Reference for



 alarm information. Restart 


 host line. If these steps do



 not solve the problem, use a 


 protocol analyzer to monitor 
________________________________________________________________________________

 the BTIM and BHIM ports. 
 ____ User gets TERMINAL
 Only one input message at a time can
 Wait a few minutes and try 
 TEMPORARILY OUT OF SERVICE
 be outstanding from a particular
 again. As a last resort,

 message on user terminal, and message  terminal. Host may be busy processing  remove and restore the BTIM 
 does not clear itself.
 other terminals and may take a long
 terminal device that is seeing 

 time before it processes the data from  the problem.


 this terminal. Any attempt to send



 another input message will result in this 

________________________________________________________________________________
 message.






 ____ User gets TERMINAL OUT OF
 BTIM terminal device is out of service.  Restore BTIM terminal

 SERVICE UNTIL FURTHER NOTICE

 device that is getting the

 message.
________________________________________________________________________________

 message.

Data Networking Products SYNC8 Module Reference, Issue 2
5-5
________________
SYNC8 Troubleshooting
Procedures for Correcting SYNC8 Problems
PROCEDURE

5-1. Correcting SYNC8 Download Failure
1. Record any alarm when a failure occurs; see Data Networking Products Messages Reference
for a more complete description.
2. If the module is in a concentrator, check the link for errors.
3. Use the verify bsc3270 command to check the download server and software version. If
they are not the Control Computer defaults, determine if the path to the serving host is
functional.
4. Reseat the module and try to download again using restore bsc3270.
5. Replace the module and attempt to download again.
6. Check the voltages on the backplane to determine if a potential power problem exists and
verify that the voltage on the modular power supplies are set correctly; see the BNS-2000
Node Reference or the Data Networking Products Multipurpose Concentrator Reference.
7. Run off-line diagnostics on the module; see Procedure 5-8 or Procedure 5-9 as applicable.
PROCEDURE

5-2. Correcting SYNC8 Link Failure
Requirements:
Run this procedure at both the origination and destination ports.
1. Verify the configuration specifications for the port: duplex, baud rate, etc.
2. Look for alarms at the port, control unit, or terminal. See the Data Networking Products
Messages Reference for information on alarms.
3. Verify that the module and port and terminal are in service and the predefined destination
(PDD) or circuit is connected.
4. Verify that the I/O board and cables are correct and secure; see SYNC8 Cabling.
NOTE:
I/O boards AWJ5 and AWJ6 use the bottom 50-pin connector as a V.35 interface.
This is port 1 on the I/O board. The top connector provides RS-232-C ports 2, 3,
and 4.
5. Use display connections on both ends of the link to determine if they are communicating
and if the PDD has been set up.
5-6
Data Networking Products SYNC8 Module Reference, Issue 2
________________
SYNC8 Troubleshooting
PROCEDURE 5-2.
Correcting SYNC8 Link Failure (continued)
6. Input dstat bsc3270 and check the operating state of the port, control unit, and terminal at
both ends.
a. If the operating state of the port is down, this indicates that the external equipment is
not connected to the BHIM or BTIM. Check the RS-232-C leads. Input dstat bsc3270
with the high detail option for the particular port.
The Electronics Industry Association (EIA) control signals (DTR, DCD) should be
active.
If the I/O board is a DCE type, the I/O board will supply DCD and timing and the
attached device should be asserting data terminal ready (DTR).
If the I/O board is a DTE type, the I/O board will supply DTR and the attached
device should be supplying data carrier detect (DCD) and timing.
If the attached device is not providing these signals, the link will stay down.
b. If the operating state of the control unit is down, proceed as follows, depending on
whether the control unit is down at the BHIM or BTIM:
BHIM—The host is not polling. Restart the host line and check that the host line is
configured to poll this control unit.
BTIM—The physical control unit did not respond to the poll. Ensure the control
unit is physically present, powered on, and its bisynchronous address matches the
address for which the BTIM is configured.
c. If, for the terminal, the AVAILABLE message shows no, proceed as follows, depending
on whether the terminal is unavailable at the BHIM or BTIM:
BHIM—The host is not polling. Restart the host line and check that the host line is
configured to poll the control unit to which this terminal is attached.
BTIM—The physical terminal did not respond to a select from the BTIM. Ensure
the terminal is physically present and powered on.
7. If the node side is at fault, try the following:
a. Remove and restore the module.
b. Run diagnostics, as instructed in the next section of this chapter.
c. Replace the module and I/O board.
d. Change slots.
e. Check backplane voltages.
If the steps above do not solve the problem, use a protocol analyzer on the link. First monitor the
BTIM port, then monitor the BHIM port. Verify that polling is occurring and devices are
responding to the polls.
Data Networking Products SYNC8 Module Reference, Issue 2
5-7
________________
SYNC8 Troubleshooting
PROCEDURE 5-3.
Correcting SYNC8 Timing Problems
1. Determine what devices provide timing.
2. Set up other devices correctly to derive timing from the master source.
3. When connecting modems back-to-back, note the following:
In most cases, modems (DCE devices) provide timing to hosts and terminals (DTE
devices).
One modem is usually set up for master timing (internal timing) and the other is set up
for received timing. This setup allows one modem to derive its timing from the master
timing modem.
When a host or DTE device provides the timing, the modem is set for external timing,
which allows it to take the timing from RS-232-C pin 24. The other modem still uses
received timing from the master timing modem.
4. Choose between a DCE or DTE I/O board. One board can provide timing and the other
cannot. Make sure you have the right board.
SYNC8 Diagnostics
Both on-line and off-line diagnostics are available for the SYNC8.
On-line diagnostics, or loopback tests, are run on one port at a time and affect service on that port
only.
Off-line diagnostics check the module hardware. Three tests—boot diagnostics, memory tests,
and downloaded diagnostics are available. These three tests run consecutively. If any of the three
fails, testing automatically stops at that point.
On-line Diagnostics
On-line diagnostics for the SYNC8 include the following tests:
Internal Port
External Port
Local Modem
Remote Modem
During these on-line diagnostics, the module must be in service, and the port to be tested must be
entered in the database and out of service.
5-8
Data Networking Products SYNC8 Module Reference, Issue 2
________________
SYNC8 Troubleshooting
PROCEDURE 5-4.
Running the Internal Port Test
The Internal Port test places the Universal Synchronous/Asynchronous Receiver/Transmitter
(USART) within the module into loopback mode and sends a test message through the USART
and back to the module.
1. Enter
diagnose bsc3270 on-line
<module address> <port#> internal_port
a. If the test passes, go to Procedure 5-5. Running the External Port Test or Procedure
5-6. Running the Local Modem Test, depending on whether a DCE or DTE I/O
distribution board is being used.
b. If the test fails, the trouble is probably in the module. Replace the module and repeat
the test.

PROCEDURE
5-5. Running the External Port Test
The External Port test is used for DCE ports.
Requirements:
A special loopback connector (ED5P056-30, G24) is required.
1. Remove the normal cable and attach the loopback connector.
2. Enter
diagnose bsc3270 on-line
<module address> <port #> external_port
a. If the test passes, the problem may be in the connection to the Public Data Network
(PDN) or in the network. Move the loopback connector to the next farther location
from the module and repeat the test until you encounter the PDN.
b. If the test fails, the trouble is probably in the I/O distribution board. Check the switch
settings or replace the board and repeat the test.
3. Remove the loopback connector and reattach the normal cable.
Data Networking Products SYNC8 Module Reference, Issue 2
5-9
________________
SYNC8 Troubleshooting
PROCEDURE 5-6.
Running the Local Modem Test
The Local Modem test is for DTE ports.
1. Place the modem in loopback mode as appropriate for the modem being used.
2. Enter
diagnose bsc3270 on-line
<module address> <port #> local_modem
a. If the test passes, go to Procedure 5-7. Running the Remote Modem Test.
b. If the test fails, check the SYNC8 I/O distribution board and its switch settings, the
cables between the I/O distribution board and the modem, or the local modem. Replace
each component, one at a time, until the problem is resolved.
3. Remove the local modem from loopback mode when the test is complete.

PROCEDURE
5-7. Running the Remote Modem Test
The Remote Modem test is for DTE ports.
1. Place the remote modem in loopback mode as appropriate for the modem being used.
2. Enter
diagnose bsc3270 on-line
<module address> <port #> remote_modem
a. If the test passes, the trouble may be between the remote modem and the remote end.
Replace the cable and repeat the test. Run the same sequence of tests from the remote
end.
b. If the test fails, the trouble is probably in the transmission facility between the two
modems or in the remote modem. Replace the faulty component and repeat the test.
5-10
Data Networking Products SYNC8 Module Reference, Issue 2
________________
SYNC8 Troubleshooting
Off-line Diagnostics
Off-line diagnostics for the SYNC8 consist of three tests— boot diagnostic, memory test, and
downloaded diagnostics—which run consecutively when the diagnose bsc3270 off-line
command is entered. The results are displayed at the end of each test. If a test fails, testing
automatically stops at that point, see Procedure 5-8.
During off-line diagnostics, the module and at least one port must be entered in the database and
the module must be out of service.
Off-line diagnostics are also available for a SYNC8 port with a VDM connected to the line, see
Procedure 5-9.

PROCEDURE
5-8. Running the SYNC8 Off-line Test
1. Enter
diagnose bsc3270 off-line
<module address>
2. The SYNC8 module is faulty if you receive any of the following error messages. Replace
the module and repeat the test.
Offline diagnostic boot test: FAIL
Offline diagnostic memory test: FAIL
Offline diagnostic download test: FAIL
Inst. set:
Timer test:
FAIL
FAIL
3. A Timer test failure accompanied by the message Port x: FAIL indicates that port x
(where x equals 1, 2, 3, or 4) is faulty. Replace the SYNC8 module and repeat the test. If
there is no spare module, the problem may be isolated by removing port x from service.
Data Networking Products SYNC8 Module Reference, Issue 2
5-11
________________
SYNC8 Troubleshooting
PROCEDURE 5-9.
Running the SYNC8 Off-line Test with VDM
For a SYNC8 port with a VDM connected to the line, run the VDM Check Loopback test to
determine whether or not the local or remote VDM is caught in loopback mode. During this test,
a test pattern is sent to the VDM. If the test pattern is not returned, the VDM is not in loopback
mode and the test is successful. If the test pattern is returned, however, the test fails; the VDM is
stuck in loopback mode due to hardware, software, or human failure.
1. Connect a loopback connector for the duration of the test.
2. Enter
diagnose bsc3270 off-line
<module address> <port #> vdm_ckloop
a. If the test pattern is not returned, the test passes.
b. If the local (central) VDM fails this test (the test pattern is returned), restore the port to
service and then remove it from service, and repeat the test. If the test fails again,
replace the VDM.
c. If the remote VDM fails this test (the test pattern is returned), the remote administrator
may have mistakenly moved the loopback switch to the wrong position. Check with the
administrator to eliminate this possibility. If this was not the cause, the VDM is most
likely faulty; replace the VDM.
3. Remove the loopback connector and reconnect the standard cables.
5-12
Data Networking Products SYNC8 Module Reference, Issue 2
________________
SYNC8 Commands
change bsc3270
delete bsc3270
diagnose bsc3270
dmeas bsc3270
dstat bsc3270
enter bsc3270
remove bsc3270
restore bsc3270
verify bsc3270
System Responses
change logoff
delete logoff
enter logoff
verify logoff
System Responses
Data Networking Products SYNC8 Module Reference, Issue 2
6-4
6-6
6-9
6-12
6-16
6-24
6-35
6-37
6-40
6-44
6-56
6-57
6-58
6-61
6-64
________________
SYNC8 Commands
The commands related to the administration, operation, and maintenance of SYNC8 modules are
detailed in this chapter. The commands are presented in alphabetical order by verb. Since the
SYNC8 commands are for BSC3270 devices, the object of the command verbs is bsc3270. In
addition, the SYNC8 incorporates a set of logoff commands for the administration of the logoff
feature, which concludes this chapter.
System responses to the BSC3270 and logoff commands are at the end of their command section;
the responses are presented in alphabetical order by key phrase.
The enter bsc3270 command shows the full prompting sequence and contains a list of parameter
definitions; as does the enter logoff command. A broader explanation of the parameters used in
the prompting sequence of enter bsc3270, change bsc3270, enter logoff, and change logoff is
given in SYNC8 Administration. In addition, the database entry forms in Appendix A. SYNC8
Database Entry Forms follow the prompting sequence for module information.
Procedures for running diagnostics can be found in SYNC8 Troubleshooting.
Other command objects that are related to the administration, operation, and maintenance of the
SYNC8 are documented in the BNS-2000 Node Reference or Data Networking Products
Multipurpose Concentrator Reference, as applicable.
Data Networking Products SYNC8 Module Reference, Issue 2
6-3
________________
change bsc3270
change bsc3270
The change bsc3270 command enables you to modify most SYNC8 module and component
information in the database. The module address, port number, CU number, terminal number,
and service state cannot be modified. Information regarding a device can only be changed if the
port to which the device is connected is removed from service. The COMMENT parameter of a
module or port can be changed without removing it from service.
Syntax
You can input change bsc3270 in prompted entry only. The command syntax for enter bsc3270
and change bsc3270 is similar. The defaults for change bsc3270 are those values, conditions, or
states that currently exist in the database. They are displayed within parentheses in the parameter
prompt.
Parameters
Refer to the parameter definitions supplied in enter bsc3270.
Prompted Entry: Changing BSC3270 Virtual Terminal Information for Host Service
CC0> change
OBJECTS [...bsc3270...]: bsc3270
COMPONENT [module, port, terminal]: terminal
MODULE ADDRESS: 70
PORT NUMBER [1-8]: 1
VIRTUAL CONTROL UNIT [1-32]: 1
VIRTUAL TERMINAL NUMBER [1-32: +(1-32)]: 1
TERMINAL TYPE [basic, color, extended, c/e: +(basic)]: color
RECEIVE-ONLY? [yes, no: +(no)]: +
SCREEN SIZE [1920, 2560, 3440, 3564: +(3564)]: +
FORWARD DELIVERY ACKNOWLEDGEMENT? [yes, no: +(no)]: +
TERMINAL SECURITY ON? [yes, no: +(no)]: +
RECEIVING GROUP [up to 8 chars: +(bscr)]: +
LOGOFF METHOD [disc, none, sas, test, other: +(none)]: other
LOGOFF SEQUENCE IDENTIFIER [up to 6 chars]: BYE
VIRTUAL TERMINAL NUMBER [1-32: +(1-32)]:
Delete
CC0>
6-4
Data Networking Products SYNC8 Module Reference, Issue 2
________________
change bsc3270
Prompted Entry: Changing BSC3270 Terminal Information for Terminal Service
CC0> change
OBJECTS [...bsc3270...]: bsc3270
COMPONENT [module, port, terminal]: terminal
MODULE ADDRESS: 71
PORT NUMBER [1-8]: 1
CONTROL UNIT [1-32]: 1
TERMINAL NUMBER [1-32: +(1-32)]: 1
TEXT TYPE [mixed, upper: +(mixed)]: +
REPORT STATUS AND SENSE MESSAGES [yes, no: +(yes)]:
TERMINAL TYPE [basic, color, extended, c/e: +(basic)]: color
RECEIVE-ONLY? [yes, no: +(no)]: +
ORIGINATING GROUP [up to 8 chars: +(bsco)]: +
PREDEFINED DESTINATION ["none" to delete: +(bschome)]: +
CONNECT-TIME BILLING [on, off: +(off)]: +
BROADCAST PERMISSION [on, off: +(on)]: +
SCREEN SIZE [1920, 2560, 3440, 3564: +(1920)]: +
CALL HOLD [on, off: +(off)]: +
ATTENTION STRING [up to 4 chars or "none": +(%ATT)]: +
ATTENTION ACTION [disconnect, command mode: +(command_mode)]: +
FORWARD DELIVERY ACKNOWLEDGEMENT? [yes, no: +(no)]: +
TERMINAL SECURITY ON? [yes, no: +(no)]: +
TERMINAL NUMBER [1-32: +(1-32)]:
Delete
CC0>
Data Networking Products SYNC8 Module Reference, Issue 2
6-5
________________
delete bsc3270
delete bsc3270
The delete bsc3270 command enables you to delete information regarding a BSC3270
component from the database. All information for lower-level components connected to the
specified component must be deleted before information regarding the specified component can
be deleted.
Before module and port information can be deleted, the module or port must be removed from
service. CUs or terminals do not have to be removed from service before their database entries
can be deleted; however, the port to which each is connected must be removed from service.
Thus, any attached devices are put into the ready-for-service state.
Syntax
You can input delete bsc3270 in prompted or one-line entry.
CC0> delete
OBJECTS [...bsc3270...]: bsc3270
COMPONENT [module, port, cu, terminal]:
For a module, port, cu, or terminal:
MODULE ADDRESS:
For a port:
PORT NUMBER [1-8: +(1-8)]:
For a cu:
PORT NUMBER [1-8]:
If SERVICE TYPE is host:
VIRTUAL CONTROL UNIT [1-32: +(1-32)]:
If SERVICE TYPE is terminal:
CONTROL UNIT [1-32: +(1-32)]:
For a terminal:
PORT NUMBER [1-8]:
If SERVICE TYPE is host:
VIRTUAL CONTROL UNIT [1-32]:
VIRTUAL TERMINAL NUMBER [1-32: +(1-32)]:
If SERVICE TYPE is terminal:
CONTROL UNIT [1-32]:
TERMINAL NUMBER [1-32: +(1-32)]:
Parameters
Refer to the parameter definitions supplied in enter bsc3270.
6-6
Data Networking Products SYNC8 Module Reference, Issue 2
________________
delete bsc3270
Prompted Entry: Deleting BSC3270 Terminal Information
CC0> delete
OBJECTS [...bsc3270...]: bsc3270
COMPONENT [module, port, cu, terminal]: terminal
MODULE ADDRESS: 71
PORT NUMBER [1-8]: 1
CONTROL UNIT [1-32]: 1
TERMINAL NUMBER [1-32: +(1-32)]: 1
CC0>
Prompted Entry: Deleting BSC3270 CU Information
CC0> delete
OBJECTS [...bsc3270...]: bsc3270
COMPONENT [module, port, cu, terminal]: cu
MODULE ADDRESS: 71
PORT NUMBER [1-8]: 1
CONTROL UNIT [1-32: +(1-32)]: 1
CC0>
Prompted Entry: Deleting SYNC8 Port Information
CC0> delete
OBJECTS [...bsc3270...]: bsc3270
COMPONENT [module, port, cu, terminal]: port
MODULE ADDRESS: 71
PORT NUMBER [1-8: +(1-8)]: 1
CC0>
Data Networking Products SYNC8 Module Reference, Issue 2
6-7
________________
delete bsc3270
Prompted Entry: Deleting SYNC8 Module Information
CC0> delete
OBJECTS [...bsc3270...]: bsc3270
COMPONENT [module, port, cu, terminal]: module
MODULE ADDRESS: 71
CC0>
One-line Entries: Deleting BSC3270 component information.
CC0>
CC0>
CC0>
CC0>
6-8
delete bsc3270 terminal 71 1 1 1
delete bsc3270 cu 71 1 1
delete bsc3270 port 71 1
delete bsc3270 module 71
Data Networking Products SYNC8 Module Reference, Issue 2
________________
diagnose bsc3270
diagnose bsc3270
The diagnose bsc3270 command enables you to initiate an off-line or on-line diagnostic test for a
SYNC8 module or port. Off-line diagnostics (off-line) check various parts of the module
hardware. The three types of off-line diagnostics are boot diagnostics, memory tests, and
downloaded diagnostics. The module being tested must be entered in the database and be out of
service.
On-line diagnostics (on-line) check the communications path. The module must be in service and
the port to be tested must be out of service. This command tests one port at a time and affects
service on that port only.
NOTE:
If a VDM is attached to the line when running the local modem or remote modem test,
the Control Computer automatically puts the VDM in the loopback mode. The Control
Computer then runs the vdm ckloop test on the port before and after running either test.
If a message indicating the VDM is stuck in the loopback mode appears while you are
running either test, let the test finish; this procedure typically takes the modem out of
loopback mode. In addition, power problems can cause remote VDMs to become stuck
in loopback mode. Ask the remote user to make sure the switch on the VDM is not in
the loopback position.
Syntax
You can input diagnose bsc3270 in prompted entry only.
CC0> diagnose
OBJECTS [...bsc3270...]: bsc3270
DIAGNOSTIC TYPE [off-line, on-line]:
MODULE ADDRESS:
If DIAGNOSTIC TYPE is on-line:
PORT NUMBER [1-8]:
TEST TYPE: [internal_port, external_port, local_modem,
remote_modem: +(external_port)]:
If a VDM is connected:
TEST TYPE: [internal_port, external_port, local_modem,
remote_modem, vdm_ckloop: +(external_port)]:
CONTINUE TESTING [yes, no: +(yes)]:
Parameters
CONTINUE TESTING
Specifies whether (yes or no) diagnostic testing should be continued.
DIAGNOSTIC TYPE
Specifies if off-line or on-line diagnostics are to be run.
PORT NUMBER
If DIAGNOSTIC TYPE is on-line, a single number from 1 to 8 specifying the port on which
diagnostics are to be run.
Data Networking Products SYNC8 Module Reference, Issue 2
6-9
________________
diagnose bsc3270
Parameters (continued)
TEST TYPE
Specifies the type of diagnostic to be run. Each begins and ends at the Control Computer.
internal_port
This test extends to the USART within the DCE or DTE port being diagnosed. It does
not check the integrity of the interface terminators and receivers.
external_port
This test, which is valid for DCE ports only, extends through the port to an external, 25pin loopback connector. It checks the integrity of the IODB and the interface
terminators and receivers.
local_modem
This test, which is valid for DTE ports only, extends to the port’s local modem. The
local modem must be in the loopback mode.
remote_modem
This test, which is valid for DTE ports only, extends to the port’s remote modem. The
remote modem must be in the loopback mode.
vdm_ckloop
This test, which appears only if a VDM is attached, consists of two parts: the first part
detects if the local (central office) VDM is stuck in the loopback mode; the second part
detects if the remote VDM is stuck in the loopback mode.
For the remaining parameters, refer to the definitions supplied in enter bsc3270.
Prompted Entry: Running BSC3270 On-line Port Diagnostics
CC0> diagnose
OBJECTS [...bsc3270...]: bsc3270
DIAGNOSTIC TYPE [on-line, off-line]: on-line
MODULE ADDRESS: 71
PORT NUMBER [1-8]: 1
TEST TYPE: [internal_port, external_port, local_modem,
remote_modem, vdm_ckloop: +(external_port)]: external_port
94-12-31 12:24:38 NODE=Redqueen
M diagnose bsc3270 on-line 71 1 external_port
Test requires a loop-around connector on port.
Replace port cable with loop-around connector.
CONTINUE TESTING [yes, no: +(yes)]: +
94-12-31 12:26:13 NODE=Redqueen
M diagnose bsc3270 on-line 71 1 external_port
Diagnose completed - test passed.
CONTINUE TESTING [yes, no: +(yes)]: no
CC0>
6-10
Data Networking Products SYNC8 Module Reference, Issue 2
________________
diagnose bsc3270
Prompted Entry: Running SYNC8 Module Off-line Diagnostics
CC0> diagnose
OBJECTS [...bsc3270...]: bsc3270
DIAGNOSTIC TYPE [on-line, off-line]: off-line
MODULE ADDRESS: 71
94-12-31 12:56:28 NODE=Redqueen
M diagnose bsc3270 off-line 71
Boot tests in progress - . . .
94-12-31 12:56:28 NODE=Redqueen
M
Offline diagnostic boot test: PASS
94-12-31 12:56:28 NODE=Redqueen
M
Extended RAM test in progress - . . .
94-12-31 12:56:28 NODE=Redqueen
M
Offline diagnostic memory test: PASS
Diagnostic download in progress - . . .
94-12-31 12:56:28 NODE=Redqueen
M diagnose bsc3270 off-line 71
Offline diagnostic downloaded test:
Inst. Set:
PASS
Timer test:
PASS
Port 1:
PASS
Port 2:
PASS
Port 3:
PASS
Port 4:
PASS
Port 5:
PASS
Port 6:
PASS
Port 7:
PASS
Port 8:
PASS
DIAGNOSTIC COMPLETED
CC0>
Data Networking Products SYNC8 Module Reference, Issue 2
6-11
________________
dmeas bsc3270
dmeas bsc3270
The dmeas bsc3270 command enables you to generate on-demand measurements reports for a
SYNC8 module or component. These reports contain traffic, performance, and utilization
measurements for the specified module or port.
Syntax
You can input dmeas bsc3270 in prompted or one-line entry.
CC0> dmeas
OBJECTS [...bsc3270...] bsc3270
COMPONENT [module, port, terminal]:
MODULE ADDRESS:
For port measurements:
PORT NUMBER [1-8: +(1-8)]:
For terminal measurements:
PORT NUMBER [1-8]:
CU NUMBER [1-32]:
TERMINAL NUMBER [1-32: +(1-32)]:
INTERVAL [current, previous: +(current)]:
Parameters
COMPONENT
Specifies if the component to be entered is a module, port, or terminal.
INTERVAL
Specifies if the on-demand report is to be printed for the current or previous reporting
interval. The current interval includes those measurements accumulated since the previous
scheduled report was generated; or if a report was not scheduled, those measurements
accumulated since the module was last reset. Conversely, the previous interval includes
those measurements accumulated prior to the current interval.
For the remaining parameters, refer to the definitions supplied in enter bsc3270.
6-12
Data Networking Products SYNC8 Module Reference, Issue 2
________________
dmeas bsc3270
Prompted Entry: Displaying BSC3270 Terminal Measurements
CC0> dmeas
OBJECTS [...bsc3270...]: bsc3270
COMPONENT [module, port, terminal]: terminal
MODULE ADDRESS: 71
PORT NUMBER [1-8]: 1
CU NUMBER [1-32]: 1
TERMINAL NUMBER [1-32: +(1-32)]: 1
INTERVAL [current, previous: +(current)]: +
<report output>
One-line Entry/Output: Displaying BSC3270 Terminal Measurements
CC0> dmeas bsc3270 terminal 71 1 1 1 +
94-12-31 16:48:04 NODE=Redqueen
M dmeas bsc3270 terminal 71 1 1 1 current
MODULE ADDRESS: 71
PACKETS
FM NODE
674
PACKETS
TO NODE
373
MODULE ADDRESS: 71
94-12-31
HALF FULL
FIFO INTRPTS
0
16:32 ------> 16:40
BUFFERS
NOT AVAIL
0
PORT: 1
IDLE
94%
MIN
IDLE
94%
SPEED: 9600
PORT
PEAK BUFFERS
PARITY
UTIL
UTIL NOT AVAIL ERRORS
5%
0% 0
0
<-----------RECEIVED--------------------><-----------TRANSMITTED------------>
DATA
MSG
ABNORM TIME DATA
MSG
ABNORM
BYTES CNT NAKS WAKS RVIS EOT
OUTS BYTES CNT NAKS WAKS RVIS EOT
319
50
0
0
0
0
0
7949
177 0
5
0
0
MODULE ADDRESS: 71
TERM NO:
1
RCV MSGS:
0
TRN MSGS:
0
ABNORM SS:
0
CC0>
TERMINAL MEASUREMENTS FOR PORT: 1
CONTROL UNIT: 1
Data Networking Products SYNC8 Module Reference, Issue 2
6-13
________________
dmeas bsc3270
Report Fields
ABNORM EOT
The number of abnormal ends of transmission (received/transmitted).
ABNORM SS
The number of abnormal status and sense messages.
BUFFERS NOT AVAIL
The number of times the module requested buffer space and none was available.
DATA BYTES
The number of data bytes (received/transmitted).
HALF FULL FIFO INTRPTS
The number of half-full, first-in/first-out interrupts the module received during the interval.
IDLE
The average percentage of time the module was idle during the interval.
MIN IDLE
The minimum percentage of time the module was idle during its busiest five-minute
interval.
MODULE ADDRESS
The address of the module for which measurements have been requested.
MSG CNT
The message count not including retransmission (received/transmitted).
NAKS
The number of negative acknowledgements (received/transmitted).
PACKETS FM NODE
The number of packets received from the node.
PACKETS TO NODE
The number of packets sent to the node.
PARITY ERRORS
The number of envelopes received and discarded with parity errors for that line.
PEAK UTIL
The peak five-minute utilization.
PORT UTIL
The port utilization percentage—the percentage of the total number of characters
sent/received by the port for the interval. This value is calculated by taking the ratio of the
total number of characters sent and received by the port, to the maximum number of
characters that could be received and sent by the port during the interval.
RCV MSGS
The number of messages received, not including retransmissions.
6-14
Data Networking Products SYNC8 Module Reference, Issue 2
________________
dmeas bsc3270
RVIS
The number of reverse interrupts (received/transmitted).
TIME OUTS
The number of timeouts (received).
TRN MSGS
The number of messages transmitted, not including retransmissions.
WAKS
The number of wait acknowledgements before the transaction is positive
(received/transmitted).
Data Networking Products SYNC8 Module Reference, Issue 2
6-15
________________
dstat bsc3270
dstat bsc3270
The dstat bsc3270 command enables you to display hardware and software status information
regarding a SYNC8 module and components.
Syntax
You can input dstat bsc3270 in prompted or one-line entry.
CC0> dstat
OBJECTS [...bsc3270...] bsc3270
COMPONENT [module, port, terminal: +(module)]:
MODULE ADDRESS:
For a port:
PORT NUMBER [1-8: +(1-8)]:
For a terminal:
PORT NUMBER [1-8]:
CU NUMBER [1-32]:
TERMINAL NUMBER [1-32: +(1-32)]:
DETAIL [low, high: (+low)]:
Parameters
COMPONENT
Specifies if the component to be entered is a module, port, or terminal.
DETAIL
Specifies if the output is to show a limited amount of information (low detail) or more
information (high detail).
For the remaining parameters, refer to the definitions supplied in enter bsc3270.
Prompted Entry: Displaying High Detail BSC3270 Terminal Status
CC0> dstat
OBJECTS [...bsc3270...]: bsc3270
COMPONENT [module, port, terminal: +(module)]: terminal
MODULE ADDRESS: 71
PORT NUMBER [1-8]: 1
CU NUMBER [1-32]: 1
TERMINAL NUMBER [1-32: +(1-32)]: 1
DETAIL [low, high: (+low)]: high
<report output>
6-16
Data Networking Products SYNC8 Module Reference, Issue 2
________________
dstat bsc3270
One-line Entry/Output: Displaying High Detail BSC3270 Terminal Status
CC0> dstat bsc3270 terminal 71 1 1 1 high
94-12-31 07:50:24 NODE=Redqueen
M dstat bsc3270 terminal 71 1 1 1 high
********************************* MODULE 71 *********************************
MODULE TYPE
SERVICE STATE
HARDWARE ERROR COUNT SERIAL NUMBER
sync8
in service
1
1182
LAST HARDWARE ALARM
Module was reset 94-12-31 07:46
LAST SOFTWARE ALARM
none
ONLINE ENABLED
yes
yes
-------------------------------- HIGH DETAIL -------------------------------MODULE FIFO
FM NODE FM NODE SANITY
RESET
RESET
PARITY OVERFLO ERROR
1
0
0
0
0
EXPECT FULL
EMPTY
ACTUAL ACTUAL EXPECT EXPECT
TYPE
PACKETS PACKETS STAT1
STAT2
STAT1
STAT2
sync8
180
0
1
0
1
0
MEMORY
STACK
END
END
END
MEMORY
START
TOTAL
END
SPACE
BSS
DATA
TEXT
LEFT
BUFS
BUFMEM
0x80000 0x2000
0x45e4e 0x3e412 0x2e728 0x15e3a 0x69220 0x12de0
BILLREC SOFTWARE NUMBER TIMEOUT TIMEOUT TRUNC
AVG RSP
DROPPED ALARMS
TRANS
MOD
SYNCM
TRANS
TIME (msec)
0
0
44
0
0
0
22
RANGE
BAD
ERRORS* PACKETS*
14
2
94-12-31 15:30:45 NODE=Redqueen
M dstat bsc3270 terminal 71 1 1 1 high
***************************** MODULE 71 PORT 1 *****************************
PORT
EXPECT
ACTUAL
OPERATING
TYPE
SRVC STATE
SRVC STATE
STATE
BSC host
in service
in service
up
DCD
DTR
RTS
CTS
DSR
on
on
off
on
on
94-12-31 15:30:45 NODE=Redqueen
M dstat bsc3270 terminal 71 1 1 1 high
-------------------------------- HIGH DETAIL -------------------------------SYNC
RXCHAR
CHAN
CHAN
CHAN
HUNT
AVAIL
RCV
XMT
EXT ST
yes
no
yes
yes
yes
VECTOR
TX
TX CRC
RX
RX CRC
GENERATOR
STATUS
ENABLE
ENABLE
ENABLE
ENABLE
ENABLE
yes
no
no
yes
no
yes
PARITY
CRC/FRM
RCV FIFO TX
TX
ERR
ERR
OVF
UN/EOM
BUF EMPTY
no
no
no
yes
yes
Data Networking Products SYNC8 Module Reference, Issue 2
6-17
________________
dstat bsc3270
One-line Entry/Output (continued)
************************** MODULE 71 PORT 1 CU 1 **************************
CU
EXPECT
ACTUAL
OPERATING
TYPE
SRVC STATE
SRVC STATE
STATE
BSC host
in service
in service
down
******************************* BSC TERMINAL ********************************
TERM EXPECT
ACTUAL
OPERATING
NO
SRVC STATE
SRVC STATE
STATE
AVAILABLE
1
in service
in service
down
no
CC0>
Report Fields
References made to alarms refer to those alarms messages cited in the Data Networking Products
Messages Reference.
ACTUAL SRVC STATE
According to the module, the actual service state of the port.
ACTUAL STAT1
The actual value of the hardware status byte of the most currently received status packet for
the module. The actual and expected values of STAT1 can differ.
ACTUAL STAT2
The actual value of the software status byte of the most currently received status packet for
the module. The actual and expected values of STAT2 can differ.
AVAILABLE
Gives the current operating state of the terminal according to the BSC3270 module.
The possible values for BHIM are:
yes—the virtual terminal is in service and the FEP has polled it in the last 8 minutes.
no—the virtual terminal is not in service or the FEP has not polled it in the last 8
minutes.
The possible values for BTIM are:
yes—the physical terminal is in service and it did respond to the latest select
no—the physical terminal is not in service or it did not respond to the latest select
(within the last few minutes)
AVG RSP TIME (msec)
The average response time which is derived by dividing the total module response time by
the total number of module transactions.
BAD PACKETS
For ECPU Systems only, the count of packets with envelope parity errors transmitted by the
module and detected by the Eswitch. To determine if the module is defective, run
diagnostics.
6-18
Data Networking Products SYNC8 Module Reference, Issue 2
________________
dstat bsc3270
Report Fields (continued)
BILLREC DROPPED
The number of billing records dropped by syncmaint. See BILLING CANNOT ALLOCATE
CONTROLLER alarm.
CHAN EXT ST
Indicates if (yes or no) external status interrupts are enabled on the SYNC8 port USART.
This allows the USART to generate an interrupt when EIA lead transitions occur.
CHAN RCV
Indicates if (yes or no) receive interrupts are enabled on the SYNC8 port USART. This
allows the USART to generate an interrupt when data is received.
CHAN XMT
Indicates if (yes or no) transmit interrupts are enabled on the SYNC8 port USART. This
allows the USART to generate an interrupt when data is transmitted.
CRC/FRM ERR
Indicates if (yes or no) the SYNC8 port USART detected a CRC or framing error.
CTS
The status of the EIA lead clear to send is on or off for the port.
CU TYPE
The type of service to which the CU is connected.
DCD
The status of the EIA lead data carrier detect is on or off for the port. If the port is
configured for half duplex, this field shows an n/a.
DSR
The status of the EIA lead data set ready is on or off for the port.
DTR
The status of the EIA lead data terminal ready is on or off for the port.
EMPTY PACKETS
The number of empty status packets received, which indicates the module is not physically
present in the shelf slot. Contrast with FULL PACKETS. See EMPTY SLOT alarm.
ENABLED
According to status packet data, shows a status of yes if the module mode switch is in the
ENABLE position.
END BSS
The end of BSS for the module.
END DATA
The end of data for the module.
Data Networking Products SYNC8 Module Reference, Issue 2
6-19
________________
dstat bsc3270
Report Fields (continued)
END TEXT
The end of text for the module.
EXPECT SRVC STATE
According to the database contents, the expected service state of the port.
EXPECT STAT1
The expected value of the hardware status byte for the module.
EXPECT STAT2
The expected value of the software status byte for the module.
EXPECT TYPE
The expected hardware type in the shelf slot. For in-service modules, this field shows
administrator-supplied data. For out-of-service modules, this field shows status packet
data.
FIFO RESET
A count of FIFO resets (a hardware synchronization problem) on the module. See FIFO
RESET alarm.
FM NODE OVERFLO
The difference between the rate at which information arrives at a module and the rate at
which the subscriber processes this information. (Overflow errors can occur during typical
operation and do not necessarily indicate a problem. See FROM BUS OVERFLOW alarm.)
FM NODE PARITY
The number of packets that have been sent to or received from the node with parity errors.
FULL PACKETS
The number of full status packets received, which indicates the module is physically present
in the shelf slot. Contrast with EMPTY PACKETS.
GENERATOR ENABLE
Indicates if (yes or no) the baud rate generator for the port is enabled. The baud rate
generator provides clocking for the transmitter and receiver on DCE ports.
HARDWARE ERROR COUNT
An approximate sum of module errors detected since its last reboot. Counts of 3 or 4 are
typical; higher counts probably indicate some problem.
LAST HARDWARE ALARM
According to status packet data, the last alarm for the module. This data is not stored
between Control Computer reboots.
LAST SOFTWARE ALARM
The text, date, and time of the last alarm the module issued by and for itself. This data is
not stored between module or Control Computer reboots.
6-20
Data Networking Products SYNC8 Module Reference, Issue 2
________________
dstat bsc3270
Report Fields (continued)
MEMORY END
The end of memory for the module.
MEMORY LEFT
The amount of remaining memory for the module.
MODULE RESET
The number of module resets. (Resets can occur during normal operation.) See MODULE
WAS RESET alarm.
MODULE TYPE
According to status packet data, the type of module present. This field, which is initialized
to empty, does not reflect the module type specified with enter and delete.
NUMBER TRANS
The number of transactions processed since the last reboot.
ONLINE
According to status packet data, shows yes if the green LED on the module is on.
OPERATING STATE
Gives the current state of operation of the port, control unit or terminal.
Port Section:
Up means the FEP or control units are physically connected to the BHIM or BTIM.
This is determined by checking the EIA leads.
Down means the FEP or control units are not physically connected to the BHIM or
BTIM. This is determined by checking the EIA leads.
Control Unit Section:
On a BHIM, up means the virtual control unit has been polled by the FEP within the
last 8 minutes.
On a BHIM, down means the virtual control unit has not been polled within the last 8
minutes.
On a BTIM, up means the physical control unit has responded to a poll within the last
minute.
On a BTIM, down means the physical control unit did not respond to the last poll
(within the last minute).
Terminal Section:
There are 10 possible states of the terminal according to the control unit:
down: indicates the terminal is unavailable for call origination or reception.
pending down: indicates the terminal is going down.
Data Networking Products SYNC8 Module Reference, Issue 2
6-21
________________
dstat bsc3270
Report Fields (continued)
channel not connected: indicates the terminal is available for call origination or
reception.
pending idle: indicates the external leads are down.
pending outcall for device: indicates an outgoing call is pending.
pending incoming call: indicates an incoming call is pending.
control session with cc: indicates a control session with the control computer.
pending control session with cc: indicates a pending control session the with control
computer.
data transfer state indicates the connection is up.
pending talking indicates the connection is almost up.
PARITY ERR
Indicates if (yes or no) the SYNC8 port USART detected a parity error.
PORT TYPE
Indicates if the type of service connection the port provides is that of a terminal or host.
RANGE ERRORS
For ECPU Systems only, the count of packets transmitted by the module on a channel that is
beyond the limit for which the module is configured. Bad packet counts might be attributed
to a defective module that is corrupting the address field of the packet or to a channel
configuration mismatch on the two sides of the trunks or CPM. To determine if the module
is defective, run module diagnostics; to determine if a configuration mismatch has occurred,
review the module configuration.
RCV FIFO OVF
Indicates if (yes or no) the SYNC8 port USART detected a receiver FIFO overflow for the
port.
RTS
The status of the EIA lead request to send is on or off for the port.
RXCHAR AVAIL
Indicates if (yes or no) a received character is available from the SYNC8 port USART.
RX CRC ENABLE
Indicates if (yes or no) the receiver cyclic redundancy check is enabled for the port.
RX ENABLE
Indicates if (yes or no) the receiver is enabled for the port.
SANITY ERROR
See MODULE MALFUNCTION alarm.
SERIAL NUMBER
The factory-encoded number that appears on all modules that access the backplane—that is,
6-22
Data Networking Products SYNC8 Module Reference, Issue 2
________________
dstat bsc3270
have a switch and an LED. Maintaining records with these numbers can help track circuit
pack vintages.
SERVICE STATE
Indicates if the module is currently in service (via restore); oos,manual (out of service via
remove); oos,fault,auto (out of service via the alarm system); or rfs (ready for service).
SOFTWARE ALARMS
The number of module alarms reported since the last reboot.
STACK SPACE
The amount of stack space available on the module.
START BUFS
The start of buffer space for the module.
SYNC HUNT
Indicates if the BSC3270 synchronized hunt status is enabled (yes) or disabled (no) for the
port. If yes then the receiver is searching for the beginning of a frame.
TERM NO
The number(s) of the terminal(s) connected to a CU.
TIMEOUT MOD
The number of transactions that timed out at the module since the last reboot.
TIMEOUT SYNCM
The number of transactions that were returned from the module, but were timed out by
syncmaint, since the last reboot.
TOTAL BUFMEM
The amount of buffer memory available on the module.
TRUNC TRANS
The number of truncated transactions that occurred since the last reboot.
TX BUF EMPTY
Indicates if (yes or no) the transmit buffer is empty for the port.
TX CRC ENABLE
Indicates if (yes or no) the transmitter cyclic redundancy check is enabled for the port.
TX ENABLE
Indicates if (yes or no) the transmitter is enabled for the port.
TX UN/EOM
Indicates if the SYNC8 port USART terminates the current frame as an underrun (yes) or
provides proper CRC for data transmitted when the transmit buffer bus is empty.
VECTOR STATUS
Indicates if (yes or no) the vector returned on an interrupt is variable for the type of interrupt
which occurred.
Data Networking Products SYNC8 Module Reference, Issue 2
6-23
________________
enter bsc3270
enter bsc3270
The enter bsc3270 command enables you to add information regarding a SYNC8 module and its
components into the database.
Syntax
You can input enter bsc3270 in prompted entry only. The sequence of prompts depends on your
response to the COMPONENT and SERVICE TYPE prompts. The defaults are shown in
parentheses.
CC0> enter
OBJECTS [...bsc3270...]: bsc3270
COMPONENT [module, port, cu, terminal]:
MODULE ADDRESS:
For a module:
DOWNLOAD SERVER [+(controller)]:
If DOWNLOAD SERVER is controller:
SOFTWARE VERSION [+(standard)]:
If DOWNLOAD SERVER is other than controller:
SOFTWARE VERSION:
NUMBER OF USER CHANNELS [1-128: +(100)]:
Command loops to MODULE ADDRESS prompt.
For a port:
PORT NUMBER [1-8: +(1-8)]:
COMMENT [up to 60 chars double quoted]:
SERVICE TYPE [host or terminal]:
If SERVICE TYPE is host:
HOST TYPE [btam, vtam, other]:
MESSAGE CHAINING [yes, no: +(yes)]:
If SERVICE TYPE is terminal:
AT&T VDM ON THIS PORT [yes, no: +(no)]:
CODE SET [asciicrc, asciiodd, ebcdic, crc2, odd2, ebc2: +(ebcdic)]:
PORT DUPLEX [half, full: +(full)]:
If SERVICE TYPE is host:
BAUD RATE [1200, 2400, 4800, 9600, 19200, 56k: +(9600)]:
If SERVICE TYPE is terminal:
BAUD RATE [1200, 2400, 4800, 9600, 19200: +(9600)]:
If SERVICE TYPE is terminal:
START UP [standard, null_write: +(standard)]:
Command loops to PORT NUMBER prompt.
6-24
Data Networking Products SYNC8 Module Reference, Issue 2
________________
enter bsc3270
Syntax (continued)
For a cu:
PORT NUMBER [1-8]:
If SERVICE TYPE is host:
VIRTUAL CONTROL UNIT [1-32: +(1-32)]:
If SERVICE TYPE is terminal:
CONTROL UNIT [1-32: +(1-32)]:
INITIAL SERVICE STATE [in, out: +(out)]:
Command loops to CONTROL UNIT/VIRTUAL CONTROL UNIT prompt.
For a terminal:
PORT NUMBER [1-8]:
If SERVICE TYPE is host:
VIRTUAL CONTROL UNIT [1-32]:
VIRTUAL TERMINAL NUMBER [1-32: +(1-32)]:
If SERVICE TYPE is terminal:
CONTROL UNIT [1-32]:
TERMINAL NUMBER [1-32: +(1-32)]:
TEXT TYPE [mixed, upper: +(mixed)]:
REPORT STATUS AND SENSE MESSAGE [yes, no: +(yes)]:
TERMINAL TYPE [basic, color, extended, c/e: +(basic)]:
RECEIVE-ONLY? [yes, no: +(no)]:
If SERVICE TYPE is host and RECEIVE-ONLY? is no:
SCREEN SIZE [1920, 2560, 3440, 3564: +(1920)]:
FORWARD DELIVERY ACKNOWLEDGEMENT? [yes, no: +(no)]:
If SERVICE TYPE is terminal and RECEIVE-ONLY? is no:
TERMINAL SECURITY ON? [yes, no: +(no)]:
If SERVICE TYPE is host:
RECEIVING GROUP [up to 8 chars]:
LOGOFF METHOD [disc, none, sas, test, other: +(none)]:
If LOGOFF METHOD is other:
LOGOFF SEQUENCE IDENTIFIER [up to 6 chars]:
If SERVICE TYPE is terminal:
ORIGINATING GROUP [up to 8 chars]:
If SERVICE TYPE is terminal and RECEIVE ONLY? is yes:
PREDEFINED DESTINATION:
If SERVICE TYPE is terminal and RECEIVE-ONLY? is no:
PREDEFINED DESTINATION [+(none)]:
CONNECT-TIME BILLING [on, off: +(off)]:
BROADCAST PERMISSION [on, off: +(on)]:
If SERVICE TYPE is terminal and RECEIVE-ONLY? is no:
SCREEN SIZE [1920, 2560, 3440, 3564: +(1920)]:
CALL HOLD [on, off: +(off)]:
ATTENTION STRING [up to 4 chars, "none": +(%ATT)]:
Data Networking Products SYNC8 Module Reference, Issue 2
6-25
________________
enter bsc3270
Syntax (continued)
If ATTENTION STRING is not none:
ATTENTION ACTION [disconnect, command_mode: +(command_mode)]:
FORWARD DELIVERY ACKNOWLEDGEMENT? [yes, no: +(no)]:
For SERVICE TYPEs host and terminal:
INITIAL SERVICE STATE [in, out: +(out)]:
Command loops to TERMINAL NUMBER/VIRTUAL TERMINAL NUMBER prompt.
Parameters
ATTENTION ACTION
If the terminal is originating only and ATTENTION STRING is not none, specifies whether
the attention signal can disconnect the terminal session or put the terminal in
command_mode.
ATTENTION STRING
For originating terminals only, a string of 1 to 4 characters which sets the attention signal for
the terminal, or the word none meaning no attention signal is to be set.
BAUD RATE
Specifies the particular speed in which the port is to communicate with its attached device.
See Syntax for specific speeds.
BROADCAST PERMISSION
Specifies whether (on or off) the terminal should receive network broadcast messages. For
display terminals, the option should be on. For printers and receive-only terminals, the
option should be off.
CALL HOLD
If RECEIVE-ONLY? is no for a terminal, specifies whether the call hold option should be on
or off.
CODE SET
If COMPONENT is port and SERVICE TYPE is terminal, specifies the transmission code
used by attached devices to be asciicrc, asciiodd, ebcdic, crc2, odd2, or ebc2. Entry of crc2
configures the port for the asciicrc code set and two end-of-transmissions (EOTs); entry of
odd2 configures the port for the asciiodd code set and two EOTs; entry of ebc2 configures
the port for the ebcdic code set and two EOTs. If crc2, odd2, or ebc2 are selected, the select
sequence sent by the BTIM will begin and end with an EOT. Otherwise, the select sequence
will only begin with an EOT.
COMMENT
An optional string of 1 to 60 characters, enclosed in double quotation marks, that contains
needed administrative information.
COMPONENT
Specifies whether the component to be entered is a module, port, cu, or terminal.
6-26
Data Networking Products SYNC8 Module Reference, Issue 2
________________
enter bsc3270
Parameters (continued)
CONNECT-TIME BILLING
Specifies whether (on or off) billing information (the count of packets sent to/from the
device) is to be logged for the port and reported to the billing process.
CU NUMBER/VIRTUAL CU NUMBER
A number from 1 to 32 specifying the active control unit for the port. Ranges and
sequences of CU numbers are not allowed when entering a terminal. (Device numbering for
the node differs from the conventional station or device numbering scheme. The following
table correlates the node CU or terminal numbers with ASCII/EBCDIC poll codes and with
the conventional station or device numbering schemes.)
_______________________________________________________________
 Node CU or

 Conventional Station or 
Poll Code
 Terminal Number  ASCII

EBCDIC 
Device Number




_______________________________________________________________
_______________________________________________________________






 space  space


1
0

 A


2
A
1


 B



3
B
2





4
C
3

 C



5
D
4

 D




 E


6
E
5


 F



7
F
6





8
G
G
7





9
H
8

 H







10
I
I
9





11
[
¢
10






12
.
.
11





13
<
12

 <



14
(
(
13






 +


15
+
14






16
!

15





17
&
16

 &



18
J
J
17






 K


19
K
18


 L


20
L
19


 M



21
M
20





22
N
21

 N



23
O
22

 O




 P


24
P
23


 Q



25
Q
24





26
R
25

 R



27
]
!
26






 $


28
$
27


 *


29
*
28






30
)
)
29





31
;
;
30





32
ˆ
¬
31
_______________________________________________________________




Data Networking Products SYNC8 Module Reference, Issue 2
6-27
________________
enter bsc3270
Parameters (continued)
DOWNLOAD SERVER
If COMPONENT is module, specifies the source of the software to be downloaded to the
module. It must be a valid service address or the local controller.
FORWARD DELIVERY ACKNOWLEDGEMENT
Specifies if (yes or no) delivery acknowledgements are to be forwarded from the SYNC8
module to its session partner.
HOST TYPE
Specifies if the host is that type associated with the Virtual Telecommunications Access
Method (vtam), the Basic Telecommunications Access Method (btam), or another
telecommunications access method (other).
INITIAL SERVICE STATE
Specifies the initial service state of the component (cu or terminal) upon completion of the
database entry to be in or out of service. A cu or terminal initially put into service goes into
the ready-for-service (rfs) state because the port to which it is connected has to be out of
service before executing enter bsc3270.
IS AN AT&T VDM CONNECTED TO THIS LINE
If SERVICE TYPE is terminal, specifies if (yes or no) an AT&T Voice/Data Multiplexer
(VDM) is connected to the line.
LOGOFF METHOD
If SERVICE TYPE is host, specifies the logoff method to be used when a session is broken
with a terminal without a PDD. If no logoff sequence is specified, the session to the host
stays up after the user disconnects. The next user who connects will get the same session.
This can be a security problem.
Specified at BHIM, the logoff sequence is sent to the host either when the call goes down or
when a new call comes up. There are five types:
disc (disconnect)
For btam hosts, the Control Computer reads all messages queued for the terminal before
allowing another terminal to log on in the same slot. The module discards the
messages.
When a new call comes up, 22 messages are sent to the host. These messages will cause
the host to drain all messages in its output queue for that particular device.
none (do nothing)
No indication of a break in the session is sent to the host. Nothing is sent.
sas (status and sense)
When a call comes down, the Intervention Required (x2026, SP &) status
and sense message is sent. When a new call comes up, the Device End (x4220, B
SP) status and sense message is sent indicating that the device is now available.
6-28
Data Networking Products SYNC8 Module Reference, Issue 2
________________
enter bsc3270
test (test request)
When a new call comes up, a test request message is generated. The format is: SOH, %,
/, STX, SBA, SPACE, SPACE, SPA DA, ETX.
For vtam hosts running special applications programs that support the ‘test’ message, a
test request message is sent to the host containing the terminal ID. Special host
processing clears the terminating terminal’s message queue. The host must be
programmed to interpret this test sequence and then to log off the application in order to
avoid further problems.
other
A customized logoff sequence is needed and specified in the LOGOFF SEQUENCE
IDENTIFIER prompt.
LOGOFF SEQUENCE IDENTIFIER
If SERVICE TYPE is host and LOGOFF METHOD is other, a string of 1 to 6 characters used
to identify a customized logoff sequence to be used each time a virtual terminal is
disconnected. See enter logoff in this chapter.
MESSAGE CHAINING
If SERVICE TYPE is host, specifies if (yes or no) the port is to receive chained messages
from the host. Data throughput is increased when chained messages are not expected. This
capability is host dependent and should be set appropriately.
MODULE ADDRESS
A number identifying the address of the SYNC8 module. If the module is installed directly
into the node, the address is <module>. Where: module is the node slot number the SYNC8
occupies.
If the SYNC8 is installed in a concentrator, the address is <concentrator/module>. Where:
concentrator is the node slot number that the LIM, which connects the concentrator to the
module, occupies; and module is a number indicating the BNS-2000 MPC slot number the
SYNC8 occupies.
Multiple module address entries can be specified when adding modules; single address
entries must be specified when adding ports, CUs, or terminals.
NUMBER OF USER CHANNELS
If COMPONENT is module, a number from 1 to 128 that specifies the number of active user
channels to be distributed to module ports. This number does not include overhead
channels, and cannot be decreased below the highest channel number assigned to a device.
ORIGINATING GROUP
A string of 1 to 8 characters specifying the originating group to which the physical terminal
belongs.
PORT DUPLEX
If SERVICE TYPE is terminal, specifies the port type as full or half duplex.
Data Networking Products SYNC8 Module Reference, Issue 2
6-29
________________
enter bsc3270
PORT NUMBER
A number from 1 to 8 specifying a port to be administered. Multiple port number entries
can be specified when adding ports; single port number entries must be specified when
adding CUs or terminals.
NOTE:
If you are using an I/O board with a V.35 connector and a 50-pin connector, you
can only enter ports 1 to 4, even though the software does accept ports 5 to 8.
(These ports cannot be put into service.)
PREDEFINED DESTINATION
If RECEIVE-ONLY? is yes, a string of 1 to 72 characters specifying a service address and,
optionally, a physical address to which the terminal is to connect automatically when put
into service. If RECEIVE-ONLY? is no, this string is optional.
RECEIVE-ONLY?
Specifies if (yes or no) the terminal is to receive data only. If the device is a printer, this
parameter must be yes.
RECEIVING GROUP
A string of 1 to 8 characters specifying the receiving group to which the virtual terminal
belongs.
REPORT STATUS AND SENSE
Specifies if (yes or no) the terminal is to receive SSM alarms.
SCREEN SIZE
Specifies the total number of characters displayed on a terminal. A 1920, 2560, or 3440
character screen provides a screen width of 80 characters; a 3564 character screen provides a
screen width of 132 characters.
SERVICE TYPE
Specifies if the type of service connection to be provided on the port is that of terminal or
host. All ports on the same module must provide the same service.
SOFTWARE VERSION
If COMPONENT is module, a string of 1 to 14 characters specifying the software version
filename to be downloaded to the module. If DOWNLOAD SERVER is controller, enter
standard as the filename. If DOWNLOAD SERVER is not controller, enter the filename of a
valid software release.
START-UP
If COMPONENT is port and SERVICE TYPE is terminal, specifies the start-up sequence
(standard or null_write) to be used to query devices so their physical existence can be
determined.
Users of UBLAN (Ungermann-Bass Local Area Network) equipment should use null_write
for Start-up.
6-30
Data Networking Products SYNC8 Module Reference, Issue 2
________________
enter bsc3270
The start-up sequence is executed:
When a port is restored to service
When a printer terminal device is restored to service
Periodically the BTIM will query field terminals (for example, power on the Cluster
Control Unit is off) to see if they are available. If these terminals respond (for example,
power is turned on), the BTIM will send them the start-up sequence.
The standard start-up sequence is:
1. Each device is issued a BISYNC select. A select is used by the control station to
indicate to the tributary that it has something to send.
2. If the device is present, it will respond with an ACK. This indicates that it is ready to
receive.
3. The BTIM will respond with an EOT, indicating that it really had nothing to send.
The null_write start-up sequence is:
1. Each device is issued a BISYNC select.
2. If the device is present, it will respond with an ACK.
3. The BTIM will respond with the following Bisync Data Frame:
STX,ESC, 1, NULL, ETX
(This is a write command with a WCC of 0 and no data. Upon receiving this, a
printer will not print anything and a video display terminal will not display
anything. Keyboard status is unaffected.)
4. The UBLAN responds with ACK.
5. The BTIM responds with EOT.
TERMINAL NUMBER/VIRTUAL TERMINAL NUMBER
A number from 1 to 32 specifying the active channel that a physical or virtual terminal
occupies. See the parameter definition for CU NUMBER.
TERMINAL TYPE
Specifies that the type of terminal attached to the CU is a basic terminal, a color terminal
(one with color display), an extended terminal (one with programmed symbols and/or
extended highlighting features or functions), or a c/e terminal (one with color and extended
features/functions).
TERMINAL SECURITY ON
yes specifies the BTIM is to respond to a received Device Available Status and Sense
Message (B, SP) from a non-Receive Only device when there is no pending error condition
as indicated by a prior Status and Sense Message. When yes is entered, the Status and Sense
Message will cause the BTIM to take down the user call.
Data Networking Products SYNC8 Module Reference, Issue 2
6-31
________________
enter bsc3270
TEXT TYPE
Specifies whether the type of text to be output is uppercase and lowercase (mixed) or just
uppercase (upper).
Prompted Entry: Entering SYNC8 Module Information
CC0> enter
OBJECTS [...bsc3270...]: bsc3270
COMPONENT [module, port, cu, terminal]: module
MODULE ADDRESS: 70,71
DOWNLOAD SERVER [+(controller)]: +
SOFTWARE VERSION [+(standard)]: +
NUMBER OF USER CHANNELS [1-128: +(100)]: +
MODULE ADDRESS:
Delete
CC0>
Prompted Entry: Entering SYNC8 Port Information for Host Service
CC0> enter
OBJECTS [...bsc3270...]: bsc3270
COMPONENT [module, port, cu, terminal]: port
MODULE ADDRESS: 70
PORT NUMBER [1-8: +(1-8)]: 1
COMMENT [up to 60 chars double quoted]:
"host service"
SERVICE TYPE [host or terminal]: host
HOST TYPE [btam, vtam, other]: btam
MESSAGE CHAINING [yes, no: +(yes)]: +
CODE SET [asciicrc, asciiodd, ebcdic: +(ebcdic)]: +
PORT DUPLEX [half, full: +(full)]: +
BAUD RATE [1200, 2400, 4800, 9600, 19200, 56k: +(9600)]: +
PORT NUMBER [1-8: +(1-8)]:
Delete
CC0>
Prompted Entry: Entering BSC3270 Virtual CU Information for Host Service
CC0> enter
OBJECTS [...bsc3270...]: bsc3270
COMPONENT [module, port, cu, terminal]: cu
MODULE ADDRESS: 70
PORT NUMBER [1-8]: 1
VIRTUAL CONTROL UNIT [1-32: +(1-32)]: 1
INITIAL SERVICE STATE [in, out: +(out)]: +
VIRTUAL CONTROL UNIT [1-32: +(1-32)]:
Delete
CC0>
6-32
Data Networking Products SYNC8 Module Reference, Issue 2
________________
enter bsc3270
Prompted Entry: Entering BSC3270 Virtual Terminal Information for Host Service
CC0> enter
OBJECTS [...bsc3270...]: bsc3270
COMPONENT [module, port, cu, terminal]: terminal
MODULE ADDRESS: 70
PORT NUMBER [1-8]: 1
VIRTUAL CONTROL UNIT [1-32]: 1
VIRTUAL TERMINAL NUMBER [1-32: +(1-32)]: 1
TERMINAL TYPE [basic, color, extended, c/e: +(basic)]: +
RECEIVE-ONLY? [yes, no: +(no)]: +
SCREEN SIZE [1920, 2560, 3440, 3564: +(1920)]: 3564
FORWARD DELIVERY ACKNOWLEDGEMENT? [yes, no: +(no)]: +
TERMINAL SECURITY ON? [yes, no: +(no)]: +
RECEIVING GROUP [up to 8 chars]: bscr
LOGOFF METHOD [disc, none, sas, test, other: +(none)]: +
INITIAL SERVICE STATE [in, out: +(out)]: +
VIRTUAL TERMINAL NUMBER [1-32: +(1-32)]:
Delete
CC0>
Prompted Entry: Entering SYNC8 Port Information for Terminal Service
CC0> enter
OBJECTS [...bsc3270...]: bsc3270
COMPONENT [module, port, cu, terminal]: port
MODULE ADDRESS: 71
PORT NUMBER [1-8: +(1-8)]: 1
COMMENT [up to 60 chars double quoted]:
"terminal service"
SERVICE TYPE [host or terminal]: terminal
AT&T VDM ON THIS PORT [yes, no: +(no)]: +
CODE SET [asciicrc, asciiodd, ebcdic, crc2, odd2, ebc2: +(ebcdic)]: +
PORT DUPLEX [half, full: +(full)]: +
BAUD RATE [1200, 2400, 4800, 9600, 19200: +(9600)]: +
START-UP [standard, null-write: +(standard)]: +
PORT NUMBER [1-8: +(1-8)]:
Delete
CC0>
Data Networking Products SYNC8 Module Reference, Issue 2
6-33
________________
enter bsc3270
Prompted Entry: Entering BSC3270 CU Information for Terminal Service
CC0> enter
OBJECTS [...bsc3270...]: bsc3270
COMPONENT [module, port, cu, terminal]: cu
MODULE ADDRESS: 71
PORT NUMBER [1-8]: 1
CONTROL UNIT [1-32: +(1-32)]: 1
INITIAL SERVICE STATE [in, out: +(out)]: +
CONTROL UNIT [1-32: +(1-32)]:
Delete
CC0>
Prompted Entry: Entering BSC3270 Terminal Information for Terminal Service
CC0> enter
OBJECTS [...bsc3270...]: bsc3270
COMPONENT [module, port, cu, terminal]: terminal
MODULE ADDRESS: 71
PORT NUMBER [1-8]: 1
CONTROL UNIT [1-32]: 1
TERMINAL NUMBER [1-32: +(1-32)]: 1
TEXT TYPE [mixed, upper: +(mixed)]: +
REPORT STATUS AND SENSE MESSAGES [yes, no: +(yes)]:
TERMINAL TYPE [basic, color, extended, c/e: +(basic)]: +
RECEIVE-ONLY? [yes, no: +(no)]: +
ORIGINATING GROUP [up to 8 chars]: bsco
PREDEFINED DESTINATION [+(none)]: bschome
CONNECT-TIME BILLING [on, off: +(off)]: +
BROADCAST PERMISSION [on, off: +(on)]: +
SCREEN SIZE [1920, 2560, 3440, 3564: +(1920)]: +
CALL HOLD [on, off: +(off)]: +
ATTENTION STRING [up to 4 chars or "none": +(%ATT)]: +
ATTENTION ACTION [disconnect, command_mode: +(command_mode)]: +
FORWARD DELIVERY ACKNOWLEDGEMENT? [yes, no: +(no)]: +
TERMINAL SECURITY ON? [yes, no: +(no)]: +
INITIAL SERVICE STATE [in, out: +(out)]: +
TERMINAL NUMBER [1-32: +(1-32)]:
Delete
CC0>
6-34
Data Networking Products SYNC8 Module Reference, Issue 2
________________
remove bsc3270
remove bsc3270
The remove bsc3270 command enables you to take a SYNC8 module and/or its components out
of service.
Syntax
You can input remove bsc3270 in prompted or one-line entry.
CC0> remove
OBJECTS [...bsc3270...]: bsc3270
COMPONENT [module, port, cu, terminal]:
For a module, port, cu, or terminal:
MODULE ADDRESS:
For a port, cu, or terminal:
PORT NUMBER [1-8]:
For a cu or terminal:
CU NUMBER [1-32: +(1-32)]:
For a terminal:
TERM NUMBER [1-32: +(1-32)]:
Parameters
CU NUMBER
A number from 1 to 32 specifying a physical control unit for the port.
TERM NUMBER
A number from 1 to 32 specifying an active channel that a physical terminal occupies.
For the remaining parameters, refer to the definitions supplied in enter bsc3270.
Prompted Entry: Removing a BSC3270 Terminal from Service
CC0> remove
OBJECTS [...bsc3270...]: bsc3270
COMPONENT [module, port, cu, terminal]: terminal
MODULE ADDRESS: 71
PORT NUMBER [1-8]: 1
CU NUMBER [1-32: +(1-32)]: 1
TERM NUMBER [1-32: +1-32)]: 1
CC0>
Data Networking Products SYNC8 Module Reference, Issue 2
6-35
________________
remove bsc3270
Prompted Entry: Removing a BSC3270 CU from Service
CC0> remove
OBJECTS [...bsc3270...]: bsc3270
COMPONENT [module, port, cu, terminal]: cu
MODULE ADDRESS: 71
PORT NUMBER [1-8]: 1
CU NUMBER [1-32: +(1-32)]: 1
CC0>
Prompted Entry: Removing a SYNC8 Port from Service
CC0> remove
OBJECTS [...bsc3270...]: bsc3270
COMPONENT [module, port, cu, terminal]: port
MODULE ADDRESS: 71
PORT NUMBER [1-8]: 1
CC0>
Prompted Entry: Removing a SYNC8 Module from Service
CC0> remove
OBJECTS [...bsc3270...]: bsc3270
COMPONENT [module, port, cu, terminal]: module
MODULE ADDRESS: 71
CC0>
One-line Entries: Removing BSC3270 components from service.
CC0>
CC0>
CC0>
CC0>
6-36
remove bsc3270 terminal 71 1 1 1
remove bsc3270 cu 71 1 1
remove bsc3270 port 71 1
remove bsc3270 module 71
Data Networking Products SYNC8 Module Reference, Issue 2
________________
restore bsc3270
restore bsc3270
The restore bsc3270 command enables you to put a SYNC8 module and its ready-for-service
components into service for the first time. However, before you can put a BSC3270 component
into service, at least one lower-level component for each component in the hierarchy must be
configured. With restore bsc3270, you can also put an out-of-service BSC3270 component back
into service.
Syntax
You can input restore bsc3270 in prompted or one-line entry. To have module downloading
execute as a background process, press Delete only after the download has started. Pressing
Delete
during the prompting sequence terminates the command.
CC0> restore
OBJECTS [...bsc3270...]: bsc3270
COMPONENT [module, port, cu, terminal]:
For a module, port, cu, or terminal:
MODULE ADDRESS:
For a port, cu, or terminal:
PORT NUMBER [1-8]:
For a cu or terminal:
CU NUMBER [1-32: +(1-32)]:
For a terminal:
TERM NUMBER [1-32: +(1-32)]:
Parameters
CU NUMBER
A number from 1 to 32 specifying a physical control unit for the port.
TERM NUMBER
A number from 1 to 32 specifying an active channel that a physical terminal occupies.
For the remaining parameters, refer to the definitions supplied in enter bsc3270.
Data Networking Products SYNC8 Module Reference, Issue 2
6-37
________________
restore bsc3270
Prompted Entry: Restoring a BSC3270 Terminal to Service
CC0> restore
OBJECTS [...bsc3270...]: bsc3270
COMPONENT [module, port, cu, terminal]: terminal
MODULE ADDRESS: 71
PORT NUMBER [1-8]: 1
CU NUMBER [1-32: +(1-32)]: 1
TERM NUMBER [1-32: +1-32)]: 1
CC0>
Prompted Entry: Restoring a BSC3270 CU to Service
CC0> restore
OBJECTS [...bsc3270...]: bsc3270
COMPONENT [module, port, cu, terminal]: cu
MODULE ADDRESS: 71
PORT NUMBER [1-8]: 1
CU NUMBER [1-32: +(1-32)]: 1
CC0>
Prompted Entry: Restoring a SYNC8 Port to Service
CC0> restore
OBJECTS [...bsc3270...]: bsc3270
COMPONENT [module, port, cu, terminal]: port
MODULE ADDRESS: 71
PORT NUMBER [1-8]: 1
CC0>
6-38
Data Networking Products SYNC8 Module Reference, Issue 2
________________
restore bsc3270
Prompted Entry: Restoring a SYNC8 Module to Service
CC0> restore
OBJECTS [...bsc3270...]: bsc3270
COMPONENT [module, port, cu, terminal]: module
MODULE ADDRESS: 71
Downloading in progress for module 71
All downloads in progress. Hit <DEL> to put process in background.
Download proceeding > > > > > <DEL>
CC0>
One-line Entries: Restoring BSC3270 components to service.
CC0> restore bsc3270 terminal 71 1 1 1
CC0> restore bsc3270 cu 71 1 1
CC0> restore bsc3270 port 71 1
CC0> restore bsc3270 module 71
<system output>
CC0>
Data Networking Products SYNC8 Module Reference, Issue 2
6-39
________________
verify bsc3270
verify bsc3270
The output of the verify bsc3270 command enables you to check the database contents for a
particular SYNC8 module and its components or all SYNC8 modules and their components.
Syntax
You can input verify bsc3270 in prompted or one-line entry. Report output displays information
for the component level specified and each higher level.
CC0> verify
OBJECTS [...bsc3270...]: bsc3270
COMPONENT [module, port, cu, terminal +(module)]:
For a module, port, cu, or terminal:
MODULE ADDRESS [+(all)]:
For a port, cu, or terminal:
PORT NUMBER [1-8: +(all)]:
For a cu or terminal:
If SERVICE TYPE is terminal:
CU NUMBER [1-32: +(all)]:
If SERVICE TYPE is host:
VIRTUAL CU NUMBER [1-32: +(all)]:
For a terminal:
If SERVICE TYPE is terminal:
TERMINAL NUMBER [1-32: +(all)]:
If SERVICE TYPE is host:
VIRTUAL TERMINAL NUMBER [1-32: +(all)]:
Parameters
Except for being able to specify the word all, meaning every SYNC8 module, port, CU, or
terminal, the parameter definitions for MODULE ADDRESS, PORT NUMBER, VIRTUAL/CU
NUMBER, and VIRTUAL/TERMINAL NUMBER are the same as those for enter bsc3270.
Prompted Entry: Verifying Physical and Virtual BSC3270 Terminal Information
CC0> verify
OBJECTS [...bsc3270...]: bsc3270
COMPONENT [module, port, cu, terminal]: terminal
MODULE ADDRESS [+(all)]: +
<report output>
6-40
Data Networking Products SYNC8 Module Reference, Issue 2
________________
verify bsc3270
One-line Entry/Output: Verifying BSC3270 Terminal Information (host service)
CC0> verify bsc3270 terminal +
94-12-31 13:58:08 NODE=Redqueen
M verify bsc3270 terminal all
MODULE ADDRESS: 70
MODULE TYPE: bsc3270
NCHLS: 100
SERVICE STATE: out
DOWNLOAD SERVER: controller
VERSION: standard
94-12-31 13:58:08 NODE=Redqueen
M verify bsc3270 terminal all
HOST
MSG
CODE
PORT
BAUD
PORT CHNLS
TYPE TYPE
CHNG
SET
DUPLEX RATE
SRVC
1
1
host btam
yes
ebcdic
full
9600
out
94-12-31 13:58:08 NODE=Redqueen
M verify bsc3270 terminal all
PORT COMMENT
1
host service
94-12-31 13:58:08 NODE=Redqueen
M verify bsc3270 terminal all
PORT CU
SRVC
1
1
out
94-12-31 13:58:08 NODE=Redqueen
M verify bsc3270 terminal all
TERM
SCRN RECV
LOGOFF LOGOFF FWD
PORT CU TERM TYPE
SIZE GRP
METHOD SEQ ID ACK SRVC
1
1 1
color
3564 bscr
other
BYE
no
out
94-12-31 13:58:08 NODE=Redqueen
M verify bsc3270 terminal all
BKPL
PORT CU TERM CHNL
1
1 1
5
94-12-31 13:58:08 NODE=Redqueen
M verify bsc3270 terminal all
MODULE ADDRESS: 71
MODULE TYPE: bsc3270
NCHLS: 100
SERVICE STATE: out
DOWNLOAD SERVER: controller
VERSION: standard
94-12-31 13:58:08 NODE=Redqueen
M verify bsc3270 terminal all
CODE
PORT
BAUD
PORT CHNLS
TYPE
VDM
SET
DUPLEX RATE
START-UP
SRVC
1
1
term
no
ebcdic
full
9600
standard
out
94-12-31 13:58:08 NODE=Redqueen
M verify bsc3270 terminal all
PORT COMMENT
1
terminal service
94-12-31 13:58:08 NODE=Redqueen
M verify bsc3270 terminal all
PORT CU
SRVC
1
1
out
Data Networking Products SYNC8 Module Reference, Issue 2
6-41
________________
verify bsc3270
One-line Entry/Output (continued)
94-12-31 13:58:08 NODE=Redqueen
verify bsc3270 terminal all
TERM
SCRN ORIG
C-T BDCST CALL ATT
ATT
PORT CU TERM TYPE
SIZE GRP
BILL PERM HOLD STRING ACT
1
1 1
color
1920 bsco
off on
off %ATT
c
94-12-31 13:58:08 NODE=Redqueen
M verify bsc3270 terminal all
BKPL
TEXT
REPORT
PORT CU TERM CHNL
TYPE
SSM
PREDEFINED DESTINATION
1
1 1
5
mixed yes
bschome
CC0>
M
FWD
ACK SRVC
no out
One-line Entry/Output: Verifying BSC3270 Terminal Information (terminal service)
CC0> verify bsc3270 terminal 71 1
94-12-31 15:28:28 NODE=Redqueen
M verify bsc3270 terminal 71 1
MODULE ADDRESS: 71
MODULE TYPE: bsc3270
NCHLS: 100
SERVICE STATE: out
DOWNLOAD SERVER: controller
VERSION: standard
94-12-31 15:28:28 NODE=Redqueen
M verify bsc3270 terminal 71 1
CODE
PORT
BAUD
PORT CHNLS
TYPE
VDM
SET
DUPLEX RATE
START-UP
SRVC
1
1
term
no
ebcdic
full
9600
standard
out
94-12-31 15:28:28 NODE=Redqueen
M verify bsc3270 terminal 71 1
PORT COMMENT
1
terminal service
94-12-31 15:28:28 NODE=Redqueen
M verify bsc3270 terminal 71 1
PORT CU
SRVC
1
1
out
94-12-31 15:28:28 NODE=Redqueen
M verify bsc3270 terminal 71 1
TERM
SCRN ORIG
C-T BDCST CALL ATT
ATT FWD
PORT CU TERM TYPE
SIZE GRP
BILL PERM HOLD STRING ACT ACK SRVC
1
1 1
basic
1920 bsco
off on
off %ATT
c
no out
94-12-31 15:28:28 NODE=Redqueen
M verify bsc3270 terminal 71 1
BKPL TEXT
REPORT TERM
PORT CU TERM CHNL TYPE
SSM
SECR
1
1 1
5
mixed yes
no
PREDEFINED DESTINATION
bschome
CC0>
6-42
Data Networking Products SYNC8 Module Reference, Issue 2
________________
verify bsc3270
Report Fields
The table below correlates each report field heading shown in the output of verify bsc3270 to the
parameter for which you are prompted in enter bsc3270 or change bsc3270. The information
beneath each report field heading reflects the parameter option specified in either command. If an
N/A appears in a report field, it means the parameter is not applicable or not used.
_______________________________________________________________________________



Report Field Name
Corresponding Parameter Name
________________________________________________________________________________


______________________________________________________________________________



 ATT ACT
 ATTENTION ACTION

 ATT STRING
 ATTENTION STRING

 BAUD RATE
 BAUD RATE

 BDCST PERM
 BROADCAST PERMISSION




 BKPL CHNL
 None: backplane channel to which the terminal is mapped 
 CALL HOLD
 CALL HOLD

 CHNLS
 NUMBER OF USER CHANNELS

 CODE SET
 CODE SET




 COMMENT
 COMMENT

 CU
 CU NUMBER/VIRTUAL CU NUMBER

 C-T BILL
 CONNECT-TIME BILLING

 DOWNLOAD SERVER
 DOWNLOAD SERVER

 FWD ACK
 FORWARD DELIVERY ACKNOWLEDGEMENT




HOST
TYPE
HOST
TYPE



 LOGOFF METHOD
 LOGOFF METHOD

 LOGOFF SEQ ID
 LOGOFF SEQUENCE IDENTIFIER

 MODULE ADDRESS
 MODULE ADDRESS




MODULE
TYPE
None:
type
of
hardware
module



 MSG CHNG
 MESSAGE CHAINING

 NCHLS
 None: number of available user channels

 ORIG GRP
 ORIGINATING GROUP

 PORT
 PORT NUMBER




 PORT DUPLEX
 PORT DUPLEX

 PREDEFINED DESTINATION  PREDEFINED DESTINATION

 RECV GRP
 RECEIVING GROUP

 SCRN SIZE
 SCREEN SIZE




SERVICE
STATE
None:
service
state
of
the
SYNC8
module



 SRVC
 None: service state of the component

 START-UP
 START-UP

 TERM
 TERMINAL NUMBER/VIRTUAL TERMINAL NUMBER 
 TERM SECR
 TERMINAL SECURITY




 TERM TYPE
 TERMINAL TYPE

 TEXT TYPE
 TEXT TYPE

 TYPE
 SERVICE TYPE

 VDM
 IS AN AT&T VDM CONNECTED TO THIS LINE




VERSION
_______________________________________________________________________________
 SOFTWARE VERSION

Data Networking Products SYNC8 Module Reference, Issue 2
6-43
________________
BSC3270 - System Responses
System Responses
The following sections contain applicable system responses for the bsc3270 commands. These
sections are organized alphabetically by the key phrases that preface each response. Refer to the
BNS-2000 Node Reference for a detailed explanation of each key phrase.
COMMAND FAILED:
Cannot delete every port of module <addr> while the module is in
service.
The module must be taken out of service with remove before all ports can be deleted.
Change command failed.
The change command could not execute.
Command aborted by user.
The Control Computer terminated command execution because you pressed
console.
DEL
at the
Connected components must be deleted before deleting <component><num>.
The lower component (port, cu, terminal) in the hierarchy must be deleted first.
Could not delete terminal <num>; other terminals will not be processed.
Information regarding the specified terminal cannot be deleted.
Could not update module data for port <num>.
error occurred retrieving database information.
partial changes made. Remove and restore module to synchronize control
computer with module.
system too busy to process command. Try again later.
unknown object.
Remaining entries not done.
The configuration information for the specified port cannot be updated.
Enter command failed.
The enter command could not execute.
Error in configuration data. error code = <hex number>
Contact your support group.
Inconsistent configuration.
The hardware has not been configured consistently.
Module is downloading.
The command failed because the module is currently downloading software.
Too many components.
The number of components has exceeded system limits.
Unable to obtain data.
The system cannot obtain needed data for report output.
6-44
Data Networking Products SYNC8 Module Reference, Issue 2
________________
BSC3270 - System Responses
INPUT ERROR:
A BSC3270 cannot reside in the specified concentrator <addr>.
A BSC3270 can only reside in a BNS-2000 MPC.
All channels are defined for module <addr>.
All channels entered for the specified module were already configured.
All ports have been entered for module <addr>.
All ports for the specified module have already been configured.
All terminals have been entered for CU <num>.
All terminals for the specified control unit have been configured. You cannot enter any
additional terminals.
All <modules/ports/terminals> must have identical
<configurations/options>.
When modifying a range of components, all components must be identically configured.
Concentrator address <addr> is not a remote shelf.
A SYNC8 module can only reside in a BNS-2000 MPC.
Connected components must be deleted before deleting [module <addr>]
[port <num>] [cu <num>].
Use remove to take connected components out of service; then use delete to delete
information regarding each component. Perform the operation in reverse hierarchical
order (the lowest component to the highest).
CU <num> is already entered.
The specified CU is already configured.
CU <num> is not entered.
Information has not been added for the specified control unit.
Group has non-SYNC8 module type; cannot mix module types.
The specified group was previously assigned to a different module type than that
indicated. Different hardware types cannot be mixed within a group.
Group must be <originate/receive>-only.
The selected service type requires an originating or receiving group. Enter the correct
group type and retry the command.
Invalid Number: <num>.
The particular number you specified is not valid.
Logoff sequence identifier <id> does not exist.
Information has not been entered for the specified logoff sequence identifier. Use enter
logoff.
Data Networking Products SYNC8 Module Reference, Issue 2
6-45
________________
BSC3270 - System Responses
INPUT ERROR:
Module address <addr> is empty.
The specified module is not configured.
Module Does Not Exist: <addr>
The module at the specified address does not exist.
Module <addr> already supports <type> service type; service types cannot
be mixed.
The specified module address was previously assigned to a different service type. Each
module can only support one service type.
Module <addr> has wrong hardware type.
The specified module is not a BSC3270 (SYNC8) module.
Module <addr> has wrong hardware type stored in database.
The specified module is not configured as a BSC3270 (SYNC8) module.
Module <addr> is already entered.
The specified module address is already configured.
Module <addr> is downloading.
The module is currently downloading software.
Module <addr> is in service.
Use remove to take the module out of service.
Module <addr> is not a BSC3270 module.
The module number specified is not a BSC3270 (SYNC8) module.
Module <addr> is not entered.
The specified module has not been configured.
Module <addr> is not in service.
The module specified has been removed from service.
Module <addr> is a <type> type module, <etype> expected.
The specified module type is a type other than the type expected.
Module <addr> component(s) <num(s)> is not entered.
The specified module and component (port, cu, terminal) are not configured.
Not an Allowed Value: <input>
The specified string is not an allowed value.
Number Expected: <input>
The specified string is not numeric.
Number of channels for module <addr> cannot be reduced below the highest
channel number in use <num>.
Use the remove and delete commands to remove devices from service and eliminate
unwanted information. If the problem persists, use remove and restore to force the
Control Computer to realign the channel mapping.
6-46
Data Networking Products SYNC8 Module Reference, Issue 2
________________
BSC3270 - System Responses
INPUT ERROR:
Number of channels for module <addr> cannot be reduced until attached
devices are deleted.
Use delete to eliminate information regarding the attached devices. The operation must
be performed in reverse hierarchical order (the lowest to highest).
Parameter out of Range: <input>
The parameter specified is not within the allowed range.
Port <num> is already configured with the maximum number of CUs.
No additional control units can be entered for the specified port.
Port <num> is already entered.
The specified port has already been configured.
Port <num> is in service.
Use remove to take the port out of service.
Port <num> is not entered.
The specified port has not been configured.
Port <num> must be out of service to delete.
The attempted operation cannot be performed while the specified port is in service. Use
remove bsc3270.
Predefined destination <addr> is not a valid service address.
The address entered is not valid. Use enter address to add a valid service address.
Range not Allowed: <input>
The range of numbers specified is not allowed.
Range Specification Error: <input>
The range specified is invalid.
Slot is reserved: <addr>
The particular module address is reserved for another module.
Terminal <num> is already entered.
The specified terminal has already been configured.
Terminal <num> is not entered.
The specified terminal has not been configured.
Terminals cannot be assigned to trunk groups: <num>
Different hardware types cannot be mixed in the same group. Make sure that the specified
group contains all the same type of hardware.
There are <num> channel(s) left on the module; cannot enter <num>
terminal(s).
An insufficient number of module channels exists to accommodate the number of
terminals entered.
Data Networking Products SYNC8 Module Reference, Issue 2
6-47
________________
BSC3270 - System Responses
REMOVE/RESTORE FAILED:
all control units must have at least one terminal configured.
The control units do not have any terminals configured and 1 to 32 have been specified.
cannot assign ports for module <addr>. Reboot and try again.
If the message no more ports appears, the configuration has grown more than 10%
since the last reboot. A single reboot allocates 10% more channels. If the same failure
occurs after a reboot, the configuration is too large.
cannot assign process to port for module <addr>.
The port is assigned. The Control Computer was unable to spawn a process for the port.
cannot get text file for module <addr>.
File or directory not found.
No memory available.
If file or directory not found appears, the file system on the generic disk is
inconsistent. Use fsck to repair the damage or recover using a backup disk. If no
memory available appears, too many different call processors were active. Remove
all of one type (trunks, terminals, sync) before retrying.
could not send message to config.
The command processor could not send a message to the configuration process. Contact
your support group.
could not send message to module <addr>.
The command processor could not send a message to the specified module. Contact your
support group.
download failed for module <addr>.
The software download for the specified module failed. The module is not restored.
inconsistent database entry for module <addr>.
Delete and re-enter.
The information in the database does not agree with the information entered for the
specified module.
incorrect configuration of module <addr>.
The specified module is not configured properly.
module address <addr> contains a <type> module (<type> expected).
The indicated module address contains a different module than that type specified on the
command line.
module address <addr> is beyond the CLOCK.
The module address specified is higher in number than the Clock. Enter the correct
module address (which must be a lower address than that occupied by the Clock) and retry
the command.
6-48
Data Networking Products SYNC8 Module Reference, Issue 2
________________
BSC3270 - System Responses
REMOVE/RESTORE FAILED:
module error none of the control units on port <num> module <addr> have been
restored (error code <code>).
The range 1 to 32 has been specified.
none of the terminals on port <num> module <addr> have been restored
(error code <code>).
The word all, meaning every terminal, has been specified.
unknown <component> <num>
The system does not know that the component (port, cu, terminal) exists.
module <addr> did not respond to command.
The command processor cannot communicate with the specified module.
module <addr> is being downloaded.
The command processor cannot execute the command because the module is downloading
software.
module <addr> is in loop-around mode.
The command processor cannot execute the command because the module is in loopback
mode as a result of diagnostic testing.
module <addr> is in the diagnostic state. Try again later.
The command processor cannot execute the command because the module is being
diagnosed.
module <addr> port <num> control unit <num> must have at least one
terminal configured.
The restore operation failed because one terminal must remain entered in the database per
control unit/port.
module <addr> port <num> must have at least one terminal configured per
control unit.
The restore operation failed because one terminal must remain entered in the database per
control unit.
module <addr> too busy to process <component> <num>.
The module is too busy to process the request for the component (port, cu,
terminal).
no switch memory available.
Module <addr> cannot be restored.
The Control Computer cannot allocate the amount of switch memory the module
requires. This situation occurs if all switch memory was allocated or if it was fragmented
by removing and restoring several modules. Reboot the node so the memory space can
be reallocated in a contiguous block.
Data Networking Products SYNC8 Module Reference, Issue 2
6-49
________________
BSC3270 - System Responses
REMOVE/RESTORE FAILED:
reason for failure unknown <component> <num). Try again later.
The component (port, terminal, cu) failure is not known. The failure reason can only
be determined if the system is in debug mode.
software inconsistency for slot <addr>.
The versions of software on disk are incompatible.
system too busy to process module <addr>.
Try again later.
The system is burdened with processing other tasks. Retry the command later.
the module is sending the logoff sequence to the host for terminal
<num>. Try again later.
The module cannot be removed/restored because it is currently sending the logoff
sequence to the host.
unexpected acknowledgement from module <addr> (<component> <num>).
The acknowledgement from the specified module component (port, cu, terminal) was
not the acknowledgement that was to be expected. Retry the command. If the response
persists, contact your support group.
unexpected acknowledgement from syncmaint.
Try the command again. If the response persists, contact your support group.
unrecognized error code for module <addr>.
Retry the command. If the message recurs, contact your support group.
DIAGNOSTICS:
Boot tests in progress - . . .
Offline diagnostic boot test: <PASS/FAIL>
Extended RAM test in progress - . . .
Offline diagnostic memory test: <PASS/FAIL>
Diagnostic download in progress - . . .
Offline diagnostic downloaded test:
Inst. Set:
<PASS/FAIL>
Timer test: <PASS/FAIL>
Port 1:
<PASS/FAIL>
...
Port 8:
<PASS/FAIL>
The previous responses indicate that the named diagnostic is in progress and whether it
passed or failed.
Diagnose completed test failed; mismatch of transmitted and received data.
test passed.
The previous responses indicate that the diagnostics process completed and the test passed
or failed with the condition noted.
6-50
Data Networking Products SYNC8 Module Reference, Issue 2
________________
BSC3270 - System Responses
DIAGNOSTICS:
Diagnose not completed command cannot be sent to module <addr>.
control computer did not respond. Try again later.
control computer error (error code: <num>).
download failed (error code: <num>).
download file not found.
module task did not respond.
module <addr> did not respond to command. Try again later.
module <addr> did not respond to reinitialization. Try again later.
module <addr> has no resources to process command. Try again later.
module <addr> is being downloaded.
module <addr> is too busy to process command. Try again later.
module <addr> must be in service for on-line diagnose.
module <addr> must be out of service for off-line diagnose.
module <addr> unknown error code: <num>.
module task did not respond.
port <num> must be out of service for loop-around diagnose.
system too busy to process command. Try again later.
The previous responses indicate that the diagnostic process could not complete because
of one of the reasons stated.
WARNING:
Comment entry failed.
Comment File Compaction Failed; Comment File Deleted.
Comment File Deleted
comment file too large.
disk out of space.
not enough memory exists in the system to add the file.
system too busy.
unable to access comment file.
If the comment entry failed because of insufficient memory space, wait until the system is
less busy before reentering a comment.
Download server <addr> is not a valid service address.
The address entered is not valid. Enter the correct service address and retry the
command.
Module data could not be updated for <component> <num>;
error occurred retrieving database information.
Retry the command after waiting a while. If the problem recurs, remove and restore
the module to synchronize it with the Control Computer. If the problem persists,
contact your support group.
Data Networking Products SYNC8 Module Reference, Issue 2
6-51
________________
BSC3270 - System Responses
WARNING:
Module data could not be updated for <component> <num>;
module could not <add/delete>. Remove and restore the module to
synchronize the control computer with the module.
no response from module. Remove and restore the module to synchronize
the control computer with the module.
partial changes made. Remove and restore the module to synchronize
the control computer with the module.
remove and restore the module to synchronize the control computer
with the module.
system too busy to process command. Remove and restore the module
to synchronize the control computer with the module.
The preceding responses indicate that all changes were not downloaded to the module;
thus, the module and Control Computer are not synchronized. Removing and restoring
the module causes data to be redownloaded to the module.
unexpected error code.
unknown object.
For the preceding responses, try removing and restoring the module to synchronize the
module with the Control Computer. If the problem recurs, contact your support
group.
Number of channels may exceed the recommended capacity of the module.
The number of channels entered is greater than the number allowed by the module. Enter
an allowed number of channels and retry the command.
Predefined destination <pdd> is not a valid service address.
The specified PDD has not been entered with enter address.
The ?dwnld group does not exist; run ‘enter/change node’ to create it.
The group being entered must have been previously configured in the database using the
enter or change command.
NO KEY PHRASE:
Cannot abort; <restore/remove> in progress.
The command process cannot be aborted at this point.
Cannot expand mailbox size.
The command processor cannot expand its message queue to receive the request. If the
problem persists, contact your support group.
Control unit <num> on port <num> module <addr> is already in service.
The control unit is in service.
Control unit <num> on port <num> module <addr> is already ready for
service.
The control unit is restored; but the module and/or port is out of service.
6-52
Data Networking Products SYNC8 Module Reference, Issue 2
________________
BSC3270 - System Responses
NO KEY PHRASE:
Data from module <addr> truncated.
The specified module returned error information that exceeds the buffer size allocated. If
the problem persists, contact your support group.
DATABASE BEING MODIFIED - TRY AGAIN LATER
The command process cannot continue because the database is being changed. Wait a
while and retry the command.
Invalid data received for <component> <addr>.
The named component (module, port, terminal) returned invalid, incomplete, or
unexpected data. If the problem persists, contact your support group.
Invalid module type; cannot display port status for module <addr>.
The address specified contains a module other than a BSC3270.
Measurements not available for <component> <addr>.
The named component (module, port, terminal) is not in service.
Measurements not yet available for module <addr>.
Measurements were requested before the first five-minute interval collection completed.
Wait until the module has been in service for at least five minutes before retrying the
command.
Measurement request for <component> <addr> returned error; report will
be incomplete.
The module returned an error code instead of the requested measurements.
Measurements for the named component (module, port, terminal) are missing from
the report. If the problem persists, contact your support group.
Module <addr> is already in service.
The specified module has already been restored to service.
Module <addr> state unknown -- system did not respond.
The remove/restore command might have executed successfully; but the system did not
respond. Use verify bsc3270 or dstat bsc3270 to determine the actual service state of the
module. This response occurs most often during heavy system use.
No measurements available.
A partial report has been generated and all measurements for the specified component are
unavailable. The values in the fields appear as N/A.
No response from module <addr>.
module assumed to be out of service.
The named module does not respond to a measurements request. If the problem persists,
contact your support group.
No terminals configured for Module <addr>, Port <num>, CU <num>
The requested status information for the specified terminals cannot be generated because
none are entered.
Data Networking Products SYNC8 Module Reference, Issue 2
6-53
________________
BSC3270 - System Responses
NO KEY PHRASE:
No <type> modules are entered.
You cannot check the module(s) in the database because none of the specified type are
entered.
Port <num> on module <addr> already in service.
The specified port is currently in service.
Port <num> on module <addr> already ready for service.
The port is in service; the module is out of service.
Process terminated (DEL received); remaining modules will not be
downloaded. All downloads started will proceed in the background.
The
DEL
key was pressed at the console.
Process terminated (DEL received); remaining <component> will not be
restored.
The
DEL
terminal)
key was pressed at the console. The remaining component (port, cu,
will not be restored.
SERIOUS DATABASE TRANSACTION PROBLEM - UPDATE NOT ACCEPTED
The command process cannot continue because of a critical problem in the database.
(Possibly, a file could have been removed from the disk.) Contact your local support
group.
Status request for module <addr> returned error; report will be
incomplete.
The module returned status information containing invalid error codes or garbled data.
The status display shows N/A for the data missing in each field.
Terminal <num> on cu <num> port <num> module <addr> is already in
service.
The specified terminal has already been restored to service.
Terminal <num> on cu <num> port <num> module <addr> is already ready for
service.
The specified terminal has been restored to service; but the CU, port, and/or module is out
of service.
The module <addr> is out of service; report will be incomplete.
ports configured for Module <addr>
No
The ports on the specified module are not entered.
Time command returned error; partial report may follow.
The time interval during which measurements were collected cannot be determined. If
the problem persists, contact your support group.
Time interval shifted; partial report may follow.
Measurements cannot be collected from one time interval. If the problem persists,
contact your support group.
6-54
Data Networking Products SYNC8 Module Reference, Issue 2
________________
BSC3270 - System Responses
NO KEY PHRASE:
Too many <components> specified; report will be incomplete.
Not enough storage space was allocated for the measurements received from the module
for the named component (ports, terminals). Or, duplicate measurements were
requested for one report.
Too many transactions.
Not enough storage space was allocated to request the measurements from the module.
This response should only occur if duplicate measurements were requested in one report.
Unable to communicate with module <addr>.
Unable to obtain data.
The required data cannot be obtained from the hardware.
Unknown transaction error for mod <addr>. (contact support group)
Unable to retrieve data from module <addr>.
module assumed to be out of service.
An error occurred in the interface between the command processor and the maintenance
process. If the problem persists, contact your support group.
Data Networking Products SYNC8 Module Reference, Issue 2
6-55
________________
BSC3270 - System Responses
change logoff
The change logoff command enables you to modify the customized logoff sequences in the
database.
Syntax
You can input change logoff in prompted entry only. The command syntax for enter logoff and
change logoff is similar; however, change logoff prompts you for a NEW LOGOFF SEQUENCE
IDENTIFIER and loops on the CURRENT LOGOFF SEQUENCE IDENTIFIER prompt. The
defaults for change logoff are those values, conditions, or states that currently exist in the
database. They are displayed within parentheses in the parameter prompt.
If you do not want to change all messages in a sequence, your response to the ANOTHER
MESSAGE? prompt should be ++. If you enter no, all subsequent existing messages in the
sequence are deleted.
Parameters
CURRENT LOGOFF SEQUENCE IDENTIFIER
A string of 1 to 6 characters used to identify an existing logoff sequence associated with
BSC3270 host virtual terminals.
NEW LOGOFF SEQUENCE IDENTIFIER
A string of 1 to 6 characters used to change the CURRENT LOGOFF SEQUENCE
IDENTIFIER. Changing this identifier will update the identifier for all terminals associated
with this logoff sequence.
For the remaining parameters, refer to the definitions supplied in enter logoff.
Prompted Entry: Changing Logoff Sequence Information
CC0> change
OBJECTS [ ...logoff...]: logoff
CURRENT LOGOFF SEQUENCE IDENTIFIER [up to 6 chars]: BYE!
NEW LOGOFF SEQUENCE IDENTIFIER [up to 6 chars: +(BYE!)]: BYE
INFO: There are 245 bytes remaining.
AID BYTE [1 char: +(’)]: +
CURSOR ADDRESS [0-3563, "none": +(3560)]: +
DATA ADDRESS [0-3563, "none": +(3560)]: +
DATA FORMAT [char, hex, none: +(char)]: +
ASCII CHAR DATA [up to 25 chars double quoted: +("BYE")]: +
INFO: There are 235 bytes remaining.
ANOTHER MESSAGE? [yes, no: +(no)]: +
CURRENT LOGOFF SEQUENCE IDENTIFIER [up to 6 chars]:
CC0>
6-56
Delete
Data Networking Products SYNC8 Module Reference, Issue 2
________________
delete logoff
delete logoff
The delete logoff command enables you to eliminate a logoff sequence that is associated with a
terminal.
Syntax
You can input delete logoff in prompted or one-line entry.
CC0> delete
OBJECTS [...logoff...]: logoff
LOGOFF SEQUENCE IDENTIFIER [up to 6 chars]:
Parameters
Refer to the parameter definitions supplied in enter logoff.
Prompted Entry: Deleting Logoff Sequence Information
CC0> delete
OBJECTS [...logoff...]: logoff
LOGOFF SEQUENCE IDENTIFIER [up to 6 chars]: BYE
CC0>
One-line Entry: Deleting Logoff Sequence Information
CC0> delete logoff BYE
Data Networking Products SYNC8 Module Reference, Issue 2
6-57
________________
enter logoff
enter logoff
The enter logoff command enables you to add up to 50 logoff sequences (4000 bytes of data) into
the database. When you enter a logoff sequence, the sequence entered is sent to all in-service
BSC3270 host virtual terminals when the call goes down or when a new call comes up. Each
host module receives an identification number for the sequence, the length of the sequence in
bytes, and a variable length string containing the sequence. When a module is restored, its initial
configuration includes all logoff sequences in the database. More than one message can be sent
as part of a logoff sequence.
NOTE:
If you enter all 50 sequences, the amount of text allowed for various other commands is
restricted. In addition, each logoff sequence is limited to 245 bytes. To determine the
total number of bytes in a sequence, count 4 bytes for each message with no data; for
each message with data, count 7 bytes plus the number of characters or hexadecimal
symbols in the data part of the message. There is a maximum of 4,000 bytes for all
logoff sequences.
The logoff sequence is issued in the following Bisync Data Frame format:
STX, SPA, DA, AID, CA1, CA2, SBA, DA1, DA2, logoff sequence, ETX
where CA is cursor address and DA is data address.
Syntax
You can input enter logoff in prompted entry only. The defaults are shown in parentheses.
CC0> enter
OBJECTS [...logoff...]: logoff
LOGOFF SEQUENCE IDENTIFIER [up to 6 chars]:
INFO: There are <num> of bytes remaining.
AID BYTE [1 char: +(’)]:
CURSOR ADDRESS [0-3563, "none": +(none)]:
If CURSOR ADDRESS is not none:
DATA ADDRESS [0-3563, "none": +(none)]:
DATA FORMAT [char, hex, none: +(none)]:
If DATA FORMAT is hex:
ASCII HEX DATA [up to 25 numbers separated by commas, list double quoted]:
If DATA FORMAT is char:
ASCII CHARACTER DATA [up to 25 chars double quoted]:
INFO: There are <num> bytes remaining.
ANOTHER MESSAGE? [yes, no: +(yes)]:
If ANOTHER MESSAGE is yes:
AID BYTE [1 char: +(’)]:
CURSOR ADDRESS [1-3563, "none": +(none)]:
If ANOTHER MESSAGE is no, command loops to LOGOFF SEQUENCE IDENTIFIER prompt.
6-58
Data Networking Products SYNC8 Module Reference, Issue 2
________________
enter logoff
Parameters
A single ASCII character (the attention identification byte) which represents the
transmit key associated with this message.
AID BYTE
ANOTHER MESSAGE?
Specifies if (yes or no) another message is to be entered in the sequence. This prompt does
not appear if another message would cause the 276-byte limit per logoff sequence to be
exceeded.
ASCII CHARACTER DATA
A string of 1 to 25 printable characters surrounded by quotes. If the characters #, @, \ , or +
need to be entered, they must be preceded by a \ .
ASCII HEX DATA
A list of 1 to 25 two-digit hexadecimal symbols from 1 to 7f, interpreted as ASCII character
values, representing one of a sequence of messages to be sent to a host when a virtual
terminal is disconnected. Each symbol entered is separated by commas in a list surrounded
by double quotes.
CURSOR ADDRESS
A number from 0 to 3563 representing the screen position where the cursor is to be located if
this message was entered by a terminal user; or the word none, meaning no cursor address.
The administrator must ensure that the address is within the maximum screen size (3563) of
any virtual terminal that is to use this logoff sequence. (For example, on an 80-characterwide screen, the address for the upper left corner is 0; the address for the fifth character in
the first line is 4; the address for the first character in the second line is 80; the address for
the fifth character in the second line is 84.)
DATA ADDRESS
A number from 0 to 3563 that represents the screen position where the data would be located
if this message was entered by a terminal user; or the word none, meaning no data address.
The administrator must ensure that the address is within the maximum screen size (3563) of
any virtual terminal that is to use this logoff sequence. (The data addresses allowed are
calculated like the cursor address.)
DATA FORMAT
Specifies the format in which data is entered as an ASCII character string (char), a list of
hexadecimal symbols (hex) representing the ASCII values of the characters in the message,
or the word none meaning no data in the message.
LOGOFF SEQUENCE IDENTIFIER
A string of 1 to 6 characters used to identify the logoff sequence associated with BSC3270
host virtual terminals.
Data Networking Products SYNC8 Module Reference, Issue 2
6-59
________________
enter logoff
Prompted Entry: Entering Logoff Sequence Information
CC0> enter
OBJECTS [...logoff...]: logoff
LOGOFF SEQUENCE IDENTIFIER [up to 6 chars]: BYE!
INFO: There are 245 bytes remaining.
AID BYTE [1 char: +(’)]: +
CURSOR ADDRESS [0-3563, "none": +(none)]: 3560
DATA ADDRESS [0-3563, "none": +(none)]: 3560
DATA FORMAT [char, hex, none: +(none)]: char
ASCII CHAR DATA [up to 25 chars double quoted]: "BYE"
INFO: There are 236 bytes remaining.
ANOTHER MESSAGE? [yes, no: +(no)]: no
LOGOFF SEQUENCE IDENTIFIER [up to 6 chars]:
CC0>
6-60
Delete
Data Networking Products SYNC8 Module Reference, Issue 2
________________
verify logoff
verify logoff
The output of the verify logoff command enables you to check the contents of the database for
logoff sequence information. Message data is shown as ASCII characters if the message contains
all printable characters, regardless of whether the message was entered in ASCII characters or in
hexadecimal notation. If the message contains nonprintable characters, the message data is
printed in hexadecimal notation.
Syntax
You can input verify logoff in prompted or one-line entry.
CC0> verify
OBJECTS [...logoff...]: logoff
LOGOFF SEQUENCE IDENTIFIER [up to 6 chars, all: +(all)]:
REPORT TYPE [sequences, terminals, both: +(sequences)]:
Parameters
Except for being able to specify the word all, meaning every logoff sequence identifier, the
LOGOFF SEQUENCE IDENTIFIER parameter definition for verify logoff is the same as that for
enter logoff.
REPORT TYPE
Specifies the type of information to be verified as sequences (logoff sequence information
displayed); terminals (associated BSC3270 host virtual terminal information displayed); or
both (logoff sequences and virtual terminal information displayed).
Prompted Entry: Verifying Logoff Sequence Information
CC0> verify
OBJECTS [...logoff...]: logoff
LOGOFF SEQUENCE IDENTIFIER [up to 6 chars, all: +(all)]: BYE
REPORT TYPE [sequences, terminals, both: +(sequences)]: both
<report output>
Data Networking Products SYNC8 Module Reference, Issue 2
6-61
________________
verify logoff
One-line Entry/Output: Verifying Logoff Sequence Information
CC0> verify logoff BYE both
94-12-31 12:00 NODE=Redqueen
M verify logoff BYE both
THERE ARE 3945 LOGOFF SEQUENCE BYTES REMAINING.
LOGOFF SEQUENCE ID: BYE
MESSAGE 1
AID
BYTE
’
CURSOR
ADDR
3560
DATA
ADDR
3560
MODULE ADDRESS: 70
MODULE TYPE: bsc3270
SERVICE STATE: out
DOWNLOAD SERVER: controller
VERSION: standard
M
M
M
M
DATA
"BYE"
NCHLS: 100
94-12-31 12:00 NODE=Redqueen
verify logoff BYE both
HOST
MSG
PORT CHNLS
TYPE TYPE
CHNG
1
1
host btam
yes
CODE
SET
ebcdic
PORT
DUPLEX
full
BAUD
RATE
9600
SRVC
out
94-12-31 12:00 NODE=Redqueen
verify logoff BYE both
PORT COMMENT
1
host service
94-12-31 12:00 NODE=Redqueen
verify logoff BYE both
PORT CU
SRVC
1
1
out
94-12-31 12:00 NODE=Redqueen
verify logoff BYE both
TERM
SCRN
PORT CU TERM TYPE
SIZE
1
1 1
color
3564
RECV
GRP
bscr
FWD
ACK
no
SRVC
out
94-12-31 12:00 NODE=Redqueen
verify logoff BYE both
BKPL
PORT CU TERM CHNL
1
1 1
5
CC0>
M
6-62
Data Networking Products SYNC8 Module Reference, Issue 2
________________
verify logoff
Report Fields
The table below correlates each report field heading shown in the output of verify logoff to the
parameter for which you are prompted in enter logoff or change logoff. The information
beneath each report field heading reflects the parameter option specified in either command. If an
N/A appears in a report filed, it means that the parameter is not applicable or not used.
____________________________________________________________________________



Report Field Name
_____________________________________________________________________________
 Corresponding Parameter Name or Definition 
___________________________________________________________________________



 AID BYTE

 AID BYTE
 CURSOR ADDRESS

 CURSOR ADDR
 ASCII HEX DATA - or 
 DATA
 ASCII CHARACTER DATA





 DATA ADDRESS

 DATA ADDR
 LOGOFF SEQUENCE IDENTIFIER/

 LOGOFF SEQUENCE ID
 NEW LOGOFF SEQUENCE IDENTIFIER


 None: number of messages entered

 MESSAGE x



 None: baud rate

 *BAUD RATE
 None: backplane channel

 *BKPL CHNL



CHNLS
None:
number
of
channels
for
the
port



 None: code set

 *CODE SET
 None: comment entered

 *COMMENT
 None: CU number

 *CU
 None: download server

 *DOWNLOAD SERVER



 None: forward delivery acknowledgement

 *FWD ACK
 None: module address

 *MODULE ADDRESS
 None: type of the module

 *MODULE TYPE
 None: message chaining

 *MSG CHNG



*NCHLS
None:
number
of
available
user
channels



 None: port number

 *PORT
 None: port duplex

 *PORT DUPLEX
 None: receiving group

 *RECV GRP
 None: screen size

 *SCRN SIZE



 None: service state of the module or component

 *SERVICE STATE
 None: port/cu/terminal service state

 *SRVC
 None: terminal number

 *TERM
 None: terminal type

 *TERM TYPE



 None: host type

 *TYPE
*VERSION
 None: version of software

____________________________________________________________________________
____________________________________________________________________________
* Parameter is not specified with any logoff command; specified via bsc3270 commands. 
Data Networking Products SYNC8 Module Reference, Issue 2
6-63
________________
Logoff - System Responses
System Responses
The following sections contain applicable system responses for the logoff commands. These
sections are organized alphabetically by the key phrases that preface each response. Refer to the
BNS-2000 Node Reference for a detailed explanation of each key phrase.
COMMAND FAILED:
Database Full - Entry Failed: logoff sequence <id/string/table>.
Changes or additions to the logoff sequence identifier, string, or table cannot be made
because the database is full.
Logoff sequence string cannot be retrieved from the database.
The command processor cannot locate the logoff sequence string or identifier in the
database. This message could mean a database inconsistency.
The logoff sequence string database entry not found.
The command processor could not find the database entry for the logoff sequence string.
The logoff sequence would exceed 4000 byte limit.
Too many logoff sequences currently exist in the database.
INFO:
There <is/are> <num> <byte/bytes> remaining.
There is not enough room for a message.
Do a ’change’ or ’delete’ logoff to free up some space.
You are approaching the system limit of 50 logoff sequences (4000 bytes of data).
There <are/is> <num> <byte/bytes> remaining.
This message tells you how many data bytes are left for customized logoff sequence
identifiers.
INPUT ERROR:
Logoff sequence identifier <id> already exists.
The specified logoff sequence identifier has already been added.
Logoff sequence <id> does not exist.
The specified logoff sequence identifier has not been added.
Parameter out of Range: <num-num>
The specified range is not valid.
The logoff sequence cannot be deleted.
with the logoff sequence.
There are terminals configured
A BSC3270 host virtual terminal, which references this logoff sequence, is configured.
6-64
Data Networking Products SYNC8 Module Reference, Issue 2
________________
Logoff - System Responses
INPUT ERROR:
The number of bytes for logoff sequence would be exceeded by <num>.
The previous message was not <entered/changed>.
You have exceeded the bytes allocated for a customized logoff sequence by num bytes.
There are not enough bytes remaining for data.
The data bytes allocated for customized logoff sequences have been depleted.
<hex input> is not a valid format.
The data format specified was character, not hexadecimal.
<hex input> is not a valid hex digit.
The specified input is an invalid form of hexadecimal notation.
WARNING:
Module <addr> could not be updated. Remove and restore module
to synchronize module with control computer.
The command processor could not modify the database entries for the specified module.
Remove and restore the module.
Module <addr> is downloading and cannot be updated. Remove and
restore module to synchronize module with control computer.
The command processor could not modify the database entries for the specified module
because it was currently downloading software.
NO KEY PHRASE:
DATABASE BEING MODIFIED - TRY AGAIN LATER
The command process cannot continue because the database is being changed. Wait a
while and retry the command.
SERIOUS DATABASE TRANSACTION PROBLEM - UPDATE NOT ACCEPTED
The command process cannot continue because of a critical problem in the database.
(Possibly, a file could have been removed from the disk.) Contact your local support
group.
Data Networking Products SYNC8 Module Reference, Issue 2
6-65
________________
Appendix A.
SYNC8 Database Entry Forms
This section contains sample database entry forms. These forms give prompts that appear when
enter commands are used, and the possible values (or range of values) that can be entered in
response to the prompts. Default values are shown in italics.
Form
Title
Page
Form A-1.
Form A-2.
Form A-3.
Form A-4.
Form A-5.
Form A-6.
Form A-7.
Form A-8.
Entering a SYNC8 (BCS3270) Service
Entering a SYNC8 (BSC3270) Module
Entering a SYNC8 (BSC3270) Port for Service Type Host
Entering a SYNC8 (BSC3270) Port for Service Type Terminal
Entering a SYNC8 (BSC3270) Control Unit (CU) for Service Type Terminal
Entering a SYNC8 (BSC3270) Control Unit (CU) for Service Type Host
Entering a SYNC8 (BSC3270) Component Terminal for Service Type Terminal
Entering a SYNC8 (BSC3270) Component Terminal for Service Type Host
Data Networking Products SYNC8 Module Reference, Issue 1
A-2
A-3
A-4
A-5
A-6
A-7
A-8
A-9
A-1
________________
Appendix A. SYNC8 Database Entry Forms
FORM A-1.
Entering a Logoff Sequence for SYNC8 (BSC3270) Service
______________________________________________________________________________________________
 LOGOFF SEQUENCE





 IDENTIFIER











[up to 6 chars]
______________________________________________________________________________________________











 AID BYTE





 [1 char, ’]





______________________________________________________________________________________________






 CURSOR ADDRESS





 [0-3563, none]





______________________________________________________________________________________________





 If a CURSOR ADDRESS is entered:





 DATA ADDRESS





 [0-3563, none]





______________________________________________________________________________________________





 DATA FORMAT
















 [char, hex, none]
______________________________________________________________________________________________






If
DATA
FORMAT
is
hex:











 ASCII HEX DATA
 [double-quoted, comma-separated list





 of up to 25 numbers]





______________________________________________________________________________________________





 If DATA FORMAT is char:





 ASCII CHARACTER DATA











[up to 25 chars double-quoted]
______________________________________________________________________________________________






________________
Values in italics are defaults.
A-2
Data Networking Products SYNC8 Module Reference, Issue 1
________________
Appendix A. SYNC8 Database Entry Forms
FORM A-2.
Entering a SYNC8 (BSC3270) Module
______________________________________________________________________________________________
 COMPONENT





 [module, port, cu, terminal]





module
module
module
module






______________________________________________________________________________________________
 MODULE ADDRESS











______________________________________________________________________________________________
 DOWNLOAD SERVER











[controller]






______________________________________________________________________________________________






 If DOWNLOAD SERVER is controller:





 SOFTWARE VERSION





 [standard]





______________________________________________________________________________________________






 If DOWNLOAD SERVER is not





 controller:





 SOFTWARE VERSION





______________________________________________________________________________________________





 NUMBER OF USER CHANNELS











[1-128,
100]
______________________________________________________________________________________________






________________
Values in italics are defaults.
Data Networking Products SYNC8 Module Reference, Issue 1
A-3
________________
Appendix A. SYNC8 Database Entry Forms
FORM A-3.
Entering a SYNC8 (BSC3270) Port for Service Type Host
______________________________________________________________________________________________
 COMPONENT





 [module, port, cu, terminal]





port
port
port
port
______________________________________________________________________________________________





 MODULE ADDRESS





______________________________________________________________________________________________





 PORT NUMBER











[1-8]
______________________________________________________________________________________________











 COMMENT





 [up to 60 chars double-quoted, none]





______________________________________________________________________________________________






 SERVICE TYPE





host
host
host
host
 [host, terminal]





______________________________________________________________________________________________






 HOST TYPE





 [btam, vtam, other]





______________________________________________________________________________________________





 MESSAGE CHAINING





 [yes, no]





______________________________________________________________________________________________





 CODE SET











[asciicrc,
asciiodd,
ebcdic]
______________________________________________________________________________________________











 PORT DUPLEX





[half,
full]
______________________________________________________________________________________________











 BAUD RATE





 [1200, 2400, 4800, 9600, 19200, 56k]






______________________________________________________________________________________________





________________
Values in italics are defaults.
A-4
Data Networking Products SYNC8 Module Reference, Issue 1
________________
Appendix A. SYNC8 Database Entry Forms
FORM A-4.
Entering a SYNC8 (BSC3270) Port for Service Type Terminal
______________________________________________________________________________________________
 COMPONENT





 [module, port, cu, terminal]





port
port
port
port
______________________________________________________________________________________________





 MODULE ADDRESS





______________________________________________________________________________________________





 PORT NUMBER





 [1-8]





______________________________________________________________________________________________





 COMMENT











[up
to
60
chars
double-quoted,
none]
______________________________________________________________________________________________











 SERVICE TYPE





terminal
terminal
terminal
terminal
 [host, terminal]





______________________________________________________________________________________________






 AT&T VDM ON THIS PORT





 [yes, no]





______________________________________________________________________________________________





 CODE SET





 [asciicrc, asciiodd, ebcdic, crc2, odd2, 




 ebc2]





______________________________________________________________________________________________





 PORT DUPLEX











[half, full]
______________________________________________________________________________________________











BAUD
RATE






[1200, 2400, 4800, 9600, 19200]
______________________________________________________________________________________________











 START UP





 [standard, null_write]






______________________________________________________________________________________________





________________
Values in italics are defaults.
Data Networking Products SYNC8 Module Reference, Issue 1
A-5
________________
Appendix A. SYNC8 Database Entry Forms
Entering a SYNC8 (BSC3270) Control Unit (CU) for Service Type
FORM A-5.
Terminal*
______________________________________________________________________________________________
 COMPONENT





 [module, port, cu, terminal]





cu
cu
cu
cu
______________________________________________________________________________________________





 MODULE ADDRESS





______________________________________________________________________________________________





 PORT NUMBER











[1-8]
______________________________________________________________________________________________











CONTROL
UNIT






 [1-32]





______________________________________________________________________________________________






 INITIAL SERVICE STATE





 [in, out]






______________________________________________________________________________________________





________________
Values in italics are defaults.
* The service type is configured by a previous iteration of the enter bsc3270 command for the component port.
A-6
Data Networking Products SYNC8 Module Reference, Issue 1
________________
Appendix A. SYNC8 Database Entry Forms
FORM A-6.
Entering a SYNC8 (BSC3270) Control Unit (CU) for Service Type Host
______________________________________________________________________________________________
 COMPONENT





 [module, port, cu, terminal]





cu
cu
cu
cu
______________________________________________________________________________________________





 MODULE ADDRESS





______________________________________________________________________________________________





 PORT NUMBER











[1-8]
______________________________________________________________________________________________











 VIRTUAL CONTROL UNIT





 [1-32]





______________________________________________________________________________________________






 INITIAL SERVICE STATE





 [in, out]






______________________________________________________________________________________________





Data Networking Products SYNC8 Module Reference, Issue 1
A-7
________________
Appendix A. SYNC8 Database Entry Forms
FORM A-7.
Entering a SYNC8 (BSC3270) Component Terminal for Service Type
Terminal
______________________________________________________________________________________________





 COMPONENT





 [module, port, cu, terminal]
terminal
terminal
terminal
terminal






______________________________________________________________________________________________





 MODULE ADDRESS






______________________________________________________________________________________________





 PORT NUMBER [1-8]






______________________________________________________________________________________________





 CONTROL UNIT [1-32]






______________________________________________________________________________________________





 TERMINAL NUMBER [1-32]






______________________________________________________________________________________________





 TEXT TYPE [mixed, upper]






______________________________________________________________________________________________





 REPORT STATUS AND SENSE





 [yes, no]






______________________________________________________________________________________________





 TERMINAL TYPE






[basic, color, extended, c/e]





______________________________________________________________________________________________






RECEIVE
ONLY
[yes,
no]






______________________________________________________________________________________________











 ORIGINATING GROUP





 [up to 8 chars]
______________________________________________________________________________________________











 PREDEFINED DESTINATION





 [none]
______________________________________________________________________________________________











 CONNECT-TIME BILLING





 [on, off]
______________________________________________________________________________________________











 BROADCAST PERMISSION





 [on, off]






______________________________________________________________________________________________





 SCREEN SIZE






[1920,
2560,
3440,
3564]






______________________________________________________________________________________________











 TERMINAL SECURITY





 [yes, no]
______________________________________________________________________________________________










 CALL HOLD [on, off]

______________________________________________________________________________________________










 ATTENTION STRING





 [up to 4 chars, none, %ATT]





______________________________________________________________________________________________





 If an attention string is entered:





 ATTENTION ACTION





 [disconnect, command_mode]





______________________________________________________________________________________________





 INITIAL SERVICE STATE







[in,
out]






______________________________________________________________________________________________
A-8
Data Networking Products SYNC8 Module Reference, Issue 1
________________
Appendix A. SYNC8 Database Entry Forms
FORM A-8.
Entering a SYNC8 (BSC3270) Component Terminal for Service Type
Host
______________________________________________________________________________________________
 COMPONENT





 [module, port, cu, terminal]





terminal
terminal
terminal
terminal
______________________________________________________________________________________________





 MODULE ADDRESS





______________________________________________________________________________________________





 PORT NUMBER











 [1-8]





______________________________________________________________________________________________






VIRTUAL
CONTROL
UNIT






 [1-32]





______________________________________________________________________________________________






 VIRTUAL TERMINAL





 NUMBER





 [1-32]





______________________________________________________________________________________________






 TERMINAL TYPE





 [basic, color, extended, c/e]











______________________________________________________________________________________________
 RECEIVE ONLY











[yes,
no]






______________________________________________________________________________________________






 SCREEN SIZE





 [1920, 2560, 3440, 3564]





______________________________________________________________________________________________






 FORWARD DELIVERY





 ACKNOWLEDGEMENT





 [yes, no]





______________________________________________________________________________________________






 RECEIVING GROUP





 [up to 8 chars]











______________________________________________________________________________________________
 LOGOFF METHOD











 [disc, none, sas, test, other]





______________________________________________________________________________________________






If
LOGOFF METHOD is other:






 LOGOFF SEQUENCE





 IDENTIFIER





 [up to 6 chars]





______________________________________________________________________________________________





 INITIAL SERVICE STATE





 [in, out]






______________________________________________________________________________________________





________________
Values in italics are defaults.
Data Networking Products SYNC8 Module Reference, Issue 1
A-9
________________
Appendix B.
Host and Terminal Interfaces
Switched binary synchronous service is provided through SYNC8 modules. SYNC8 modules
interface to 3270-type hosts through RS-232-C or V.35 connections. Refer to the following
tables for the pin/lead assignments.
B-1
B-2
B-3
RS-232 Leads Supported by the SYNC8 Module (DTE)
RS-232 Leads Supported by the SYNC8 Module (DCE)
V.35 Leads Supported by the SYNC8 Module (DTE)

TABLE
B-1. RS-232 Leads Supported by the SYNC8 Module (DTE)
_____________________________________________________________________________

 RS-232 Lead  Pin No. 
Action


_____________________________________________________________________________


 Asserted during link initialization. Remains asserted while link is up.
_____________________________________________________________________________
 20
DTR




DSR
6

 Should be sensed high for link to be up.
_____________________________________________________________________________





DCD
8
Half-duplex: only high while the port is receiving data.

 Full-duplex: always high while the link is in-service.


_____________________________________________________________________________



RTS
4

 Half-duplex: high when the port is sending.



 Full-duplex: always high while the link is in-service.
_____________________________________________________________________________





CTS
5
Half-duplex: must be high for the port to transmit; sensed by the DTE.

 Full-duplex: should always be high while the link is in-service.


_____________________________________________________________________________



TD
2


 Data transmitted from the node to the DSU or modem.
_____________________________________________________________________________




RD
3
Data received by the node from the DSU or modem.
_____________________________________________________________________________



TC
 Clocking received from the DSU or modem.

 15
_____________________________________________________________________________




RC
17
Clocking received from the DSU or modem.
_____________________________________________________________________________





 Ground
_____________________________________________________________________________
FG
1


 Ground

SG
7


_____________________________________________________________________________

Data Networking Products SYNC8 Module Reference, Issue 1
B-1
________________
Appendix B. Host and Terminal Interfaces
TABLE B-2.
RS-232 Leads Supported by the SYNC8 Module (DCE)
_____________________________________________________________________________




RS-232 Lead  Pin No. 
Action
_____________________________________________________________________________





DTR
20
Sensed by the node during link initialization.


 Remains asserted while link is up.

_____________________________________________________________________________



DSR
6


 Asserted during link initialization. Remains high while the link is in
_____________________________________________________________________________

 service.





DCD
8


 Full-duplex: Asserted during link initialization. Remains high while the 


 link is in-service.

_____________________________________________________________________________

 Half-duplex: only high while the port is sending data.





RTS
4


 Half-duplex: low when the port is sending; sensed by the DCE.

_____________________________________________________________________________

 Full-duplex: should always be high while the link is in-service.



 Half-duplex: low when the port desires to transmit.

CTS
5
_____________________________________________________________________________

 Full-duplex: always high while the link is in-service.





TD
2
_____________________________________________________________________________

 Data received by the node from the DSU or modem.





RD
3
Data transmitted to the DSU or modem.
_____________________________________________________________________________



TC
_____________________________________________________________________________
 15
 Clocking provided to the DTE by the DCE.

_____________________________________________________________________________
 17
 Clocking provided to the DTE.

RC




FG
1
_____________________________________________________________________________

 Ground

SG
7
_____________________________________________________________________________

 Ground

B-2
Data Networking Products SYNC8 Module Reference, Issue 1
________________
Appendix B. Host and Terminal Interfaces
TABLE B-3.
V.35 Leads Supported by the SYNC8 Module (DTE)
_____________________________________________________________________________
 V.35 Lead
 Pin No. 

Action
_____________________________________________________________________________



 DTR

 Asserted during link initialization. Remains asserted while link is in
H
_____________________________________________________________________________

 service.





DSR
E
_____________________________________________________________________________

 Must be asserted for link to come up.

 DCD

 Half-duplex: should only be high while the port is receiving data.

F
_____________________________________________________________________________

 Full-duplex: should always be high while the link is in-service.





C
 RTS

 Half-duplex: high when the port is sending.

_____________________________________________________________________________

 Full-duplex: always high while the link is in-service.

 CTS

 Half-duplex: must be high for the port to transmit; sensed by the DTE. 
D
_____________________________________________________________________________

 Full-duplex: should always be high while the link is in-service.





TD+
S
_____________________________________________________________________________

 Data transmitted from the node to the DSU or modem.

 TD
 Data transmitted from the node to the DSU or modem.

P
_____________________________________________________________________________



RD+
T
_____________________________________________________________________________

 Data received by the node from the DSU or modem.

 RD


R
Data received by the node from the DSU or modem.
_____________________________________________________________________________



TC+
AA
_____________________________________________________________________________

 Clocking received from the DSU or modem.

_____________________________________________________________________________

 Clocking received from the DSU or modem.

TCY




RC+
X
_____________________________________________________________________________

 Clocking received from the DSU or modem.

RCV
_____________________________________________________________________________

 Clocking received from the DSU or modem.

_____________________________________________________________________________

 Ground

FG
A




SG
B
_____________________________________________________________________________

 Ground

NOTE:
For the AWJ5 I/O-DB, DSR is not supported on the V.35 connection.
Data Networking Products SYNC8 Module Reference, Issue 1
B-3
________________
Appendix C. Multipoint Control
Unit Configuration Using AT&T
Dataphone II Modems
When configuring AT&T Dataphone II 2048 modems for a multipoint operation using a SYNC8,
use the following configuration illustrated in Figure C-1.
FIGURE C-1.
2048A RS-232-C
Modem
Control
Unit 1
50-pin
2048A RS-232-C
Modem
Control
Unit 2
4-Wire
BTIM
BNS-2000 VCS,
BNS-1000,
BNS-2000
Series M1 Cabinet,
or BNS-2000
MPC Node
50-pin
RS-232-C 2048C 4-Wire Analog
Modem
Bridge
4-Wire
Dataphone II 2048 Modem Configuration
The analog bridge shown in the above configuration uses type A connectorization, which only
allows the main line to be connected to a separate terminal block. If a CSC 8F VF analog bridge
is used, the analog bridge internal switches should be set as follows:
main line terminal impedance set to Norm
drop pad is set for 2048A modems
gating is disabled
main line level is set
anti-streaming timeout duration is disabled
aux mode is disabled
fast level adjustment is disabled
anti-streaming override is disabled
Data Networking Products SYNC8 Module Reference, Issue 1
C-1
________________
Appendix C. Multipoint Control Unit Configuration Using AT&T Dataphone II Modems
Dataphone II 2048C Modem Options
The Dataphone II 2048C modem options should be set as follows:
A3
multipoint control
B1
internal timing
C6
switch carrier, switched RS
D7
channel interface unit not used
E1
quick start-up
E2
one-second holdover out
E3
transmit soft turn off
E4
receive soft turn off
Dataphone II 2048A Modem Options
The Dataphone II 2048A modem options should be set as follows:
A4
multipoint tributary
B2
slaved timing
C6
switched carrier, switched RS
D7
channel interface unit not used
E1
quick start-up
E2
one-second holdover out
E3
transmit soft turn off
E4
receive soft turn off
C-2
Data Networking Products SYNC8 Module Reference, Issue 1
________________
Index
BSC3270. See Binary Synchronous Communication
3270 (BSC3270)
110 patch panel,
cabling, 3-6, 3-7
ordering information, 3-7
C
A
Address,
address as an operations command object, 4-5
module, 4-6
Attention Identification (AID) byte, 4-3
Attention string,
configuration, 4-9
database entry, 4-9
AWJXX board, 2-4, 3-3
cabling, 3-5, 3-6, 3-8
usage for SYNC8, 2-3
V.35 interface, 5-6
B
Backplane,
voltage check, 5-6, 5-7
Billing,
report generation, 4-5, 4-14
Billing on SYNC8 ports, 1-3
Binary Synchronous Communication 3270 (BSC3270),
protocol, 1-3, 3-3, 4-4
SYNC8 module, 4-9
system responses, 6-44, 6-55
terminals, 4-3
Bisynchronous Host Interface Module (BHIM), 1-4
Bisynchronous Terminal Interface Module (BTIM), 1-4
BNS-1000 Modular Cabinet,
shielding requirements, 3-5
BNS-2000 VCS Modular Shelf,
shielding requirements, 3-5
BNS-2000 MPC, 3-5
BNS-2000 Series M1 Shelf,
shielding requirements, 3-5
Cabinet backplane, 2-4
Cabling, 3-3–3-17
to cluster controller, 3-5
to cluster controller via 110 patch panel, 3-6
to cluster controller via DSU, 3-7
to cluster controller via FOM, 3-7
to cluster controller via modem, 3-7
to DTE device via 110 patch panel, 3-6
to host computer, 3-5
to host computer via 110 patch panel, 3-6
to host computer via DSU, 3-7
to host computer via FOM, 3-7
to host computer via modem, 3-7
to Model 045CS VDM, 3-12
to R-VDM, 3-13, 3-15
to R-VDM via D4 Channel Bank and Model 045CS
VDM, 3-16
to R-VDM via D4 Channel Bank and VDM cabinet,
3-13
to R-VDM via D4 Channel Bank and VDM StandAlone Shelf, 3-15
to R-VDM via Model 045CS VDM, 3-12
to R-VDM via VDM cabinet, 3-9
to R-VDM via VDM Stand-Alone Shelf, 3-11
to V.35 DTE device, 3-5
to V.35 DTE via DSU, 3-7
to V.35 DTE via FOM, 3-7
to V.35 DTE via modem, 3-7
to VDM cabinet, 3-9
to VDM Stand-Alone Shelf, 3-11
via 110 patch panel, 3-6
via D4 Channel Bank, 3-13
via D4 Channel Bank and Model 045CS VDM, 3-16
via D4 Channel Bank and VDM Stand-Alone Shelf,
3-15
Data Networking Products SYNC8 Module Reference, Issue 2
I-1
________________
Index
via DSU, 3-7
via FOM, 3-7
via modem, 3-7
via VDM cabinet and D4 Channel Bank, 3-13
Central office (CO), 3-10, 3-11, 3-12, 3-14, 3-15, 3-17
VDM circuit, 3-10, 3-11
change bsc3270 (operations command), 4-4, 4-5, 4-11,
6-3, 6-4
change logoff (operations command), 4-5, 6-3, 6-56
Cluster controller, 6-31
cabling, 3-5, 3-6, 3-7
ordering information, 3-6, 3-7, 3-9
SYNC8 configuration, 4-5
CO. See Central office (CO)
Code set,
database entry, 4-7
Command set, 4-4–4-5, 6-3–6-65
Configurable options, 1-5
Connection range from node to host, 1-3
Control unit (CU), 4-3
configuration, 4-5
entry in database, 4-7
copy module (operations command), 4-13
CU. See Control unit (CU)
D
D4 Channel Bank,
cabling, 3-13, 3-15, 3-16
ordering information, 3-14, 3-16, 3-17
Data communications equipment (DCE),
RS-232-C ports, 3-3
synchronous configuration, 3-3
Data Service Unit (DSU),
cabling, 3-7
ordering information, 3-9
Data terminal equipment (DTE),
cabling, 3-5
ordering information, 3-7
RS-232-C ports, 3-3
synchronous configuration, 3-3
V.35 port, 3-3
Database,
command set overview, 4-4, 4-5
copying information, 4-13
entering information, 4-10
I-2
extensive changes, 4-11
information verification, 4-14
initial administration requirements, 4-3
minor changes, 4-11
module addresses, 4-12, 4-13
moving information, 4-12
parameter considerations, 4-5–4-9
sizing report, 4-14
dbaudit (utility command), 4-14
DCE. See Data communications equipment (DCE)
DCE support, 1-3
delete bsc3270 (operations command), 4-4, 4-5, 4-11,
4-12, 6-6
delete logoff (operations command), 4-5, 6-57
delete (operations command), 6-21
diagnose bsc3270 (operations command), 4-4, 4-5, 5-4,
5-9, 5-10, 5-11, 6-9
Diagnostics,
as a SYNC8 feature, 1-3
commands, 4-4, 4-5, 5-4
SYNC8 module, 5-8
DISABLE position, 2-5
display connections (operations command), 4-14, 5-4,
5-6
display traffic (operations command), 4-14, 5-4
dmeas bsc3270 (operations command), 4-4, 4-14, 5-4,
6-12
Download server,
correcting failure, 5-6
database entry, 4-7
dstat bsc3270 (operations command), 4-4, 4-14, 5-4,
6-16
dstat module (operations command), 5-4
DSU. See Data Service Unit (DSU)
DTE. See Data terminal equipment (DTE)
DTE support, 1-3
E
Electromagnetic interference (EMI), 2-3
Electronics Industry Association (EIA),
control signals, 5-7
Electrostatic discharge (ESD), 2-3
EMI. See Electromagnetic interference (EMI)
Data Networking Products SYNC8 Module Reference, Issue 2
________________
Index
ENABLE position, 2-5
ENABLE position, 6-19
End of Text (ETX), 4-8
enter address (operations command), 4-3
enter bsc3270 (operations command), 4-4, 4-5, 4-6,
4-9, 4-10, 4-11, 4-12, 4-13, 6-3, 6-4, 6-10,
6-12, 6-16, 6-24
enter group (operations command), 4-3
enter logoff (operations command), 4-5, 4-9, 4-11, 6-3,
6-29, 6-58
enter (operations command), 6-21
ESD. See Electrostatic discharge (ESD)
ETX. See End of Text (ETX)
External port diagnostics, 5-9, 6-10
F
Faceplate,
indicators, 1-3, 5-3
Features,
diagnostic capability, 1-3
Fiber Optic Multiplexer (FOM),
cabling, 3-7
ordering information, 3-9
FOM. See Fiber Optic Multiplexer (FOM)
insertion of, 2-3, 2-4
LEDs, 1-3, 2-3, 5-3
physical description, 1-3
removal of, 2-5
SW1 toggle switch, 1-3, 2-3, 5-3
switch settings, 2-3, 2-4
SYNC8 designation, 2-3
verification of, 2-3
Internal port diagnostic, 5-9
Internal port diagnostics, 6-10
L
Latch, 1-3, 2-5
Light emitting diodes (LEDs),
on faceplate, 1-3
LIM. See Link interface module (LIM)
Link interface module (LIM), 4-6
Local modem diagnostics, 5-10, 6-10
Logoff,
commands, 4-3, 4-5
database entry, 4-8
sequence, 4-9, 4-10
system responses, 6-64
Low-speed connections,
cabling for, 3-3
G
Groups,
group as an operations command object, 4-5
H
Hosts,
and connection range to node, 1-3
Host(s),
cabling, 3-5, 3-6, 3-7
documentation needed, 5-3
ordering information, 3-6, 3-7, 3-9
service, 4-3
I
Input/output (I/O) board, 3-3
backplane connector, 2-4
cabling, 2-5
cabling external devices, 2-3
configurations, 3-4
M
Main Distribution Frame (MDF), 3-10, 3-11, 3-12,
3-13, 3-15, 3-17
MDF. See Main Distribution Frame (MDF)
Medium-speed connections,
cabling for, 3-3
Message chaining,
database entry, 4-8
Mode switch, 1-3
DISABLE position, 2-5
ENABLE position, 2-5
Model 045CS VDM. See Voice/Data Multiplexer
(VDM) Model 045CS
Modem,
cabling, 3-7
ordering information, 3-9
Module,
addresses, 4-6
Data Networking Products SYNC8 Module Reference, Issue 2
I-3
________________
Index
administration, 4-9–4-13
diagnostics for, 1-3, 5-3, 5-8–5-12
faceplate, 1-3, 5-3
insertion of, 2-5
LEDs, 1-3
link failure, 5-6
mode switch, 1-3, 2-5
module as an operations command object, 4-5
physical description, 1-3
problems with, 5-4
removal of, 2-5
slot selection, 2-3, 2-4
standard signaling, 3-3
status display, 4-4, 4-14, 5-4
timing problems, 5-8
move module (operations command), 4-12
N
Node,
connection range to host, 1-3
slot constraints, 2-3, 2-4
O
Out-of-service module,
oosmods as an operations command object, 4-5
verification, 4-14
R
Receiving group, 4-3
Remote modem diagnostics, 6-10
Remote-Voice/Data Multiplexer (R-VDM),
cabling, 3-9, 3-10, 3-11, 3-12, 3-13, 3-15, 3-16
ordering information, 3-10, 3-12, 3-13, 3-14, 3-16,
3-17
remove bsc3270 (operations command), 4-4, 4-5, 4-11,
4-12, 4-13, 6-35
remove (operations command), 6-23
Report generation, 4-3
billing schedule verification, 4-5
bsc3270 status, 5-4
connection display, 4-5
database information verification, 4-4, 4-5, 4-11,
4-12, 4-13, 4-14, 5-4
database sizing, 4-14
endpoint number verification, 4-4, 4-5, 4-14
group name verification, 4-10
module status, 4-4, 4-5, 4-14, 5-4
out-of-service module verification, 4-4, 4-5, 4-14
traffic display, 4-5, 5-4
Reset push button, 1-3, 5-3
restore bsc3270 (operations command), 4-4, 4-5, 4-11,
4-12, 4-13, 5-6, 6-37
restore (operations command), 6-23
Round-robin service, 4-3
R-VDM. See Remote-Voice/Data Multiplexer
P
PDD. See Predefined destination (PDD)
Physical characteristics, 3-3
Pins,
bent, 2-4
Port duplex,
database entry, 4-8
Port numbers,
database entry, 4-7
Predefined destination (PDD), 5-6
Problems,
and faceplate indicators, 5-3
common to all modules, 5-3
running host diagnostics, 5-3
steps to resolve, 5-5
with host boards, 5-3
I-4
S
Schedule,
billing report verification, 4-14
schedule as an operations command object, 4-5
Search sequences, 4-3
Series M1 Cabinet, 1-3, 2-4
Service address,
address as an operations command object, 4-5
Service state,
as determined by LEDs, 1-3
commands used to alter, 4-4, 4-5, 4-11, 4-12, 4-13
Shielding requirements,
for BNS-1000 Modular Cabinet, 3-5
for BNS-2000 MPC, 3-5
for BNS-2000 Series M1 Shelf, 3-5
for BNS-2000 VCS Modular Shelf, 3-5
Data Networking Products SYNC8 Module Reference, Issue 2
________________
Index
for synchronous connections, 3-5
Slot selection and constraints, 2-3, 2-4
Stand-Alone Shelf. See Voice/Data Multiplexer
(VDM) Stand-Alone Shelf
StarKeeper II NMS,
administration of SYNC8 via, 4-4
SW1 toggle switch on I/O board, 1-3
Switch,
input/output (I/O) board SW1 toggle, 1-3
I/O board settings, 2-4
mode, 1-3
Synchronous connections,
shielding requirements for, 3-5
Synchronous service,
switched, 1-4
System Responses,
BSC3270, 6-44–6-55
Logoff, 6-64–6-65
verify module (operations command), 4-12, 4-13, 5-4
verify oosmods (operations command), 4-14
Voice/Data Multiplexer (VDM), 6-28
ckloop diagnostics, 6-10
Voice/Data Multiplexer (VDM) cabinet,
cabling, 3-9, 3-10, 3-13
ordering information, 3-10, 3-14
Voice/Data Multiplexer (VDM) Model 045CS,
cabling, 3-12, 3-16
ordering information, 3-13, 3-17
Voice/Data Multiplexer (VDM) Stand-Alone Shelf,
cabling, 3-11, 3-15
ordering information, 3-12, 3-16
T
Terminal(s),
entry in database, 4-7
screen size, 4-9
service, 4-3
type, 4-8
Testing. See Diagnostics
Throughput, 1-5
Timing,
synchronous service problems, 5-8
test, 5-11
Troubleshooting. See Problems
V
V.35 DTE device,
cabling, 3-5, 3-6, 3-7
ordering information, 3-6, 3-9
VDM. See Voice/Data Multiplexer (VDM)
vdm_ckloop diagnostics. See Voice/Data Multiplexer
(VDM)
verify bsc3270 (operations command), 4-4, 4-5, 4-10,
4-11, 4-12, 4-13, 5-4, 5-6, 6-40
verify group (operations command), 4-10, 4-11
verify logoff (operations command), 4-5, 6-61
Data Networking Products SYNC8 Module Reference, Issue 2
I-5
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement