There's a few reasons not to do this...

- The file it generates may be *enormous*, especially if the loaded files were compressed.
- Older versions of CMOD had issues generating generic index files over 2GB in size, rolling over the byte offset back to 0.
- Loading a single large file with data that spans years may break expiration processing, especially if the expiration type is 'Load'.
- Any error retrieving data from CMOD will result in the entire extract failing.
- If there's more than a couple thousand documents, you'll quickly reach a point where your filesystem will be overwhelmed, and simple commands (ls / cp / mv / rm) will take several minutes.

Most folks extract by Load ID or date or by a mostly-unique ID like customer number, etc.

If this is a particularly large job, reach out to me via eMail -- I have a fast & automated extraction utility I use for migrations.

-JD.

Sounds like it would be a good enhancement request.  :)

-JD.

Just a quick note to let you know we were down for a little over 24 hours due to a blackout in the area -- the VM server came back up after power was restored, but the individual VM didn't restart automatically!

We'll be fixing that issue by moving to a small cloud server in the next week or so.

-JD.

Excellent.  I'm glad to see you got the problem resolved.  Take care!

-JD.

That adds some clarity, but unfortunately we still can't answer your question, because we don't know what your site's backup strategy is, and if it relies on being able to access these files to complete a database restore to a particular point in time.  You'll have to determine this with the help of your in-house database administrators and enterprise backup teams.

-JD.

We don't have enough information on your system design to answer the question.  That's not a standard folder name (as per the Installation Guide) so we don't know what's being stored in there.

-JD.

Just guessing, but there's probably more than one record pointing to the same document.  I've seen this at banks where more than one customer is listed on a mortgage -- two records in the database table will point to the same document for a mortgage statement.  You should try using the options -agcNv to export them with the Generic Index File, then look for two records with the same offset & length.

Hrm.  I was hoping the indexing parameters would be helpful, but I don't see anything there. 

It sounds like these are temporary files - is your ARS_TMP configuration parameter set to the same directory that you're loading from?  If so, changing it to another directory might move these out of the way, although it doesn't answer the question about what's in them.

You can use the UNIX/Linux 'file' command to see if the OS recognizes the file format:
  file Load.File.PDF.out?

This should give you the best guess for each data type.  If it can't determine what it is, the response will be 'data'.

-JD.

Adding your PDF indexing parameters from your Application Definition, and showing the relative size of the files will help us figure it out.  :)

-JD.

Basic troubleshooting steps:

 - Make sure the command you're running specifies the full path to the stash file. (/home/archive/ARCHIVE.stash rather than ARCHIVE.stash)
 - Double-check your user id and permissions - does the OS allow you to access the file?

Easiest way forward would be to back up the original stash file and create a new one in its place -- if you don't know the current password, you can change it through the admin client to a new password and use that password to create the new stash file.

Of course, if you create a new one, make sure the OS ownership and permissions are restrictive enough to be secure.

Good luck, and please report back with a resolution.

Thanks.

-JD.

Odd question.... How much RAM does this system have? 

And just as a recommendation - ask if the notifications can be "smoothed out" by only sending a few emails per second, or schedule them to be sent in the middle of the night, so people don't all click on them as soon as they're sent.

-JD.

I'm not familiar with IBM RPA, so I don't know if it could be integrated into your OCR system.  That sounds like a question for IBM.

-JD.

Please use our enhancements forum instead, so we can present the item to IBM as part of the next Enhancements Discussion with IBM.

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.

Start here and reply back with any questions:

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

-JD.