Runtime Considerations

The detail occurrence for a pageable map cannot occupy more lines than are available in the detail area at runtime.

Size Constraints on Maps

A pageable map can be displayed on screens of varying sizes. The following constraints apply:

A map cannot be displayed on a screen that is narrower than the map.
A pageable map can only be displayed on a screen if the runtime detail area is large enough to hold at least one complete detail occurrence.
The footer (if available) will adjust to the different devices. For example, if the footer starts three lines from the bottom of the screen, the footer will start on:
- Line 22 of a 24X80
- Line 30 of a 32X80
- Line 41 of a 43X80
- Line 25 of a 27X132

Constraints on System-supplied Fields

The following considerations apply to system-supplied fields on a pageable map:

A maximum of one message field can be defined on a map. If defined, the message field for a pageable map should be defined as follows:
- In the header or footer area, if the most important messages for the map are generated by the ADS DISPLAY MESSAGE command.
- In the detail occurrence, if the most important messages for the map are generated by the ADS PUT DETAIL MESSAGE command. At runtime, the single message field defined in the detail occurrence is mapped out once in each occurrence in the detail area.
A page field can be defined in the header or footer area of a pageable map. The page field is associated with the system $PAGE field when the map is defined by using the mapping facility. At runtime, the page field displays the number of the current map page. If the page field is unprotected, the operator can key a page number, first, or last in the field to request display of a page.
A response field can be defined in the header or footer area of a pageable map. A response field is meaningful only when the map is used by a CA ADS dialog.