Loading Future Dates

[rstockton]

Is there a way to prevent CMOD from loading a date greater than current date as a segment date?



Thanks
RS

[pankaj.puranik]

The only way I can think of is through writing a user exit (index records exit). This exit program would check the indexes and would add, remove or verify them  and would produce an output that is then written to the index output (.ind) file.

I think this way it is possible to remove the date that's greater than the current date.
But I am not sure if you want to discard the data (document) that is associated with this future date.
If that's the case I am not sure how one can achieve this.

Thanks
Pankaj.

[rstockton]

Thanks Panjak.

What I am trying to do is to have the load fail if the date is greater than current date.

Thanks
RS

[Justin Derrick]

Hi Guys.

That sort of data validation doesn't belong in CMOD.  It belongs upstream, where the data is generated. Failed loads create a bit of a mess - they are exceptions that must be handled manually by an administrator, and they create a failure messages in the System Log, and waste CPU time and I/O.  If you have a data quality issue, that needs to be addressed where the data is created.  CMOD is an archive -- the ultimate long term storage facility for documents, not a data validation tool.

As a very last resort, I'd consider writing a script on the server to test the data before handing it to CMOD, but really your management should be pushing back on the source of the data to perform proper validation.

-JD.

[rstockton]

Thanks Justin.

I am famliiar with processing and handling failed files as I have handled several instances in the past.  I was just checking to see if OnDemand might have built something in that I could set for future loads.  We are creating several new Application Groups for varied input systems and I wanted to fail any bad dates during testing.

Thanks,
RS