DCS 300 User’s Manual
10-64
Verify that
•
the script file handles the error properly. Usually, the script file clears the error
condition, sends a message to notify the source that the transaction has failed, and
then returns to the main host screen to wait for the next transaction.
Problem
Solution
The script file is
stuck in a host
screen.
View the logic that you defined for the region. If you defined a message
to send when the region appears, check the Receive Transactions dialog
box to see if the message was received. If the message exists, the script
has caught the region. Verify that the keystrokes you captured that
move from one host screen to the next screen are correct.
The message
received is not what
you expect.
If you define a region for a specific error and you also define a region
for general errors and their locations overlap, make sure that the script
checks the specific error before the general error. Define both regions
in the same group and then use the Screen Event Ordering dialog box to
adjust the region order.
(VT only) The script
file does not catch
the region even
though you can see
it on the host screen.
Due to the timing problem that occurs when the script file is executed
faster than the host response time, the script file might check the region
before the host sends the error message to the terminal screen. In the
script file, add a PAUSE statement before the IF_REGION so the script
file will pause for a certain amount of time before it checks the region.
(Part 4) To verify the logic of a script file
•
Debug the script.
a.
Add some
LOG_ERROR
statements to your script file.
b. View the Status Monitor window.
c.
Check the error messages that appear as the script is running.
Conclusion
When you have verified the logic of the script file on the DCS 300, you can try
downloading your application and then running it. Verify the application as much as
possible before you use it with the script file. The most common errors occur when the
application expects to receive a response after it sends a transaction. Make sure that the
script file only sends one message per transaction to the terminal; otherwise, messages
are queued in the Hot Standby file and your application will get out of sync messages.
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 ...