5.8.5 If you Comply with SAA/CUA Standards and Guidelines
The following section only applies if you are modifying an existing partition or creating a new partition to comply with SAA/CUA standards and guidelines.
Before attempting to create or use an SAA/CUA compliant partition read the chapter in the that describes in full the IBM i SAA/CUA Implementation used by LANSA.
When you are changing an existing partition to implement SAA/CUA standards or creating a new partition that will use SAA/CUA standards a series of additional screen formats will be presented which will request details of your SAA/CUA implementation.
The following information tables describe the recommended answers to all questions asked on these additional screen formats:
|
Note 1: If you plan to use reverse video borders, the use of the blank (i.e. X'40') character for all four of these window fill characters is strongly recommended.
Note 2: Compiled pop-up window applications are locked into these fill characters at compile time, so a change to any value may mean that applications need to be recompiled before the change will be completely visible to end users.
SAA/CUA Color/Attributes Defaults
The following color and attribute table describes the default colors and attributes adopted by LANSA itself, and for applications created within SAA/CUA partitions.
You are not forced to follow these default values.
|
|
Color codes you should use are |
White- WHT Green- GRN Blue- BLU |
|
Attribute codes you should use are |
High Intensity - HI Underline- UL |
For other color and attribute codes that are available, refer to the field definition section of this guide.
SAA/CUA Function Key Defaults
The table below indicates the standard function key assignments used by the LANSA implementation under SAA/CUA, the suggested short form descriptions and the suggested function key that should be assigned.
You are not forced to follow the recommended values and can change them to your site standards if desired.
|
Notes about this Table
|
Re |
indicates an SAA/CUA 'reserved' function key. In such cases the function key cannot be reassigned to other functions, even if the specified functions don't apply to a particular panel. |
|
Op |
indicates a 'non-reserved' SAA/CUA function key. In such cases the function key may be reassigned to other functions, but only if the application does not support the functions proscribed for the function key by this table. |
|
* |
indicates an SAA/CUA function key assignment that is proscribed for complete SAA/CUA compatibility, but is not currently implemented directly within LANSA. The use of such keys is controlled by the USER_KEYS parameter of DISPLAY and REQUEST commands. It is the responsibility of the user to implement such key assignments in RDML programs as per the SAA/CUA guidelines described by the table above. |
|
*** |
indicates a non-SAA/CUA proscribed function key that is required in this table because it is implemented by LANSA. |