5.8.4 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 LANSA Application Design Guide 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:
SAA/CUA Defaults
|
Recommended Value And Comments
|
Process menu style
|
N - Select by number or cursor
|
Process menu prompt line
|
Enter number of function required or place cursor on same line:
|
Process title in upper case
|
N (upper and lower allowed)
|
Function title in upper case
|
N (upper and lower allowed)
|
Display panel identifiers
|
Y (in CUA 1989 non-action bar systems)
N (in CUA 1989 action bar systems)
|
Message line number
|
22 (above function keys)
|
Function key line number 1/2
|
23/24 (below messages)
|
Show process date and time
|
N (not required)
|
Show function date and time
|
N (not required)
|
Process auto-record advance
|
Y (yes)
|
Function auto-record advance
|
Y (yes)
|
Pull down auto record advance
|
Y (yes)
|
Window border fill characters
|
| - . ' (Sides, Top/Bottom, Top
|
OR
|
: . . : corner and Bottom corner)
|
|
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.
Panel Element Category
|
Color and Additional Color Screen Attributes
|
Additional Mono Screen Attributes
|
ABCH Action bar and pull-down
|
White
|
High Intensity
|
PBPT Panel title
|
Blue
|
|
PBPI Panel identifier
|
Blue
|
|
PBIN Instructions to user
|
Green
|
|
PBFP Field label/description
|
Green
|
|
PBBR Brackets
|
Green
|
|
PBCM Field column headings
|
Blue
|
High Intensity
|
PBGH Group headings
|
Blue
|
High Intensity
|
PBNT Normal text
|
Green
|
|
PBET Emphasized text
|
White
|
High Intensity
|
PBEN Input capable field (normal)
|
Green, Underline
|
Underline
|
PBEE Input capable field (emph)
|
White, Underline
|
Underline, High Intensity
|
PBCH Choices shown on menu
|
Green
|
|
PBSC Choice last selected on menu
|
White
|
High Intensity
|
PBUC Choices not available
|
Blue
|
|
PBCN Protected field (normal)
|
Green
|
|
PBCE Protected field (emphasized)
|
White
|
High Intensity
|
PBSI Scrolling information
|
White
|
High Intensity
|
PBSL Separator line
|
Blue
|
|
PBWB Pop-up window border
|
Blue
|
|
FKCH Function key information
|
Blue
|
|
|
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
|
Function Key Description
|
Short Form Description
|
Function Key No
|
Re
|
Cancel current action
|
Cancel
|
12
|
Re
|
Enter any entry fields
|
Enter
|
RA
|
Re
|
Request help for the current function
|
Help
|
01
|
Op
|
Display choices from a list of entries
|
Prompt
|
04
|
Op *
|
Restore or refresh panel
|
Refresh
|
05
|
***
|
LANSA defined messages key
|
Messages
|
14
|
Op *
|
Scroll panel backward
|
Bkwd
|
07
|
Op *
|
Allow entry of a command
|
Command
|
09
|
Op *
|
Display cycle of function key area forms
|
Keys
|
13
|
Re
|
Exit to the highest level
|
Exit
|
03
|
Re
|
Exit to the next level above
|
Exit
|
03
|
Op *
|
Move cursor to first field on the screen
|
Home
|
HM
|
Op *
|
Scroll panel forward
|
Forward
|
08
|
Op
|
Display table of contents for help
|
Contents
|
23
|
Op
|
Provide information about entire panel
|
Ex Help
|
02
|
Op *
|
Provide index of help information *
|
Index
|
11
|
Op *
|
Provide names and functions of keys *
|
Keys help
|
09
|
Op *
|
Scroll panel left *
|
Left
|
19
|
Op *
|
Re-display last command that was issued *
|
Retrieve
|
09
|
Op *
|
Scroll panel right *
|
Right
|
20
|
Op *
|
Move cursor backward *
|
Switchbkwd
|
18
|
Op *
|
Move cursor forward *
|
Switch fwd
|
06
|
Op
|
Move cursor to action bar
|
Actions
|
10
|
***
|
LANSA defined add key
|
Add/Create
|
06
|
***
|
LANSA defined change key
|
Change
|
21
|
***
|
LANSA defined delete key
|
Delete
|
22
|
|
Notes about this Table
Re
|
indicates an SAA/CUA 'reserved' function key. In such cases the function key cannot be reassigned to other functions.
|
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 a function listed for the function key in the table above.
|
*
|
indicates an SAA/CUA function key assignment that is not allowed for complete SAA/CUA compatibility. 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 function key that is required in this table because it is implemented by LANSA.
|