How the DCS 300 Routes Transactions
C-5
C
About Transactions
Communications from an application through the DCS 300 to devices and other
applications involve two types of transactions: data transactions and system
transactions.
Data Transactions
The message handler uses the transaction ID to determine the destinations for a
transaction; it is the primary routing mechanism used by the DCS 300. When a device
transmits a data stream, the data stream contains the transaction ID. The DevComm
locates the end of the transaction ID using the system delimiter. Then, the DevComm
removes the transaction ID from the data stream and places it in the header of the
transaction. If a device cannot place a transaction ID in the data stream, you can
configure one for it.
All transactions are date/time stamped in the transaction header. The DCS 300 also
maintains a unique message number counter for each application. All data transactions
are sequential; therefore, an application can use its counter to check for transaction
continuity.
Each transaction has a well-defined structure consisting of a transaction header and a
data field.
•
The transaction header contains 96 bytes.
•
The transaction data can consist of a maximum of 1024 bytes.
System Transactions
System transactions provide various system control and system operation functions.
They consist of a single mnemonic string, such as Inter. To send a system transaction to
the DCS 300, the application places the system transaction mnemonic into the
destination field, DestApId, of the transaction header and sets the system transaction
flag to S.
Applications must acknowledge all system transactions. For example, all applications
must recognize the system transaction DcmSysHalt, which informs applications that the
DCS 300 has shut down.
For more information on system transactions, see the
DCS 300 Technical Reference
Manual
.
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 ...