How can I identify a COLD background template document id that was deleted from IBM FileNet Image Services?

Answer

An easy way to find out the document id of the background template to print the document from an IDM Desktop or ISRA client. An error should occur and the document id of the background template may be contained in the print job.

Another option to find out the document id of the background template, if the compress option was not used in the COLD format configuration, is to run the CSM_tool Objecttofile command and create a disk file of the COLD document page when it is in page cache. For example:

CSM_tool
<CSM_tool> OBjecttofile 1 10312008 249841 1 249841.obj
<CSM_tool>quit

Next, run the UNIX vi command on the file.

\306\304`d``TALK^K^R^N200
^Wlaser/COLD20x32
^M^N00.000I,^N0,^N00.250I,^N0
^P^N249840,^N1,^N10312008

The document id of the background template is shown as 249840 and the SSN number of the server where the document was created is shown as 10312008.

If COLD's Page Compression was enabled at the time of committal than the task becomes a little more difficult because the contents of the page cannot be viewed due to the compression. Then the next option would be to use eladisp on the Image Services server and filter on the IP address of a client (IDM DT or ISRA) station.

The eladisp command must be run with the options shown below. All of the output from eladisp is redirected to the output file name eladisp.out

eladisp
eladisp> en ev csm inx
eladisp> ass trace 128
eladisp> ass bind 0 csm inx
eladisp> set trace_byte_dump on
eladisp> en tra 0
eladisp> assign chfilter 0[xx.xx.xx.xx] (where xx.xx.xx.xx is the Client IP Address)
eladisp> show tra 0 > eladisp.out

The next step is to login to the IDM or ISRA client and query for one of the COLD documents that has the missing background template.

After the query returns the document id, attempt to display the document. An error should be generated reporting the background template is missing.

On the Image Services server, enter Control-C to get the eladisp prompt and then enter quit to exit the program.

Use the UNIX "more" or "vi" command to display the eladisp.out file

Search for CSM:OpenCsumObject. The document id of the COLD document should be displayed.

-------------------------------------------------------
$163 CSM:OpenCsumObject 17:53:25.740 0.00 Secs 0.00 KB
NETID = [9.48.84.189,50949]
000 00 e4 5b 00 00 9d 59 48 00 02 15 e2 00 01 00 01 | ..[...YH........
csh = 0xe45b00 (14965504)
object = RECORD [
ssn = 0x9d5948 (10312008),
id = 0x215e2 (136674),
pageNumber = 0x1 (1)
]
mode = read(0x1)

-------------------------------------------------------

Next search for aborted.

-------------------------------------------------------
$170 INX:GetSingleDIR 17:53:28.690 0.00 Secs 0.00 KB (aborted, Reason = 0x6
NETID = [9.48.84.189,50954]
000 00 e3 5b 03 00 02 14 92 00 00 00 00 | ..[.........
h = 0xe35b03 (14899971)
docId = 0x21492 (136338)
lock = false
override = false

-------------------------------------------------------

The document id of the background template will be contained in the aborted message.

Finally the last option would be to enable GDBdebug tracing:
GDBdebug -s 9999

Retrieve the document to get the error, then turnoff the tracing:
GDBdebug -s 0000

The output will be saved in the trace file created:

/fnsw/local/logs/gdb_logs/GDBdbg<pid> for UNIX platforms
<drive>:\fnsw_loc\logs\gdb_logs\GDBdbg<pid> for Windows

Review the trace file, the document id of the background template will be contained in the aborted message.