CMOD CLEANUP

[DDP021]

Hi,  We're in the process of attempting to cleanup non-active applications.  Our systems group has provided us a huge list they were able to retrieve of those applications not having anything loaded to them.  What we found was, during the cleanup, we found applications that were sending data to CMOD that would load one day, and get removed the very next day due to that actual data having dates older than the set retention being used..So as an example, if the retention was set for 7 years, and if the application was using a  POSTING DATE off the data and that date was going back further than 7 years, ARSMAINT was removing the version automatically...With the removal of the application, this causes us to receive 88 messages.  Just curious of there is ANY way of determining, ahead of time, what other applications are doing this so we can reach out to them to verify if the application id can be removed from CMOD.

[DDP021]

here's an example of what we occasionally run into..(see attachment) You can see the document was loaded into CMOD on 08/31 and then on 09/01 it was removed by ARSMAINT...Not sure how this could even be searched

[Justin Derrick]

The date on that document is from 2003.  You have a data quality issue or indexing/default value problem, not an arsmaint problem.

I suppose the best way to find this is querying the system log for a specific App Group name, and see if you've log loads happening one day and expiring the next.

I don't see any simple/quick/easy way to identify this issue without a lot of programming.

-JD.