Body Records

The BODY layout type is used for the majority of data in the user's input file. That is, any record that is not used for special processing as a page header, page trailer, or group header, contains data to be formatted and placed on the page.

Body records are positioned initially with the LAYOUT command. The default x (horizontal) position for each body record is to be at the same horizontal position as the previous LAYOUT. If this is the first LAYOUT on a logical page, the default horizontal position is 0.

The default y (vertical) position is to place the layout record down one line (as defined in the LINESP subcommand of the last SETUNITS command) from the previous field. If this is the first LAYOUT on a logical page, the default vertical position is one line down from the top margin of the logical page. See PAGEDEF Command for details about margins.

You can specify the rotation of data with the DIRECTION keyword on LAYOUT. All of the fields defined for this record layout uses the same direction unless it is overridden on the FIELD command. On relative LAYOUTs and their fields, the rotation must be ACROSS, so that they have the same net rotation as the page format.

You can also specify fonts and color to be used for the text formatted with this layout record. Double-byte fonts can additionally be requested if you have double byte characters in your data. The color of the text and graphic borders is specified with the COLOR keyword. See DEFINE COLOR Command and FONT Command for details.

Page segments, overlays and objects can be included with keywords on the LAYOUT command. This processing is the same as the traditional PRINTLINE command.

Body records can also be identified as belonging to a group. When the GROUP keyword is used on the body LAYOUT, the group header that is in effect at the time is repeated on subsequent pages as long as the input records use Record ID's that select body LAYOUT and use the GROUP keyword. The group is ended as soon as a Record ID in the input selects a LAYOUT that does not use the GROUP keyword.