Chapter 7. Indexing and loading 181
The output of the OS/400 indexer consists of an output file that contains the text of the 
spooled file and an index file that contains the index values that are extracted from the 
spooled file. Also, for AFP , the output of the OS/400 indexer contains a resource file that 
contains the AFP resources that are used by the spooled file (except for fonts, which are not 
stored but are mapped by Content Manager OnDemand Client during display). To create a 
resource file, the OS/400 indexer must have access to the resources that are required by the 
input data stream. Content Manager OnDemand stores the resources and then later retrieves 
the resources that are associated with a specific document when a user selects the document 
for viewing. 
The OS/400 indexer indexes input data based on the organization of the data: 
/SM590000Document organization. For reports that are made up of logical items, such as statements, 
policies, and invoices, the OS/400 indexer can generate index data for each logical item in 
the report. 
/SM590000Report organization. For reports that contain lines of detail with sorted values on each 
page, such as a transaction log or general ledger, the OS/400 indexer can divide the 
report into sets of pages and generate index data for each set of pages. 
Before you can index a report with the OS/400 indexer, you must create a set of indexing 
parameters. The indexing parameters describe the physical characteristics of the input data, 
identify where in the data stream the OS/400 indexer can locate index data, and provide other 
directives to the OS/400 indexer. 
Indexing parameters include information that allows the OS/400 indexer to identify key items 
in the print data stream, tag these items, and create index elements that point to the tagged 
items. The OS/400 indexer uses the tag and index data for efficient and structured search and 
retrieval. Y ou specify the index information that allows the OS/400 indexer to segment the 
data stream into individual items called groups. A group is a collection of one or more pages. 
Y ou define the bounds of the collection, for example, a bank statement, insurance policy, 
phone bill, or other logical segment of a report file. A group can also represent a specific 
number of pages in a report. For example, you might decide to segment a 10,000 page report 
into groups of 100 pages. The OS/400 indexer creates indexes for each group. Groups are 
determined when the value of an index changes (for example, account number) or when the 
maximum number of pages for a group is reached. 
Figure 7-4 on page 182 illustrates the data indexing and flow control for OS/400 indexer. For 
more information about the OS/400 Indexer, see IBM Content Manager OnDemand - 
Indexing Reference, SC19-3354.