Page History

...

• Compiled process menu display files are created with RSTDSP(*NO) to stop the IBM i IBM i restore display "flash" from occurring when a process menu is (re)presented after executing a function. Additionally, the compiled process itself uses slightly modified logic to cater for this change.
• Compiled RDML function display files are created with RSTDSP(*NO) to stop the IBM i restore display "flash" from occurring when returning from a call to another RDML function or 3GL program.
• The generated DDS statements make use of the special keywords PUTOVR (put overrides), OVRATR (override attributes), and OVRDTA (override data) to significantly reduce the amount of information (re)sent to the display device on (re)displays of the same screen panel. Generally, only fields and their display attributes are (re)sent on a (re)display of the same screen panel. Textual information such as panel titles, field identification details, etc, are not re-sent.
• The screen panel handling code generated for an RDML function is changed to make use of the PUTOVR, OVRATR, and OVRDTA key- words. This logic involves a special field called OA@LSQ that is used to track the last screen panel that was presented. Whenever a screen panel is to be presented this value is examined. If it matches the sequence number of the current screen panel command, the PUTOVR keywords are used to reduce the amount of information being (re)sent to the device.
• The fact that textual information is not re-sent can have a detrimental effect on screen panels that use the DEF_COND command to alter the fields and identification details that are visible between subsequent (re)displays of the same screen panel. This effect is immediately apparent , and can be easily corrected by altering the value in field OA@LSQ. See the following points for more details.
• The use of this option can also adversely effect the ":" (full colon) or "." (period) that are used on the end of automatically generated field descriptions (identification method *DESC) in some situations where the screen mode is automatically changed. This is a minor cosmetic problem that may occur in some applications, but it will not affect the application in any other way.
• The use of this option can also affect the automatic display of column headings on a browse list. When a display of an empty list is (re)displayed with a list containing data, the column headings may not appear. The reverse of this is also true, when a display of a list containing data is (re)displayed with an empty list the column headings may still be displayed. Again, this minor cosmetic effect can be corrected by making reference to the OA@LSQ field.
• The use of this option with POP_UP commands that then invoke other external routines such as help, messages, prompt key processing or calls to other functions or 3GL programs may be cosmetically effected affected by this option. Although the (re)display of the original POP_UP window is fully completed, the "background" may disappear because the RSTDSP(*YES) option is required to put back any part of the screen panel that was not created by the POP_UP command.
• Field OA@LSQ is accessible at the RDML program level. Simply define field OA@LSQ in your data dictionary as a packed decimal field of length 7, with 0 decimals, and you alter its value at the RDML level.
  The most common change to this field is to set its value to zero to "trigger" a complete resend of an entire screen panel that is being (re)displayed on the display device.

...

• Note that this change affects compiled process menus only. It does not affect the way interpretive mode process menus are (re)presented on a display device.
• This option only aids when the same screen panel is being redisplayed. It cannot aid in any way when the screen panel is not already present on the display device.
• The preceding point indicates that when an application is being designed for frequent and heavy usage on remotely attached display devices, there is no better performance aid than the minimisation minimization of the amount of information shown on, and therefore sent to and/or received from , the remote display device.

...

...

This information only appears on the screen when reviewing a process in a non-SAA/CUA partition, or when specifically reviewing a non-SAA/CUA process. In an SAA/CUA style process, all function key assignments exactly follow those defined for the associated partition.

...