Use the Macro Editor to modify a recorded macro. Macros consist of text and keyboard function keys. Text is typed into the current session when the macro is played. Keyboard function keys are represented by the function key name enclosed in a less than and greater than sign pair <keyname >. For example, the enter key appears in a macro as follows:
<Enter>
The dialog box contains the following fields:
| Macro definition: | The recorded keystrokes. You may edit the macro definition. Terminal keys are inserted by enclosing the terminal key name in a less than and greater than sign pair (<>), for example, <enter> or <tab>. Plain text is typed into the macro without the less than and greater than sign pair (<>). If it is necessary to enter a less than sign < in plain text then two less than signs must be entered <<, for example, 0 << 1. This is to distinguish a plain text less than sign from the less than sign that introduces a function key. |
| Use terminal emulation keys | When this box is not checked, edit text in the macro definition as you would text in any edit box. You must manually enclose a terminal key name in a less than and greater than sign pair (<>). |
When this box is checked, your keystrokes are recorded in the macro definition as terminal keys at the current cursor location. This option honors the terminal keyboard configuration for the current session.
| Insert Pause | Inserts a 1 second pause "<,>" into the macro. |
| Save As... | Save the current macro with a new name. |
| OK | Click the OK button to save your changes. |
| Cancel | Close the Macro Editor dialog without saving any changes. |
| Help | Display the help for the Macro Editor dialog. |
It is possible to pause macro execution if the macro needs to wait for a host response before continuing. Use the Insert Pause button to pause the macro for one second. The macro recorder does not insert pauses. If pauses are needed, you must enter them manually.
TN3270 Plus is continually being improved. To learn more about the latest enhancements, please review our Version History web page.