Identifying Screen Keywords


Webulator/400 can parse output fields in the 5250 data stream for configurable keywords or phrases and convert them into Virtual Keyboard Buttons. Pressing these buttons are the equivalent to the user pressing Enter or the corresponding function key in a 5250 emulation program. This feature allows for an easier and quicker way for the user to navigate through your applications.

Defining Keywords To Parse

You define the list of case sensitive keywords to parse by associating a text phase with an AS/400 AID Code. You can have multiple entries for any AS/400 AID Code. For example, you may want to search for all occurrences of the word Enter and ENTER and convert them to a browser button. See the configuration topic on Parsed Buttons for more information on how to configure keywords.

You can choose to have the button display the keyword entry or the text description associated with the keyword. The default behavior is to use the text description for the button text. If you specify to use the text description, Webulator/400 will use all characters after the keyword until one of the following conditions is found:

Example

Assume that the last line of your AS/400 screen had the following output fields:
   F3=Exit       F4=Prompt       F12=Cancel

You can have Webulator/400 convert these function key definitions into buttons by performing the following steps:

  1. Run the Work with Webulator/400 Parsing Strings (WRKWBLPRS) command with the name of your current Web Server/400 master configuration file.
  2. Select the desired Webulator/400 directory entry.
  3. Type the following on the Work with Webulator/400 Parsed Buttons screen to parse for the F3 keyword:
  4. Type the following on the Work with Webulator/400 Parsed Buttons screen to parse for the F4 keyword:
  5. Type the following on the Work with Webulator/400 Parsed Buttons screen to parse for the F12 keyword:

The first configuration entry is interpreted as search for all occurrences of the string "F3=" in the 5250 data stream and replace the output field with a Virtual Keyboard button that sends the F3 key code to the AS/400.

The resulting section of the screen would look like this: