DCS 300 User’s Manual
10-70
Script Builder Tool Limitations
Validation can be performed by the data collection device or the host application. The
script cannot perform any validation.
The Script Builder Tool cannot generate these commands:
ACK_MESSAGE
IF_BATCH
SEARCH_SCREEN
AUDIT
IF_SEARCH
USER_INPUT
CAPTURE_POS
LOG_ERROR
WAIT_FOR_POS
FILL_FIELD
PAUSE
WAIT_FOR
IF_
PUT_MAPPED_TRANS
WAIT_FOR_LABEL_POS
If you need to use these commands, you can define a user block to insert these
commands into the script. For help, see “Defining User Blocks” earlier in this chapter.
PUT_TRANS_FIELD
The format of this command that the Script Builder Tool
generates is:
PUT_TRANS_FIELD
transactionfieldnumber
fieldlabel
where:
transaction field number
is the position of the field in the transaction.
field label
is the name of the host screen field you want to
map to the transaction field.
In the
DCS 300 Technical Reference Manual
, there are two optional parameters
following the field label that let you map partial data to a host field. The Script Builder
Tool does not support partial data mapping. These parameters are:
SEND_MESSAGE
There are two types of messages: status and transaction.
For status messages, the format of this command that the Script Builder Tool generates
is:
SEND_MESSAGE "TERM_MESSAGE," +
userdefinedtext
+ [regionlabel |
CUR_POS | CUR_ROW] SRC
Status messages always start with “
TERM_MESSAGE
,” which is automatically
generated. The destination is always fixed to SRC, the source of the transaction, which
is assumed to be an Intermec terminal. The SRC can only receive the message if the
Wait for response check box is checked in the Terminal Screen and Fields dialog box.
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 ...