Script capturing is an easy way to generate a script that will automate doing something you can do manually. While script capturing is turned on, it will capture the key presses and mouse/cursor movements so they can be replayed when the script is activated. A script is recorded from the device where the Client is running.
To perform a script capture:
1 Launch the Client and navigate to the emulation screen you want the script to start at.
2 From the Term or Options menu, select Scripting > Start Capture.
Starting Script Capture
3 At the prompt, select Yes to verify the current screen text.
Verifying the Current Screen Text
Selecting Yes makes the captured script start with an If_not command that tells the script to exit if the current screen does not match. Unless you know that your script will only run from the correct screen (for example, a script that is run only when a session first starts, or a script called by another script), you should select Yes. Select No if you do not want to verify the current screen text.
If you select No, click the Verify Screen Contents and Save Cursor Position buttons when you start your script capture. This will cause your script to wait for the Client to finish updating the screen before processing script actions.
4 Perform any actions you want to include in the script. Special action buttons related to recording the script appear on the screen.
Verify Screen Contents and Save Cursor Position Buttons
Verify Screen Contents (or Screen) will cause the generated script to pause and wait for the screen to be updated. The pauses are necessary because the scripts can run much faster than the interaction with the host. Save Cursor Position (or Cursor) will ensure that the cursor is moved to the correct position before the script continues. Field Data ID (or ID) allows you to assign symbologies and/or Data IDs to a field so that scan data with matching criteria is sent to that field. Stop Capture (or Stop) ends the script capture.
The Field Data ID feature, specific to IBM 5250 emulation, allows you to use scripting to configure Field Data Identifiers. Field Data Identifiers assign a unique ID (such as a letter) to each field on the screen. Any time a barcode beginning with that ID is scanned, the barcode information automatically populates the corresponding field. For more information and examples related to the Field Data ID feature, see the Terminal Emulation Scripting Reference Guide.
5 Each time the screen changes, click the Verify Screen Contents button.
6 When you are finished capturing the actions you want in the script, click Stop Capture.
Once you have captured a script, the Script Editor opens. This allows you to name the script and select an activation method. You could also use the Actions tab to add actions for any error condition that the user may encounter.
Was this article useful?
The topic was:
Inaccurate
Incomplete
Not what I expected
Other
