Form Definition Source File
The form definition source file contains formatting information for an application program form. The form compiler (scrgen) converts the form definition to the specific requirements of your machine. The form compiler writes information from the form definition source file to the TranMap source file in a coded format and to the XML form definition file for the form. The user interface and associated programs use this information to edit, format, and display form data.
It also creates a form definition copybook (DSD) for each application form program. This is a source file of type COPYILE that contains the definitions of the data variables on the form. The application program uses this copybook. The form compiler ensures that this copybook matches the data in the form definition source file.
If the program can be invoked, the form compiler creates a form definition interface copybook (DSDC). This copybook is used by programs that call the invoked program.
The form compiler edits the form definition source file for errors before making changes to the TranMap, the XML form definition file, or the form definition copybook.
The full identification for a form definition source file has the following components:
| Component | Format | Comments |
|---|---|---|
| Product line | LAWAPP9 | The product line name for Lawson applications |
| Location in IFS |
Form definition source files are located in $LAWDIR/productline/rpg/syscoderpg/SYSCODERPGSRC.
|
|
| Source file name |
xxxxD.SCRN
|
The "xxxx" is the program name--for example, GL20). |
Each online program has one form definition source file. An online program can have up to nine forms. Each form in an online program has a separate form definition in the form definition source file. For example, a program with nine forms has one form definition source file that includes nine form definitions.
A form definition has four sections, which must appear in the order listed in the table below. In addition, some of these sections are defined with command pairs (for example, $SCREEN and $END-SCR). Paired commands have intermediate data specifications that are also in a fixed format.
For the formats for these data specifications, see the description of each command pair.
| Section | Req'd? | Command pair? | Definition |
|---|---|---|---|
| Form processing commands | Yes | No | Commands for processing form information based on the action chosen by the user. For more information, see Form Processing Commands. |
| Form Definition | Yes | Yes |
The form definition, or layout, that determines how the data is presented on the form. For more information, see Form Definition. In the form definition section, you can add graphical elements or form tabs to enhance the usability of the form. For more information, see Defining Graphical Elements and Form Tabs. |
| Transaction Data | Yes | Yes | Commands that define attributes for each data field on the form. For more information, see Transaction Data Section. |
| Data edits | No | Yes | A list of default and valid values for input fields on the form, including translation values for fields that have translations. For more information, see Data Edits. |