Logical Page Eject Processing

A logical page eject can be caused by the following:

• Any Record ID that references a layout format with a specification of New Page.
• A relative baseline overflow (a Body or Group Header layout format that when processed against the current input record causes an overflow of the current print position into the bottom margin). If processing of the input record would cause a relative baseline overflow, the page eject is processed before any part of the input record is printed.
• A Data Map change or Medium Map change, or, in Mixed Mode, a Begin Document or Begin Page structured field.

Page Header, Page Trailer, and Group Header Data Records used with page ejects are activated in the following manner:

• If a Data Record specifies the Record ID of a PAGEDEF Page Header layout format, that Data Record is not printed on receipt but is saved as the active page header record (for that PAGEFORMAT). It is saved for the duration of the job or until a subsequent Data Record specifies a Page Header (for that PAGEFORMAT).
• If a Data Record specifies the Record ID of aPAGEDEF Page Trailer layout format, that Data Record is not printed on receipt but is saved as the active page trailer record (for that PAGEFORMAT). It is saved for the duration of the job or until a subsequent Data Record specifies a Page Trailer (for that PAGEFORMAT).
• If a Data Record specifies the Record ID of a PAGEDEF Group Header layout format, that Data Record is not printed on receipt but is saved as the active group header record. The PAGEDEF Group Header is printed when the next Data Record specifies a Body layout with a GROUP specification and on subsequent page ejects. The Group Header and its associated Data Record is kep