DCS 300 User’s Manual
8-16
Your applications will use TCP sockets to communicate with the DCS 300 across a
TCP/IP network. The DCS 300 sets up two channels:
Receive channel
The low priority Receive channel handles unsolicited transactions
from devices and applications, and handles system transactions from applications.
ACK channel
The high priority ACK channel handles acknowledgment (ACK)
transactions from applications and devices.
The DCS 300 creates one auxiliary channel (
AUX_Q
) for each known application.
Transactions that are held in
AUX_Q
have not been saved on disk. If you have a lot of
unprotected power failures, you can reduce the risk of data loss by using the local
interface to set the Transactions held in volatile memory parameter, as follows:
•
If you set the parameter to a small number, only that many transactions can be lost
during a power failure.
•
If you set the parameter to 0, no transactions are held in volatile memory. Instead,
all transactions that would have been written to
AUX_Q
are instead written to a Hot
Standby file.
When you configure the DCS 300, you must pick a realistic value for the Hot Standby
timeout so that the DCS 300 does not hold too many transactions in the auxiliary
channels. Once an application goes into Hot Standby mode, performance and
throughput decrease because the transactions for the application are stored on disk.
It is also important for your application to remain active with respect to the DCS 300.
When an application is inactive, the last transaction sent to the DCS 300 is stored in a
Hot Standby file along with any subsequent transactions. When the application
becomes active, the transactions are delivered, first in first out (FIFO), from the Hot
Standby file.
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 ...