Running Screen Mapping
10-71
10
For transaction messages, the format of this command that is generated by Script
Builder Tool is:
SEND_MESSAGE
userdefinedtext
+ [regionlabel | CUR_POS | CUR_ROW]
SRC
The user-defined text contains data in the format of a transaction and again the
destination is fixed to SRC. This type of message is delivered to the source of the
transaction and the transaction data is mapped to the terminal screen according to the
terminal template definition.
In the
DCS 300 Technical Reference Manual
, the
SEND_MESSAGE
command lets you
specify a destination other than SRC. You can also have as many concatenations as you
want, as long as the string does not exceed the maximum line length. If the Script
Builder Tool generates the
SEND_MESSAGE
command, you are restricted to these
formats.
CURRENT_SCREEN
The Script Builder Tool generates this command and places it as
the first line of every set of events for each transaction. The screen label for this
command is the main screen, since every set of events for each transaction starts from
processing the main screen events. You cannot control where this command appears in
the script.
VT/ANSI Screen Mapping Limitations
VT/ANSI terminals have some limitations that affect how you can use screen mapping.
However, if you are having problems because of a limitation, you can use the
WAIT_FOR scripting command. For help, see the
DCS 300 Technical Reference
Manual
.
•
You cannot automatically position the host cursor to the host screen field in
VT/ANSI screen mapping. However, you can program the script to wait until the
cursor is at the field using the
WAIT_FOR
command. To move the host cursor to the
desired host screen field, you add keystrokes, such as
NEWLN
, to the script. When
you define a host screen field in Script Builder, you can define an exit keystroke
that will be applied after field mapping. If the exit field keystroke will not move the
host cursor to the next host screen field, you can define keystrokes using the user
block feature. Make sure that you add these keystrokes before the
PUT_TRANS_FIELD
command for the next field.
•
When the host VT/ANSI screen is in Scroll mode and the host is using pseudo
field-formatted screens, the DCS 300 does not know where to put the data on the
host screen. You must use the script
WAIT_FOR
commands so the DCS 300 knows
when the host is done sending data.
•
VT terminal sessions and the VT windows that are displayed on the DCS 300
screen cannot show blinking text. If the host application sends blinking text to a VT
terminal session, the DCS 300 shows the text as white text on a dark red
background. If it sends blinking text to a VT window, the DCS 300 shows the text
as green text on a black background.
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 ...