Defining Versions of Maps for Different Devices

Batch Compiler Execution and JCL › Special Coding Features of the Batch Compiler › Defining Versions of Maps for Different Devices

Defining Versions of Maps for Different Devices

Supported Screen Sizes

The following terminal screen (that is, device) sizes are supported by the batch compiler:

12X40
12X80
24X80
32X80
43X80
27x132

Defining Device-independent Maps

A map load module that can be used with more than one device type is said to be device-independent. A map developer uses the batch compiler to define a device independent map by specifying different screen layouts for each device on which the map can be displayed. For example, it might be necessary to define shorter literal fields for a 12X40 device than for a 43X80 device.

The DEVICES clause of the MAP AUTOPANEL or PANEL statement is used to specify the list of devices that is valid for the map being defined. The list of devices can be subdivided into device groupings; a different screen layout can be specified for each device grouping.

Defining Device Groupings

Device groupings are established at the field level by using MFLD (for MAP AUTOPANEL) or PFLD statements. Use any of the following techniques to establish device groupings:

Include multiple FOR specifications within one MFLD or PFLD statement, as shown:
```
ADD PANEL JOB-DATA
    DEVICES=(12X40,24X80,32X80).

    ADD PFLD NUM-POSITIONS.
        ATTRIBUTES=(BRIGHT,BLUE)
             FOR (12X40)
                 AT (2,40)
                 VALUE IS '# POSITIONS'
             FOR (24X80)
                 AT (3,80)
                 VALUE IS 'NUMBER OF POSITIONS'
             FOR (32X80)
                 AT (3,80)
                 VALUE IS 'TOTAL NUMBER OF POSITIONS'.
```
The FOR clauses in the previous example establish the following device groupings:
- The first FOR clause establishes a device grouping valid for 12X40 devices. At runtime, the literal field displays as follows:
  - The attribute byte for the field is at coordinate 2,40; the literal begins at the next coordinate (3,1)
  - The literal is # POSITIONS
- The second FOR clause establishes a device grouping valid for 24X80 devices. At runtime, the literal field displays as follows:
  - The attribute byte for the field is at coordinate 3,80; the literal begins at the next coordinate (4,1)
  - The literal is NUMBER OF POSITIONS
- The third FOR clause establishes a device grouping valid for 32X80 devices. At runtime, the literal field displays as follows:
  - The attribute byte for the field is at coordinate 3,80; the literal begins at the next coordinate (4,1)
  - The literal is TOTAL NUMBER OF POSITIONS
Clauses before the first FOR clause in an MFLD or PFLD statement apply to each subsequently established device grouping. In the previous example, the ATTRIBUTES clause displays each literal field established in the PFLD statement in bright blue.
Specify multiple screen sizes in a single FOR clause of an MFLD or PFLD statement, as shown:
```
ADD MAP EMP-INFO
    AUTOPANEL DEVICES=(24X80,32X80,43X80).

    ADD MFLD
            FOR (24X80,32X80)
            AT (14,15)
            VALUE IS 'DEPT NAME'.
```
The FOR clause in the previous sample MFLD statement establishes a device grouping made up of two device types (24X80 and 32X80). A third device grouping (43X80) is implicitly created; however, no value is assigned to the latter device grouping by this MFLD statement.
Specify different screen sizes in individual MFLD or PFLD statements, as shown:
```
ADD MAP CEXME413
    AUTOPANEL DEVICES=(24X80,32X80,43X80)
              USING (EMPOSITION 100).

    ADD MFLD
              FOR (24X80)
              AT (14,15)
              DFLD SALARY-AMOUNT-0420.
    ADD MFLD
              FOR (32X80)
              AT (20,15)
              DFLD SALARY-AMOUNT-0420.
```
Each MFLD (for MAP AUTOPANEL) statement in the previous example associates a screen field with the SALARY-AMOUNT-0420 record element by establishing a device grouping:
- The first MFLD statement establishes a device grouping valid for 24X80 devices. At runtime, the attribute byte for the field is at coordinate 14,15; the value begins at the next coordinate (14,16).
- The second MFLD statement establishes a device grouping valid for 32X80 devices. At runtime, the attribute byte for the field is at coordinate 20,15; the value begins at the next coordinate (20,16).
A third device grouping (43X80) is implicitly created in the previous example; however, values for SALARY-AMOUNT-0420 are not displayed on 43X80 devices.

Specify a combination of the previous options, as shown:

ADD MAP CEXME413 VERSION 2
    AUTOPANEL DEVICES=(24X80,32X80,43X80)
              USING (EMPOSITION 100).

     ADD MFLD
              FOR (24X80,32X80,43X80)
              AT (10,15)
              DFLD SALARY-GRADE-0420.
     ADD MFLD
              FOR (24X80)
              AT (14,15)
              DFLD SALARY-AMOUNT-0420.
     ADD MFLD
              FOR (32X80)
              AT (20,15)
              DFLD SALARY-AMOUNT-0420.

Reconciling Conflicting Specifications

The batch compiler reconciles any conflicting device grouping specifications made by the map developer so that any given screen size belongs to only one device grouping. Since 24X80 and 32X80 are each specified in two different device grouping specifications in the previous sample statements, the batch compiler subdivides the first device grouping and assigns the specifications made for the grouping to each of the three device groupings (24X80, 32X80, and 43X80) established by the second and third MFLD statements.

For example, the following device groupings are established by the previous sample statements:

A device grouping for 24X80 devices displays the following values at runtime:
- SALARY-GRADE-0420 values are displayed at 10,15.
- SALARY-AMOUNT-0420 values are displayed at 14,15.
A device grouping for 32X80 devices displays the following values at runtime:
- SALARY-GRADE-0420 values are displayed at 10,15.
- SALARY-AMOUNT-0420 values are displayed at 20,15.
A device grouping for 43X80 devices displays runtime values for the SALARY-GRADE-0420 element at 10,15.

The batch compiler subdivides conflicting device grouping specifications only as much as necessary to insure that each screen size belongs to a maximum of one device grouping. For example, two device groupings are established when the following sample statements are compiled:

ADD MAP CEXMJKD2
         AUTOPANEL DEVICES = (24X80, 32X80, 43X80)
         USING (INSURANCE-PLAN 100).
     ADD MFLD
             FOR (24X80,32X80)
             AT (14,15)
             DFLD COMPANY-NAME-0435.
     ADD MFLD
             FOR (24X80,32X80,43X80)
             AT (15,15)
             DFLD GROUP-NUMBER-0435.

The three screen sizes specified in the DEVICES clause of the previous MAP AUTOPANEL statement are divided into two device groupings:

The device grouping for 24X80 and 32X80 devices displays values for the COMPANY-NAME-0435 and GROUP-NUMBER-0435 elements.
The device grouping for 43X80 devices displays values only for the GROUP-NUMBER-0435 element.

An AT specification for a device grouping must be valid for the smallest device (screen size) in the device grouping. For example, AT (16,32) cannot be specified for a device grouping that contains the 12X40 device type.

The ORIGIN FOR clause also creates device groupings, as explained in Positioning Maps on Different Devices.

Effects of Device Groupings

The use of device groupings to achieve device independence can affect batch compiler performance, batch utility panel and map reports, and map load module overhead:

The batch compiler validates row and column specifications based on the smallest screen size within each device grouping. A row/column specification of (20,25), for example, would be acceptable for the (24X80,32X80,43X80) device grouping but would not be acceptable for the (12X40,24X80,32X80) device grouping since the specified screen location cannot be accommodated on the 12X40 screen.
The batch utility produces panel and map reports that list as many screen formats as there are device groupings associated with the specified panel/map. Each format illustrates only the smallest screen size within a device grouping. For example, if the device groupings (12X40,43X80), (24X80,32X80), and (12X80) have been defined for panel/map fields associated with the panel, the map utility report displays three screen formats, with screen sizes of 12X40, 24X80, and 12X80.
A map load module contains a separate panel occurrence for each device group, even if there is only one panel field specification that is different.

Maps defined with device groupings cannot be displayed or edited by using the online mapping compiler since that compiler can only display one screen layout for a given map-definition.