380 IBM Content Manager OnDemand Guide
/SM590000Problem: Content Manager OnDemand indexing fails when only one field is defined for an 
application group.
Reason or resolution: The Content Manager OnDemand file name indexing feature 
needs at minimum one index and a field value that are defined in the application indexer 
parameters. 
Verify that you are using a file name index with one field that is defined in the application 
group and no field or indexing parameter defined for the application. If these conditions are 
true, you must use a field. Y ou can define a dummy literal index and field value in the 
application indexing parameter as a placeholder. This dummy value is not processed, but 
it allows the file name to be indexed successfully. 
/SM590000Problem: Content Manager OnDemand does not break up the PDF file into separate 
reports when TRIGGERs are defined correctly and indexing is successful. For certain 
reports, the trigger is not honored and the reports are grouped.
Reason or resolution: The field value must change for Content Manager OnDemand to 
indicate a report break. In Figure 18-2, there are several pages of a document. Page 1 is 
the TRIGGER, and the name is the field that is placed into the index.
Figure 18-2   Sample document for indexing
In this example, because the string Page 2 does not match the TRIGGER, it is ignored, 
and that page is included in report 1. Moreover, the report does not break until the name 
John Smith is read because it is different from the name John Doe.
/SM590000Problem: When the user views a document that is loaded with large object (LOB), the 
client receives the message:        
Viewer Page count does not match Load Page Count. Viewing may be adversely 
affected. Contact your system administrator. 
If the user clicks OK, the document can be viewed in its entirety, except that the page 
number is incorrect.
Reason or resolution: When a document is loaded as LOB, the Loader must count the 
pages, because a certain number of pages go into a LOB segment. When the client 
retrieves a LOB segment, the client also counts the pages that it receives from the server. 
The user will receive the message “Viewer Page count does not match Load Page Count” 
when the two page counts do not match.
This problem is usually caused by the user running ACIF to load a document that contains 
the form feed character x'0C'. ACIF does not support the form feed character as the start 
of a new page, but the line data viewer does support the form feed character as the start of 
a new page. Therefore, the viewer ends up with a different count of pages than the loader.
If you use the asciinp exit, ensure that the exit was not modified and recompile the exit. 
Page 1
John Doe
Page 2
John Doe
...
...
Page 1
John Doe
...
Page 1
John Smith