Indexing Considerations

The index object file contains Index Element (IEL) structured fields t location of the tagged groups in the print file. The tags are containe Tagged Logical Element (TLE) structured fields.

The structured field offset and byte offset values are accurate at creates the output document file. However, if you extract various pa groups for viewing or printing, you will have to dynamically create from a temporary index object file that contains the correct offset infor file. For example, assume the following:

ŸACIF processed all the bank statements for 6 branches, using the ac

number, statement date, and branch number.

ŸThe resultant output files were archived using a system that allowed statements to be retrieved based on any combination of these thre values.

If

you

wanted

to

view all the bank statements

from

branch

1,

your r

would

have

to

extract

all

the

statements from the print file

ACIF

crea

using

the

IELs and

TLEs

in the

index object file) and create another

viewing. This new document would

need its own index object file contain

correct

offset

information.

The

retrieval system

would

have

to

be

able

Under some circumstances, the indexing that ACIF produces may not be expect, for example:

Ÿ If

your

page

definition produces multiple-up output,

and if

the

da

are

using

for your indexing attributes appear on more

than

one

of

multiple-up subpages, ACIF may produce two indexing tags

for

the

same

physical

page

of output. In this situation, only the

 

first

index a

appear as a group name, when you are using the Viewer application Workbench. To avoid this, specify a page definition that formats y without multiple-up when you submit the indexing job to ACIF.

ŸIf your input file contains machine carriage control characters, and

new-page or ASCII carriage control character as a TRIGGER, the ind created will point to the page on which the carriage control chara found, not to the new page or ASCII created by the carriage con

ŸIf your input file contains application-generated separator pages (f

banner pages), and you want to use data values for your indexing a you can write an Input Data exit program to remove the separator Otherwise, the presence of those pages in the file will make the unpredictable for ACIF to reliably locate the data values. As altern writing an exit program, you can also change your application program remove the separator pages from its output, or you can use the

INDEXSTARTBYparameter to instruct ACIF to start indexing on the fi after the header pages.

ŸIf you want to use data values for your indexing attributes, but

values appear

on the first page of each logical

document,

you

can

to place an

indexing tag on the first page by

defining a

FIELD

pa

large enough negative relative record number from the anchor record backward to the first page. Without referencing this FIELD paramete

184 ACIF User’s Guide

Page 204
Image 204
IBM S544-5285-01 manual Indexing Considerations, Acif