Intermec DCS 300, Руководство пользователя, Страница: 321 / 452

Running Screen Mapping
10-63
10
c. In the (D)ata or (S)ystem field, enter D.
d. In the Data field, enter the data that the transaction needs to be successful. If
the transaction contains data for multiple host screen fields, separate each field
with a comma and make sure that the field order matches what you have
defined in the script file.
Verify that
•
the transaction data maps correctly to the host screen fields.
•
if you use more than one host screen, when the transaction data is processed, you
return to the main host screen.
•
if you defined a message to send when the transaction is processed, the message
appears in the Receive Transactions dialog box.
•
(VT only) you do not have a timing problem. Send multiple transactions as fast as
you can. If you send transactions faster than the response time of the host, the script
file should wait for the host to be ready to receive data. The script file should
always check to see if the host screen is ready before it maps data to it.
Problem Solution
The script file is
stuck in a host
screen and cannot
finish processing the
transaction data. Make sure that the keystrokes that you captured that move you from
one host screen to the next screen are correct.
Nothing happens on
the host screen Make sure that you entered the correct transaction ID in the Send
Transactions dialog box.
Make sure that the transaction ID you entered is listed in the Selected
list box in the Screen Mapping Session Definition dialog box.
View the Status Monitor window.
(VT only) View the Status Monitor window. If you see the statement, “EMCOMM
ERROR - A bad position was specified - cannot write data,” the script
file does not handle timing properly. The error log also tells you what
field caused the error. The script file should always check to see if the
host screen is ready before mapping data to it.
(Part 3) To verify the logic of a script file
•
Test all failed transactions in the script file, one at a time. You need to make sure
that the script file handles error conditions caused by bad transaction data.
a. For each transaction, note all the regions that you have defined.
b. For each region, use the Send Transaction dialog box to send a transaction that
causes erroneous data to appear.