Intermec Antares 2420 - Page 161

Co de 39
Nugget
Operating the Terminal in a Network
4-27
4
To set up the DCS 300
• Configure a peer-to-peer destination name for the host application. Create a
transaction ID, $NGCFGRSP, that will be routed to this destination name. The
DCS 300 uses the transaction ID to route responses from the T2425 back to the host
application. $NGCFGRSP is a special transaction ID that the server uses to forward
configuration response data from a terminal.
All configuration responses will be routed with the $NGCFGRSP transaction ID.
The DCS 300 cannot keep track of multiple applications sending reader or
configuration commands. If you have two host applications sending reader or
configuration commands, they must both be configured to receive the $NGCFGRSP
transactions, and therefore both will receive all responses from all T2425s.
To set up the host computer
• Verify that you can communicate with the DCS 300.
To set up the application
• Prepare and write a host application that can communicate with the DCS 300 and
send transactions to and receive transactions from the T2425 in this format:
transaction header TMF field Configuration command
where:
transaction header
is a 96-byte field containing the message number, date
and time, source application ID, destinations application
ID, transaction ID, and other information. You must set
the system message (SYS$MSG) flag to E in the
transaction header. For help, see the
DCS 300 Technical
Reference Manual
.
TMF field
is a 2-byte field containing one of these values:
CG Configuration Get request sent from the host
application.
Cg Configuration Get response sent from the T2425
to the host.
CS Configuration Set request sent from the host
application.
Cs Configuration Set response sent from the T2425
to the host.