Chapter 7. Indexing and loading 179
14       EAG End Active Environment Group
15       BCT Begin Composed-Text Block
16         PTX Presentation Text Data
17       ECT End Composed-Text Block
18     EPG End Page
19   ENG End Named Group
20   BNG Begin Named Page Group 00000002
...
4590   ENG End Named Group
4591 EDT End Document
Each group is surrounded by BNG/ENG Structured Fields, and each group contains TLE 
Structured Fields that occur after the BNG but before the BPG.
When an input file contains TLE Structured Fields, do not specify indexing parameters, such 
as TRIGGER, FIELD, or INDEX. They are not needed because the file already contains index 
information.
ACIF processes a file that contains TLE Structured Fields in the following way:
1. For every BNG in the input, ACIF creates a group IEL Structured Field in the index file.
2. ACIF makes a copy of the TLE Structured Fields from the input and places them into the 
index file. The original TLE Structured Fields are also placed into the output file.
If the input file does not contain the correct number of TLEs in each group, ACIF might 
complete, but arsload might fail with the following message: 
“x fields submitted, n expected”
The n is the number of fields that are defined to Content Manager OnDemand. 
After ACIF processes an input AFP file, the output file might be larger than the input file, even 
if the input was an AFP file. The answer is because ACIF changes the AFP , “improves it”, and 
usually increases the file size. The following changes are made to the AFP: 
/SM590000Creating or adding comments to the BDT Structured Field
/SM590000Creating or adding group names to the BNG - ENG Structured Fields
/SM590000Changing obsolete Structured Fields to current Structured Fields (for example, MCF1 to 
MCF2, or PTD1 to PTD2)
7.5  OS/390 indexer on z/OS and AIX
The OS/390 indexer is supported on both the z/OS and AIX implementations of Content 
Manager OnDemand. The indexing parameters are the same for both implementations. If you 
are migrating from z/OS to AIX, or from AIX to z/OS, you can continue to use the OS/390 
indexer and not change your indexing parameters.
Y ou can use the OS/390 indexer to extract index data from line data and AFP reports. In 
addition, other data types, such as TIFF images, can be captured by using the ANYSTORE 
exit (ANYEXIT is described in 11.3, “OS/390 indexer exits” on page 248).
The OS/390 indexer is a single pass indexer. (It does not create an intermediate file.) It 
therefore provides better performance than ACIF . The COBOL Runtime Library is required on 
AIX to run the OS/390 indexer, and it is included in the Content Manager OnDemand 
Multiplatform software.