Virtual Key Buttons


Purpose of Virtual Key Buttons

AS/400 programs are dependent on receiving information about which key was pressed by the user to exit a screen. For example, an application may perform a specific operation if the user presses ENTER and a different operation if they press F3. The keys that allow a user to exit an AS/400 screen are known as Attention Identifier (AID) generating keys.

You must have all the Virtual Keyboard Buttons needed by your application defined in a Virtual Keyboard Row. If you do not, the user will not have access to all of your application's functionality.

Webulator/400 allows you to identify groups and positions of all the Virtual Keyboard Buttons needed to properly run your AS/400 applications.

You have control over which buttons the user will see and have access to. For example, if you do not configure the System Request key to be a button, the user will not be given access to that function.

Since Webulator/400 screens are HTML forms being executed by a browser, the user must be given access to the defined Virtual Keys. This access can be given in one of two ways. The most common is through the Webulator/400 Keyboard Plugin. The Keyboard Plugin will take the list of defined Virtual Keys and map them on the user's keyboard whenever the browser is showing a Webulator/400 screen. The other method is to not enable the Keyboard Plugin. In this case, Webulator/400 will simply create browser submit buttons that represent the AS/400 AID keys in order to notify the AS/400 application of the action they wish to take.

List Of Virtual Keyboard Buttons

Webulator/400 allows the following AS/400 keys to be defined as Virtual Keyboard Buttons:

Webulator/400 allows the following actions to be defined as Virtual Keyboard Buttons:

Selecting AS/400 Key and Browser Command Buttons

You select which AS/400 Key and Browser Command Buttons will be available by grouping the desired buttons in a manner of your choosing. You can locate a group of buttons either before or after the 5250 screen data. The ordering of the buttons inside a row is based on the order that they are defined.

Example

Assume that you would like a row of Virtual Keyboard Buttons consisting of the Enter, Reset and Close buttons to appear at the top of the screen. You would define these buttons using the following steps:
  1. Run the Work with Webulator/400 Button Rows (WRKWBLROW) command with the name of your current master configuration file.
  2. Select the desired Webulator/400 directory entry.
  3. Create a new Virtual Keyboard Row by typing the following items on the Work with Webulator/400 Virtual Keyboard Rows screen and pressing ENTER.
  4. Add the Virtual Keyboard Buttons by taking option 5 (Work with virtual keyboard buttons) for the newly created row on the Work with Webulator/400 Virtual Keyboard Rows screen and pressing ENTER.
  5. Type the following on the Work with Webulator/400 Virtual Keyboard Buttons screen to add the Enter Virtual Keyboard Button:
  6. Type the following on the Work with Webulator/400 Virtual Keyboard Buttons screen to add the Reset Virtual Keyboard Button:
  7. Type the following on the Work with Webulator/400 Virtual Keyboard Buttons screen to add the Close Virtual Keyboard Button:

The resulting Virtual Keyboard Row would look like this: