Differences between ARSMAINT in 8.4 to 8.5

[jeffs42885]

Hi All,

I am currently working with IBM support on this and I am a bit puzzled. After we upgraded to 8.5.0.6, our ARSMAINT purge process stopped working. Here are some details.

Here is something else I noticed..Keep in mind that the script begins to run at 11PM on Fridays.

I did a 127 check on our contingency server for the last hit:

12/08/2012 12:06:20   ODADMIN      15138944   Info   No      127   ApplGroup Load Expire:  Name(AG1) LoadId(6939-3-0-93FAA-11668-11668)
   
We upgraded to 8.5.0.6 On the weekend of 12/14 - 12/15 on our Contingency site.

I did a 127 check on our production server for the last hit:

01/04/2013 23:49:51   ODADMIN      59572410   Info   No      127   ApplGroup Load Expire:  Name(AG2) LoadId(6043-2-0-22522FAA-11695-11695)

We upgraded to 8.5.0.6 on the weekend of 01/11 - 01/12 on our Primary site.   

Is there something that we need to change in the syntax of our ARSMAINT command? Perhaps something added to ars.cfg / ars.ini?

[Justin Derrick]

Is your only concern that it takes longer to run?  Or is it that your "AG1" App Group didn't expire anything? All you've said is that it was the "last" item returned in the hitlist, not that AG1 didn't get expired.

If it's the fact that it runs longer, that IS an issue with CMOD 8.5, as the new (and more secure) hashing method can slow down things like load processing.  Otherwise, I'm not exactly sure where the problem is, or what's behaving differently between versions.

-JD.

[jeffs42885]

After we upgraded both sites, we do not see 127 messages in the system log when the ARSMAINT jobs run.