IBM Content Manager OnDemand PDF Indexer trace facility

An enhanced tracing capability for the IBM Content Manager OnDemand PDF Indexer is available. The tracing capability provides assistance to users who are attempting to debug problems, such as when the system fails during the indexing and loading of PDF documents.

To trace or debug a problem with the IBM Content Manager OnDemand PDF Indexer, the following are required:

The parameter file, which specifies the fields, triggers, indexes and other indexing information
The PDF input file to process

The parameter file and PDF input file can be processed by running the IBM Content Manager OnDemand PDF Indexer from the command line. For example:

arspdoci parmdd=filen.parms inputdd=filen.pdf outputdd=filen.out indexdd=filen.ind
tracedd=filen.trace

where

arspdoci: Name of the command-line version of the IBM Content Manager OnDemand PDF Indexer program
parmdd=: Specifies the name of the input file that contains the indexing parameters
inputdd=: Specifies the name of the PDF input file to process
outputdd=: Specifies the name of the output file that contains the indexed PDF documents created by the IBM Content Manager OnDemand PDF Indexer
indexdd=: Specifies the name of the output file that contains the index information that will be loaded into the database
tracedd=: Specifies the name of the output file that contains the trace information

See also: See your IBM Content Manager OnDemand Indexing Reference for more information about the parameters that can be specified when running the ARSPDOCI program.

After you run the IBM Content Manager OnDemand PDF Indexer with the trace, the output file that is specified by the tracedd=parameter contains detailed information about the processing that took place and where the PDF indexer is failing during the process. The trace information identifies whether a trigger was not found, a field was not found, the PDF data was corrupted, there was a problem extracting a PDF page from the document, or even if there was not enough memory or disk space to complete the required operations. The following is an example of the trace information that might be generated by the PDF Indexer.

COORDINATES=IN
ARSPDOCI completed code get_keyword <------------------
ARSPDOCI completed code get_keyword 003 ------------------>
TRIGGER1=UL(7.00,0.25),LR(7.70,0.57),*,'Page:'
ARSPDOCI completed code get_keyword <------------------
ARSPDOCI completed code get_keyword 003 ------------------>
ARSPDOCI completed code parse_trigger <----------------
ARSPDOCI completed code parse_quoted_parm <----------------
ARSPDOCI completed code parse_quoted_parm 001 ---------------->
ARSPDOCI completed code parse_trigger 001 ---------------->
FIELD1=UL(7.00,0.48),LR(7.90,0.77),0,(TRIGGER=1,BASE=0)
ARSPDOCI completed code get_keyword <------------------
ARSPDOCI completed code get_keyword 003 ------------------>
ARSPDOCI completed code parse_field <----------------
ARSPDOCI completed code parse_subfields <----------------
ARSPDOCI completed code get_keyword <------------------
ARSPDOCI completed code get_keyword 003 ------------------>
ARSPDOCI completed code get_keyword <------------------
ARSPDOCI completed code get_keyword 003 ------------------>
ARSPDOCI completed code parse_subfields 001 ---------------->
ARSPDOCI completed code parse_field 001 ---------------->
FIELD2=UL(6.11,1.39),LR(7.15,1.57),0,(TRIGGER=1,BASE=0)
ARSPDOCI completed code get_keyword <------------------
ARSPDOCI completed code get_keyword 003 ------------------>
ARSPDOCI completed code parse_field <----------------
ARSPDOCI completed code parse_subfields <----------------
ARSPDOCI completed code get_keyword <------------------
.
.
.
ARSPDOCI completed code get_keyword <------------------
ARSPDOCI completed code get_keyword 003 ------------------>
ARSPDOCI completed code arspparm_final_sanity_check <----------------
ARSPDOCI completed code arspparm_final_sanity_check 001 ---------------->
ARSPDOCI completed code ArspProcessOpt <------------
ARSPDOCI completed code ArspOpenIndex <-------------
ARSPDOCI completed code ArspOpenIndex 001 ------------->
Adobe PDF Library version -732512488.-1
Editing is :-1
Number of input pages =130
ARSPDOCI completed code ArspProcessOpt:Calling ArspSearchDocPages()
ARSPDOCI completed code ArspSearchDocPages <------------
ARSPDOCI completed code ArspSearchDocPages:ArspCreateWordFinder()
ARSPDOCI completed code ArspSearchDocPages:PDWordFinderAcquireWordList()
ARSPDOCI completed code ArspSearchDocPages:PDDocAcquirePage()
ARSPDOCI completed code ArspSearchDocPages:ArspSearchPage()
ARSPDOCI completed code ArspSearchDocPages:PDPageRelease()
ARSPDOCI completed code ArspSearchDocPages:PDWordFinderReleaseWordList()
Trigger(s)not found by page 1
ARSPDOCI completed code ArspSearchDocPages 004 ------------>
ARSPDOCI completed code ArspProcessOpt:Calling ArspCloseIndex()
ARSPDOCI completed code ArspCloseIndex <------------
ARSPDOCI completed code ArspCloseIndex 001 ------------>
ARSPDOCI completed code ArspProcessOpt:Calling PDDocClose()
ARSPDOCI completed code ArspProcessOpt 002 ------------>
ARSPDOCI completed code 1
ARSPDOCI completed code ArspFreeParms ()