Intermec DCS 300, User Manual

Page: 263 / 452

Running Screen Mapping
10-5
10
About Screen Mapping
Screen mapping lets you map transaction fields from a JANUS device, a Trakker
Antares terminal, or a 6400 to different host screen fields in a host application.
On the DCS 300, you use the Script Builder Tool to create a script file that the
DCS 300 uses to map transaction fields from the devices to host screen fields. You can
also use the Script Builder Tool to create logon and logoff sequences in host screens,
handle regions (such as error messages) on host screens, and send messages back to the
source of the transaction, such as a terminal.
On the DCS 300, you also must create screen mapping sessions that define specific
transactions to be sent to a specific host terminal session using a specific script file.
Screen mapping sessions allow multiple terminal sessions on the DCS 300 to
simultaneously communicate with multiple terminal emulator sessions running on
different hosts.
To create an application that runs on your devices:
•
For Trakker Antares terminals, you can use the C programming language. Intermec
recommends that you use EZBuilder, which is a fast, easy-to-use development tool
that creates applications. You can use it to create menus, screens, data fields, labels,
transactions, and other processing functions. For more information, contact your
local Intermec respresentative.
•
For JANUS devices and WTP devices, you can use C++ or any other standard
programming language.
Note: Transactions sent by Trakker Antares terminals and JANUS devices and running
in the Intermec 2.4 GHz RF network have a maximum length of 1024 characters,
including delimiters. Transactions sent by JANUS devices running in the Intermec 900
MHz RF network have a maximum length of 254 characters, including delimiters.