Trace facility
The tracing capability for the PDF indexer provides assistance to users 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 PDF indexer, the following is required:
- The parameter file, which specifies the fields, triggers, indexes and other indexing information
- The PDF input file to process
- The trace parameters tracedd and tracelevel
The parameter file and PDF input file can be processed by running the PDF indexer from the command line. For example:
arspdoci parmdd=filen.parms inputdd=filen.pdf outputdd=filen.out indexdd=filen.ind
tracedd=filen.trace tracelevel=PDF=15
Where: arspdoci
is the name of the command-line version of the 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 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.tracelevel=
specifies the amount of detail to be included in the trace.
After running the PDF indexer with the trace, the output file specified by the
tracedd=
parameter will contain detailed information about the processing that took
place and where the PDF indexer is failing during the process. The output file must be formatted by
the arstfmt command to create a readable trace file. For example:
arstfmt -i filen.trace -o filen.trace.output
Remember: The ARSPDOCI command is not supported on z/OS or
Linux for System z platforms..