When it comes to data that can't have the index information extracted automatically via the built-in indexers, administrators must provide the metadata for documents in Generic Index Format before loading happens.  For images of documents, there are Optical Character Recognition tools that can output scanned images in a format that is compatible with CMOD.

I'm not sure what "IBM RPA" is, maybe you could describe that a little more to see if we can help.

-JD.

Hello All,

Does anyone aware about loading images into CMOD 10.5 without being able to extract index information from it.
Do we need to generate indexing file before attempting to load it into CMOD or is there way to manage it within CMOD ?

I am aware about one situation where there were 30k plus docs(word files) sitting on the file system and IBM RPA script was used to push those documents into CMOD.


Thanks,
Mayank

In our case we have not seen any such behavior either as it is flushing load ids which are due to be removed irrespective of any fixed number like 100 

CMOD 10.5.0.5

I remember it not working at all post CMOD upgrade and then we followed below IBM technote which resolved our problem and it started working again.

https://www.ibm.com/docs/kk/cmofm/10.5.0?topic=linux-creating-arscache-file-instance

I see the same behavior on multiplatform 10.5.0.8 as we see a 456 msg showing 100 loads expired, then it will expire those loads and move on to the next group where another 456 msg will show 100 loads and continue on.

You specifically want to read the section on the 400 Indexer, which is used on IBM i.
https://www.ibm.com/docs/en/cmofi/7.5.0?topic=ondemand-400-indexer

Archiving spooled files is done using an output queue monitor.  This documentation should be helpful as a starting point.
https://www.ibm.com/docs/en/cmofi/7.5.0?topic=ondemand-loading-spooled-file-data

Start here and reply back with any questions:

https://www.ibm.com/docs/en/cmofm/10.5.0?topic=parameters-index

-JD.

Is this what I should be looking at?
 (Applications/indexer information/Details button)
I see the wrong field in question, entity, but have no idea what the parameters mean.


All of it:
CC=YES
CCTYPE=A
CONVERT=NO
CPGID=37
MCF2REF=CPCS
TRC=NO
FILEFORMAT=RECORD
TRIGGER1=*,1,X'F1',(TYPE=GROUP)                          /* 1      */
TRIGGER2=*,*,X'61F2F0',(TYPE=GROUP,RECORDRANGE=(1,4))    /* /20    */
TRIGGER3=*,23,X'4B',(TYPE=GROUP,RECORDRANGE=(2,6))       /* .      */
FIELD2=0,-4,9,(TRIGGER=2,BASE=TRIGGER)
FIELD3=4,-12,35,(TRIGGER=3,BASE=TRIGGER)
INDEX2=X'A8858199',FIELD2,(TYPE=GROUP,BREAK=YES)         /* year   */
INDEX3=X'8595A389A3A8',FIELD3,(TYPE=GROUP,BREAK=YES)     /* entity */
DCFPAGENAMES=NO
UNIQUEBNGS=YES
IMAGEOUT=ASIS
INDEXOBJ=GROUP
INDEXSTARTBY=1
INSERTIMM=NO
RESTYPE=NONE
DOCTYPE=AFP

Ah, I misunderstood the problem.  I thought the data in the 'hitlist' was showing up in the wrong column.

If you have an indexing issue, that's more problematic.

Indexing happens at the Application Level, on the Index Parameters tab.  Those are the instructions for getting the data from the PDF file, that will be inserted into the database, which users will search, and see the results in the hitlist box.

If you're not getting the data that end users want, then your indexing parameters need to change, and for that, your best bet is to go through the Indexing Reference.

https://www.ibm.com/docs/en/cmofm/10.5.0?topic=ondemand-pdf-indexer

Good luck!

-JD.

Thanks for you quick reply. But on number 1, how the heck is it pulling data off a report based on what is defined in Field Mapping. I just see a field defined, and it follows through and somehow auto magically strips data off the report. I see nowhere to define where that data is on the report.

On the second question, the system log just shows a log on and log off by the user.

Thanks!

Hi Tom.

If the wrong field data is showing up in a specific column of the search results (the 'hit list'), then you likely have a mapping issue at the Folder level. 

Folders are a way of abstracting the complex data defined at the Application Group level (database field names) and presenting a human-friendly interface to end users.  A database field may be called "rdate" at the Application Group level, but defined as "Report Date" inside the folder.  Inside the folder definition, you must map App Group fields to Folder fields -- and from what you describe, it sounds like the wrong field (from the Application Group) is mapped to the folder field.  If you have multiple Application Groups mapped to a folder, you'll need to investigate each of the mappings to find the one that is 'bad'.

Second, to find more diagnostic info about failed loads, you need to log into the CMOD Client and access the System Log folder.  Search for a severity of 'error' to find all of the errors being recorded in CMOD.

-JD.