7.104.2 REQUEST Comments / Warnings
The REQUEST command is not a "mode sensitive" command. For details of mode sensitive command processing, refer to Screen Modes and Mode Sensitive Commands. All fields in the FIELDS parameter will be input capable unless they have the specific attributes *NOCHG or *OUTPUT.
The following table indicates all combinations of the DESIGN and IDENTIFY parameters and what values actually result when any of the default values are used:
Specified: DESIGN
|
Specified: IDENTIFY
|
LANSA Uses: DESIGN
|
LANSA Uses: IDENTIFY
|
*IDENTIFY
|
*DESIGN
|
*DOWN
|
*LABEL
|
*IDENTIFY
|
*COLHDG
|
*ACROSS
|
*COLHDG
|
*IDENTIFY
|
*LABEL
|
*DOWN
|
*LABEL
|
*IDENTIFY
|
*DESC
|
*DOWN
|
*DESC
|
*IDENTIFY
|
*NOID
|
*ACROSS
|
*NOID
|
*DOWN
|
*DESIGN
|
*DOWN
|
*LABEL
|
*DOWN
|
*COLHDG
|
*DOWN
|
*COLHDG
|
*DOWN
|
*LABEL
|
*DOWN
|
*LABEL
|
*DOWN
|
*DESC
|
*DOWN
|
*DESC
|
*DOWN
|
*NOID
|
*DOWN
|
*NOID
|
*ACROSS
|
*DESIGN
|
*ACROSS
|
*COLHDG
|
*ACROSS
|
*COLHDG
|
*ACROSS
|
*COLHDG
|
*ACROSS
|
*LABEL
|
*ACROSS
|
*LABEL
|
*ACROSS
|
*DESC
|
*ACROSS
|
*DESC
|
*ACROSS
|
*NOID
|
*ACROSS
|
*NOID
|
|
The following table indicates all combinations of the DESIGN and IDENTIFY parameters and what values result when the *DESIGN default is used in the associated DOWN_SEP or ACROSS_SEP parameters:
Specified: DESIGN
|
Specified: IDENTIFY
|
*DESIGN Specified: DOWN_SEP
|
*DESIGN Specified: ACROSS_SEP
|
*IDENTIFY
|
*DESIGN
|
1
|
1
|
*IDENTIFY
|
*COLHDG
|
5
|
1
|
*IDENTIFY
|
*LABEL
|
1
|
1
|
*IDENTIFY
|
*DESC
|
1
|
1
|
*IDENTIFY
|
*NOID
|
1
|
1
|
*DOWN
|
*DESIGN
|
1
|
1
|
*DOWN
|
*COLHDG
|
5
|
1
|
*DOWN
|
*LABEL
|
1
|
1
|
*DOWN
|
*DESC
|
1
|
1
|
*DOWN
|
*NOID
|
1
|
1
|
*ACROSS
|
*DESIGN
|
5
|
1
|
*ACROSS
|
*COLHDG
|
5
|
1
|
*ACROSS
|
*LABEL
|
1
|
1
|
*ACROSS
|
*DESC
|
1
|
1
|
*ACROSS
|
*NOID
|
1
|
1
|
|
- In some cases all the fields specified in the FIELDS parameter will not fit on one screen. In this case a second, third, fourth, etc screen is automatically designed as required.
- In terms of the RDML program they can be treated like one "long" screen. LANSA will automatically process the screens one after another until they have all been processed. When all screens have been processed the next RDML command is executed. So when you use the REQUEST command you may in fact be requesting that 2 or 3 or more screens be input one after another.
- This facility is a feature of the automatic design procedures. If you are coding the RDML program yourself it may be advisable in some circumstances to "split up" the REQUEST command into multiple REQUEST commands that have only one screen format each.
- If you want the name of the field in which the CURSOR was located when Enter or any other AID was pressed, to be returned to your function, then refer to a field named #CURLOC$FN within your function.
#CURLOC$FN (alpha, 10) will contain the name of the field.