The following are examples of button definitions you can add to generated HTML skeletons.
<INPUT TYPE=”SUBMIT” NAME=”_K03” VALUE=”Exit”>
<INPUT TYPE=”SUBMIT” NAME=”_KEN” VALUE=”Enter”>
<INPUT TYPE=”SUBMIT” NAME=”_KHL1202” VALUE=”?”>
<INPUT TYPE=”SUBMIT” NAME=”_K040845” VALUE=”...”>
As in the examples above, you can add command keys to generated skeletons to provide functionality that is not automatically generated (such as field-sensitive help). For instance, the following HTML code displays an input field (which only allows uppercase input), with both a Select button (to mimic existing F4-prompt functionality) and a ? button (to mimic field-sensitive help) alongside it:
[assign the value for TD in your book] <INPUT TYPE=”TEXT” NAME=”_F0452U” VALUE=”” SIZE=”10”> <INPUT TYPE=”SUBMIT” NAME=”_K040452” VALUE=”Sel”> <INPUT TYPE=”SUBMIT” NAME=”_KHL0452” VALUE=”?”>
</TD>
The is an HTML non-breaking space, allowing a small gap between the input field and each button. The previous code would display as:

Before adding additional buttons to HTML skeletons, ensure that the underlying processing exists-in the previous example for instance, ensure that the F4-prompt functionality is active for the field in question.
When a page is submitted to the IBM i, only the command key pressed is sent to the Web Option router, along with all the input fields. Therefore, an HTML page can contain definitions for buttons representing many different command keys, but only one is included in the input field data sent to the IBM i.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |