1.2.19 Prompting
Specify the RDML process and function that should be invoked to handle a "prompt request" made against the field being defined or changed. A "prompt request" is made against a field when the user positions the screen cursor into a field, on its label, or on one of its column headings, and then uses the PROMPT function key or equivalent request. Normally the prompt function key is F4, but it may be assigned differently on your system.
Process
Specify the name of the process that has the RDML function to be invoked to handle a "prompt request" made against the field being defined or changed.
Function
Specify the RDML function that should be invoked to handle a "prompt request" made against the field being defined or changed.
Warnings
- LANSA does not check that the Process or Function exists.
Tips & Techniques
- When specifying the name associated with a prompting process and function, it is recommended that the process name be nominated as *DIRECT. This indicates to the prompt control procedures that the nominated function can be called in "direct" mode, without having to go through the associated process "controller".
- Using *DIRECT has positive performance benefits, but when a prompting function is to be invoked this way it must use the FUNCTION OPTIONS(*DIRECT) command. Refer to CALL Comments / Warnings and FUNCTION Examples for more details of direct mode invocation of functions.
- When a reference field has been specified, initially the prompt process/function is inherited from the referenced field, but you can change it if required. Refer to 1.2.7 Reference Field.
- If the reference field's prompt process/function is changed, any of the fields referring to it which have the same prompt process/function (before the referenced field is changed) also have their prompt process/function updated.
- For more technical details, refer to Prompt_Key Processing. For examples of prompting processes and functions, please refer to What Happens When the PROMPT Key is Used in the .
Also See