ARSMAINT Issue - Out of support

Previous topic - Next topic

jsquizz

Hi all,

I'm working on an old CMOD system, we're in the process of getting on 10.5, but for now - We're stuck on 9.5 and out of support.

AIX 7.1
DB2 10.5.0.10
TSM 7.1

When we run arsmaint - Nothing is expiring. It almost looks like nothing is happening.

When I run:

arsmaint -cd -n 60 -x 70 -I archive -g <appgroup>

I get:

Message 30, Login, loopback local, (AIX), (ARSMAINT), (9.5.0.13)
Cache Expiration,: Date(2024-07-01) InternalDate(19906) MinPct(60) MaxPct(70) Server(cmod)

Nothing else happens when I execute the command. It hangs at the command prompt. This particular application group is using TSM. When i tail the TSM log, there's nothing other than a return code of 0.

Anywhere else I can be looking? This is happening for all other appgroups as it seems.
#CMOD #DB2 #AFP2PDF #TSM #AIX #RHEL #AWS #AZURE #GCP #EVERYTHING

JeanineJ


jsquizz

Quote from: JeanineJ on September 13, 2024, 01:33:09 PMDid you ever get your answer?

Yes, the script that runs arsmaint is overly complicated in my opinion.

It connects to db2 and does a select to get all the application groups. For some reason there was an environmental variable change, and that part was failing and i started to see "db2: command not found" which was weird.

Also there was a second arsmaint script hidden in crontab that was running only segment maintenance

My fix was to just do an arsdoc query against the System Load folder, and pull out app groups from the last 160 days (per retention settings), sort it, pass it in, and that seems to have fixed it.
#CMOD #DB2 #AFP2PDF #TSM #AIX #RHEL #AWS #AZURE #GCP #EVERYTHING

teera_aoo

Does your arscache filesystems utilization is relies to your parameter?
-n 60 -x 70 : meant if threshold over 70%, expire until it has been reduced to 60%.