WARNING - ARSDOC GET -X <loadid> issues

[sisusteve]

I just wanted to let you know of a potential issue with the arsdoc get -X <loadid> command in that it may not extract all of the documents associated with the specified <loadid>.

the reason for this is that arsdoc get compares the index values that were originally loaded in the nFAA1 file with the current database values, if the values don't match, the document is excluded from the extraction.

IBM states that this is operating "as designed" and is not a bug, go figure.

So be warned, if you use the OnDemand32 Document Audit Facility (DAF), arsdoc update, or any other methods to update your index values in CMOD, you're at risk of not extracting all documents.

[Justin Derrick]

Is that to say that the source of the index values when running 'arsdoc get' is the *FAA1 file, and not the database table when using the -X parameter? 

-JD.

[Lars Bencze]

Oh my gosh!
This fits a problem we currently have.
I gives me an idea on how to reproduce it too - if I understand correctly, we need to edit the metadata of one or more of the records, and then arsdoc get -X will fail to return all documents?
Holy crap, that's scary. And yes, we have probably lost some real data due to this.

[Justin Derrick]

This differs from my experience with arsdoc, and I only very rarely use the -X option, but only the source code would tell us for sure.  I think you posted in an alternate thread that you're working on it.  Please report back to let us know the outcome.

-JD.