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.
Since Webulator/400 screens are HTML forms being executed by a browser, the
user must be given 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.
You must have all the Virtual Keyboard Buttons needed by your application defined in a Virtual
Keyboard Row or the necessary Screen Keywords defined
so that Webulator/400 will create the needed Virtual Keyboard Buttons. 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.
List Of Virtual Keyboard Buttons
Webulator/400 allows the following AS/400 keys to be defined as Virtual Keyboard Buttons:
- Enter
- Help
- Roll Down
- Roll Up
- System Request
- Attention
- Function Keys F1 through F24
Webulator/400 allows the following actions to be defined as Virtual Keyboard Buttons:
- Reset - Resets form data to original values
- Close - Closes the Webulator/400 session
- Session Configuration - Allows the user to set a limited number of configuration values for their session only
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:
- Run the Work with Webulator/400 Button Rows
(WRKWBLROW)
command with the name of your current Web Server/400 master configuration file.
- Select the desired Webulator/400 directory entry.
- Create a new Virtual Keyboard Row by typing the following items on the
Work with Webulator/400 Virtual Keyboard Rows screen and pressing ENTER.
1 in the Opt field to add a new row.
TOP in the Location field.
1 in the Order field.
- 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.
- Type the following on the Work with Webulator/400 Virtual Keyboard Buttons screen to add the Enter Virtual Keyboard Button:
1 in the Opt field to add a new entry.
Enter in the Key Name field.
10 in the Seq field.
Enter in the Description field.
- Type the following on the Work with Webulator/400 Virtual Keyboard Buttons screen to add the Reset Virtual Keyboard Button:
1 in the Opt field to add a new entry.
Reset in the Key Name field.
20 in the Seq field.
Reset Fields in the Description field.
- Type the following on the Work with Webulator/400 Virtual Keyboard Buttons screen to add the Close Virtual Keyboard Button:
1 in the Opt field to add a new entry.
Close in the Key Name field.
30 in the Seq field.
End Session in the Description field.