Running Screen Mapping
10-61
10
The top part of the DCS 300 View Results window displays the result of the script
checker. You may see some errors and warnings. Your script file should still run with
warnings, but you must resolve all errors.
Verifying the Script File Logic
To test the logic of the script file, you must set up a test environment and start data
collection on the DCS 300. Then, you must use the Send Transaction feature to send
every transaction to the script file and verify that the script file handles the transaction
correctly.
When you test script files, you should provide many different sets of data and you
should test as many scenarios as possible.
Note:
When testing VT script files, watch for timing problems.
(Part 1) To verify the logic of a script file
1. Set up your test environment.
Note:
If you already have started a host terminal session, make sure that the host
terminal session is at the logon screen.
a.
Add a screen mapping session for the script file. Select all the transactions that
the script expects. Enable the Visible when data collection started? check box.
b. Add a peer-to-peer destination. This destination will be the source of the
transaction when you send transactions to the screen mapping session. It will
also be the destination that receives output transactions from the screen
mapping sessions.
2. From the main screen sidebar buttons, choose Save and Activate.
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 ...