Re: Parse Spooled Files

On 10 Jul 2013 12:47, CRPence wrote:

On 10 Jul 2013 12:06, Dan Kimmel wrote:

V4R5. I need to parse the data in 36,000+ spooled files. One time
deal. Any suggestions how I could quickly make them all parseable?

One thought is to set up a remote outq to an outq on a V7R1 box
<<SNIP>>

Or after sending those [if only SCS] spools to the 7.1 system, use
the OmniFind with the extension to index those spool files. <<SNIP>>

From the "Nicholas Lawrence" link likely presented in the results from the web search I had offered in my prior reply [but snipped in the quoted reply], is some more specific commentary with regard to accessing SCS SplF data, which seems consistent with the described scenario:

http://www.ibm.com/developerworks/ibmi/library/i-omnifind/omnifind.html
"...

_Adding object sets_

After creating the text search collection, OmniFind needs to know which objects to index. An object set defines a set of objects that will be included in the text index during the update process.

The OmniFind extensions support two types of object sets.

* Spool Files in an output queue
* IFS Stream Files in a specific IFS directory

Adding an object set does not update the index with the text data from that object set. OmniFind will update the index with the text from these objects during the next update, which will happen when the UPDATE stored procedure is called, or when a scheduled update runs.

_Adding a spool file object set_

The ADD_SPLF_OBJECT_SET procedure was created to add spool file object sets when the text search collection was created. There are actually a number of different versions of the procedure, and we can use any of them to select which spool files to index.

For example, this procedure will add a spool file object set for all spool files in an output queue NTL/MYOUTQ:

CALL ADD_SPLF_OBJECT_SET(‘NTL’, ‘MYOUTQ’);

...

_Update the Collection_

...

_Search the collection_

..."