User interfaces for the native iSeries are made up of the following components:
Commands—The OS/400 Command Language (CL) provides a user interface that is rigorously consistent, both in appearance and in behavior. It is worth using the CL command definition language wherever possible. When defining commands, you should adhere strictly to the CL conventions. Some of these are discussed in the sections on designing and coding commands, later in this guide. However, commands are not suitable for all occasions; displays are also needed.
Display files—Display files are used to define the panels the user sees. They should be specified as external files using DDS. When defining display files, it is important to use a consistent layout, give standard weightings to the display field attributes, and handle error reporting in a consistent manner. On iSeries, control features of the programs driving the display, such as command key usage, cursor movement, and prompting for confirmation, should also be standardized to follow the SAA CUA guidelines.
Note: For more information, refer to IBM's Defining iSeries (AS/400) Compatible Displays Using DDS Specifications.
Help text—Help text is written using UIM help. Examples of how to do this are given in the IBM publication, The Guide to Programming Application Panel and Help Displays.
Print files—Print files should be specified as external files using DDS. The important considerations are to use a consistent layout and to provide reference information to indicate how, when, and by whom the report was produced.
