Floating maps: how BMS places maps using ACCUM

Maps can float - that is, they can be positioned relative to maps already written to the same page and to any edge of the page.

Floating maps save program logic when you need to support multiple screen sizes or build pages piecemeal out of headers, detail lines and trailers, where the number of detail lines depends on the data.

The BMS options that allow you to do this are:
  • JUSTIFY
  • HEADER and TRAILER
  • Relative values (NEXT and SAME) for the LINE and COLUMN options
When you are building a composite screen with the ACCUM option, the position on the screen of any particular map is determined by:
  • The space remaining on the screen at the time it is sent
  • The JUSTIFY, LINE and COLUMN option values in the map definition
The space remaining on the page, in turn, depends on:
  • Maps already placed on the current page.
  • Whether you are participating in “overflow processing”, that is, the processing that occurs at page breaks. If you are, the sizes of the trailer maps in your map sets are also a factor.
The placement rules we are about to list apply even if you do not specify ACCUM, although JUSTIFY values of FIRST and LAST are ignored. However, without ACCUM, each SEND MAP corresponds to a separate page, and thus the space remaining on the page is always the whole page.


dfhp330.html | Timestamp icon Last updated: Monday, 5 June 2017