Subcommands
- DEFAULT Subcommand
-
[DEFAULT | qtagname | QTAG starttag…]
The DEFAULT subcommand specifies a qualified tag that is used to identify the page definition.- DEFAULT
- This keyword is used only when the layout type is either PAGEHEADER or PAGETRAILER, and no name is needed. Only one default PAGEHEADER or PAGETRAILER can be specified in a PAGEFORMAT.
- qtagname
- The qtagname is a defined qualified tag. It is defined by the DEFINEqtagnameQTAG command at the beginning of the page definition.
- QTAGstarttag
- This is an explicit Qualified Tag. It is defined by coding a series of start tags
separated by commas. A start tag is an XML data element name. Put the start tag in
quotes if you want to preserve its case. Otherwise it is folded to upper case.
Example of XML Data and Associated Page Definition with Start Tags
<person> <name> <first>Justin</first> <last>Case</last> </name> </person> PAGEDEF xxx…; DEFINE lname QTAG 'person','name', 'last'; ⋮ Pageformat x … XLAYOUT lname POSITION… ⋮ Pageformat y … XLAYOUT QTAG 'person','name','last' POSITION … ⋮
In Figure Example of XML Data and Associated Page Definition with Start Tags,
person
,name
, andfirst
are start tags. The qualifying tag for the data itemCase
is'person','name','last'
. In the page definition, both XLAYOUT commands address the same XML data item,Case
.
- Layout Type Subcommand
-
[BODY [GROUP | NOGROUP] [XSPACE {0 | n [IN | MM | CM | POINTS | PELS]}] | PAGEHEADER [CONTINUE] | PAGETRAILER [CONTINUE] | GRPHEADER [CONTINUE] [XSPACE {0 | n [IN | MM | CM | POINTS | PELS]}]]
Specifies the layout type.- BODY
- The BODY layout type is used for the majority of data in your database. This is the default.
- GROUP
- The GROUP parameter indicates that the existing group header should be saved and used for subsequent pages.
- NOGROUP
- The NOGROUP parameter indicates that the active group header record should be discarded and not reprinted on subsequent pages. This is the default
- XSPACE
- XSPACE indicates the amount of extra space from the position of the layout to the bottom of the group header area. This allows the user to identify the amount of eXtra space in excess of one text line being used by the header so that the baseline moves down and the following group data is not placed on top of the header area. This space is not calculated by PPFA and must be explicitly defined by the user.
- PAGEHEADER
- This layout type specifies a header that is to be printed on each new page. The baseline
position of this layout is normally in the top margin, but can be anywhere on a logical
page. If RELATIVE is specified, the position is considered to be relative to the page origin. The header
usually contains the customer's name, address, account number, and so forth. Only
one default PAGEHEADER layout can be specified in a PAGEFORMAT and no input record data can be specified in a default layout.
- CONTINUE
- The CONTINUE parameter indicates that this XLAYOUT command is a continuation of the Page Header definition. The formation of the Page Header may require the data from more than one data element. This is done by specifying the CONTINUE parameter.
- PAGETRAILER
- This layout type specifies a trailer that is to be printed on each new page. The baseline
position of this layout is normally in the bottom margin, but can be located anywhere
on a logical page and can be specified as RELATIVE. Only one default PAGETRAILER layout can be specified in a PAGEFORMAT and no input record data is processed with a default layout. It may contain the name
of the form or a footnote.
- CONTINUE
- The CONTINUE parameter indicates that this XLAYOUT command is a continuation of the Page Trailer definition. The formation of the Page Trailer may require the data from more than one data element. This is done by specifying the CONTINUE parameter.
- GRPHEADER
- This layout type specifies a header that is to be printed at the beginning of a group of data. If a logical page eject occurs before the group of data ends, the header