Using the FLMU Utility

The FLMU Utility for DPS generates the appropriate output file, or files, depending on the command used to initiate the utility.

To generate an ePortal-compatible data definition, use the FLMU utility with the G option, and specify CONNECTOR for the Language parameter, to indicate the working storage to generate. This generates a file with the data description that you can import using ePortal Developer. To ensure that the form number is not included in label names generated by ePortal, specify N for the Prefix parameter.

The following is an example of the working-storage generated for a DPS form:

  01 SCREEN-MAINMENU-100-DATA.
     02 S100-HEADER.
        05 S100-NUMBER         PIC 9(4)   VALUE 100.
        05 S100-NAME           PIC X(8)   VALUE 'MAINMENU'.
        05 S100-SCREENFILE     PIC X(12)  VALUE 'SCREEN$RUN  '.
        05 S100-VERSION        PIC 9(1)   VALUE 3.
        05 S100-CHECK-NUMBER   PIC 9(10)  VALUE 62205.
        05 S100-CONNECTION-ID  PIC X(8)   VALUE 'DPS$CON$'.
        05 S100-SOE-YCO        PIC 9(2).
        05 S100-SOE-XCO        PIC 9(2).
        05 S100-FUNCTIONKEY    PIC 9(5).
        05 S100-OUT-YCO        PIC 9(2).
        05 S100-OUT-XCO        PIC 9(2).
        05 S100-OUT-FID        PIC 9(5).
        05 S100-IN-YCO         PIC 9(2).
        05 S100-IN-XCO         PIC 9(2).
        05 S100-IN-FID         PIC 9(5).
     02 S100-DATA.
  *
        05 SERVICE             PIC 9(1)   VALUE ZERO.
        05 FILLER              PIC X(3).
  *
        05 XMIT                PIC X(1)   VALUE SPACES.
        05 FILLER              PIC X(3).

The HEADER section of the working-storage contains some fields that can be used to simulate special terminal input for the TIP application. For example, if the TIP application contains special processing that occurs when function key input is entered, then you can set the FUNCTIONKEY field to simulate this input. The DATA section of the working-storage contains the field values in a DPS form.

Note: In cases where redefinitions are included in the working-storage for a DPS form, the second definition is selected by default. The second definition always contains the meaningful field names; the first definition only contains FILLER fields used to allocate storage.

You can also capture the formatting of your DPS forms, for example page layout and field attributes. To capture the formatting, you must generate FLDP files.

To capture the ePortal-compatible FLDP files, use the FLMU utility with the F option, which generates a short version of the FLDP files, or the FL options, which generate a long version.

Refer to the Display Processing System (DPS 2200) Form Design Programming Guide for more information.