Page History

...

Example 1: Input fields #ORDNUM, #CUSTNUM and #DATEDUE from the workstation:

   REQUEST    FIELDS(#ORDNUM #CUSTNUM #DATEDUE)

or, identically:

   GROUP_BY   NAME(#ORDERHEAD) FIELDS(#ORDNUM #CUSTNUM #DATEDUE)
   REQUEST    FIELDS(#ORDERHEAD)

both use default values for all parameters and field attributes and thus would cause a screen something like this to be designed automatically:

...

Example 2: Modify the previous example to design the screen across ways and use column headings to identify the fields:

   GROUP_BY   NAME(#ORDERHEAD) FIELDS(#ORDNUM #CUSTNUM #DATEDUE)
   REQUEST    FIELDS(#ORDERHEAD) DESIGN(*ACROSS) IDENTIFY(*COLHDG)

which would cause a screen something like this to be designed automatically:

...

When specific positions for a field are nominated the automatic design facility is effectively "disabled".

   GROUP_BY  NAME(#ORDERHEAD) FIELDS((#ORDNUM  *COLHDG *L3 *P3 ) (#CUSTNUM *LABEL  *L3 *P14) (#DATEDUE *NOID   *L7 *P37))
   REQUEST   FIELDS(#ORDERHEAD) TEXT(('--DATE--' 6 37))

which would cause a screen something like this to be designed:

...

Example 4: Use an Expandable Group expression and redesign the layout using the screen design facility:

   GROUP_BY   NAME(#XG_ORDHDG) FIELDS(#ORDNUM #CUSTNUM #DATEDUE)
   REQUEST    FIELDS(#XG_ORDHDG) DESIGN(*ACROSS) IDENTIFY(*COLHDG)

The screen designed automatically would look like:

...

The REQUEST command FIELDS parameter will be expanded as follows:

   REQUEST    FIELDS((#ORDNUM *L2 *P3) (#CUSTNUM *L2 *P13) (#DATEDUE *L5 *P26 *LAB)) DESIGN(*ACROSS)IDENTIFY(*COLHDG)