DCS 300 User’s Manual
C-4
NetComms provide network transparency. For example, the DCS 300 writes a
transaction into an input channel for an application. A local send NetComm reads the
transaction from the input channel and sends it to a remote application. The remote
application processes the transaction and acknowledges the receipt of the transaction
from the local send NetComm. The local send NetComm then writes an ACK
transaction to the ACK channel.
When a remote application sends a transaction to the DCS 300, the transaction is
actually received by the local receive NetComm and then forwarded to the Receive
channel. When the DCS 300 is started, it recognizes each remote application and then it
creates the NetComms.
Emulator communications (EmComms)
EmComms provide an interface between the
DCS 300 and applications running in a VT, ANSI, 5250, or 3270 terminal emulator.
EmComms allow transaction data from a device to be mapped to host applications
running in a terminal emulator.
Note:
Terminal sessions are established and run on the DCS 300, not on the devices.
For example, a transaction is built by a JR2020 and then transmitted through the BRU
to the DCS 300. The DCS 300 DevComm routes the transaction to the Receive channel
where the message handler receives it and passes the transaction along to the screen
mapping application (EmComm) input channel. Then, the data in the transaction is
routed to the screen mapping application that uses a script file to put the data into the
5250 emulator screens on the host. The screen mapping application then sends an ACK
to the ACK channel indicating that it received the transaction data.
Terminal session manager (TSM)
The TSM establishes terminal sessions and routes
messages between a host application and the terminal emulation software running on
the data collection devices. When the device requests a session to start, the TSM
verifies that sessions are available. If a session is available, the device is connected. If
no session is available, the TSM returns an error to the device.
Summary of Contents for DCS 300
Page 1: ...P N 067296 005 User s Manual DCS300 ...
Page 4: ...DCS 300 User s Manual blank ...
Page 16: ...DCS 300 User s Manual ...
Page 22: ...DCS 300 User s Manual ...
Page 23: ...Getting Started 1 ...
Page 24: ...DCS 300 System Manual blank ...
Page 42: ...blank ...
Page 43: ...Learning About the DCS 300 2 ...
Page 44: ...DCS 300 User s Manual blank ...
Page 68: ...blank ...
Page 69: ...Connecting to the Upline Network 3 ...
Page 70: ...DCS 300 System Manual 3 2 blank ...
Page 94: ...blank ...
Page 95: ...Connecting to the Intermec RF Network 4 ...
Page 96: ...DCS 300 System Manual blank ...
Page 134: ...blank ...
Page 135: ...Connecting to the 9180 and the Intermec CrossBar Network 5 ...
Page 136: ...DCS 300 System Manual blank blank ...
Page 158: ...DCS 300 System Manual blank ...
Page 159: ...Running Data Collection Browser 6 ...
Page 160: ...DCS 300 System Manual blank ...
Page 171: ...Running Terminal Emulation 7 ...
Page 172: ...DCS 300 System Manual blank ...
Page 209: ...Running Peer to Peer Applications 8 ...
Page 210: ...DCS 300 System Manual blank ...
Page 232: ...blank ...
Page 233: ...Running Terminal Sessions 9 ...
Page 234: ...DCS 300 System Manual blank ...
Page 258: ...DCS 300 System Manual 9 26 blank ...
Page 259: ...Running Screen Mapping 10 ...
Page 260: ...DCS 300 System Manual 10 2 blank ...
Page 269: ...Running Screen Mapping 10 11 10 Screen 3 Screen 4 Main Host Screen Screen 5 ...
Page 333: ...Troubleshooting 11 ...
Page 334: ...DCS 300 System Manual blank ...
Page 372: ...blank ...
Page 373: ...Specifications and Other Helpful Information A ...
Page 374: ...DCS 300 System Manual B 2 blank ...
Page 391: ...Upgrading the DCS 300 and Devices B ...
Page 392: ...DCS 300 System Manual blank ...
Page 411: ...How the DCS 300 Routes Transactions C ...
Page 412: ...DCS 300 System Manual blank ...
Page 430: ...blank ...
Page 431: ...Index I ...
Page 432: ...DCS 300 System Manual I 2 blank ...