Messages

1

MP Server / Re: Successful Load Fails to Unload

« on: June 21, 2022, 02:12:34 PM »

Thanks for the suggestions Justin.   I should have mentioned I had also tried with the -Q and -N options yesterday, to no help.  I just tried your other suggestion, running with -L 13031-46-0-57FAA and unfortunately still got the same result.  I always thought the load id had to match exactly but your last suggestion leads me to believe that CMOD looks for load IDs starting with the value after the -L parm.

2

MP Server / Successful Load Fails to Unload

« on: June 20, 2022, 11:00:10 PM »

A group of reports with the load id below loaded successfully a few days ago.  Today I get an error when trying to unload this load.  Same load id.  I've verified in the System Log that it has not been unloaded since being loaded.  I can also view the load's reports in the client.  Only thing slightly different is this is our test environment, which I don't believe we've ever run an unload against.  I've probably run at least a dozen such unloads in our prod environment.  Anyone ever run across such a thing?

arsadmin unload -g ApplGroup -u admin -p xxxxxxxx -h testsrvr -L 13031-46-0-57FAA-20220616000000-20220616000000-13032
The option >-L< argument >13031-46-0-57FAA-20220616000000-20220616000000-13032< is invalid

3

Other / Re: Is System Log data stored in DB only or in Cache?

« on: June 17, 2021, 10:42:58 PM »

Oh, gotcha now.  Yes, I definitely have System Log data in cache in that case.  Thank you for spelling it out for this newbie.  :-)

4

Other / Re: Is System Log data stored in DB only or in Cache?

« on: June 16, 2021, 10:22:48 PM »

I searched for %View% in the Message of the System Log for the last 6 months and got no hits.  I guess I can reasonably assume, therefore, that my installation stores all the System Log messages in the DB alone, with no data in the cache file systems.

5

Other / Is System Log data stored in DB only or in Cache?

« on: June 15, 2021, 10:24:41 PM »

Does anyone know if the System Log data is stored in the DB only?  Or does index information get stored in the DB and data in a cache file system like with a normal report application?

6

MP Server / Re: arsload fails in 8.5.0.5

« on: June 15, 2021, 02:53:15 PM »

Thank you for that information.  It is helpful.

7

MP Server / Re: arsload fails in 8.5.0.5

« on: June 08, 2021, 06:22:44 PM »

Ok, I know this topic is extremely old but... I am facing the exact same issue using CMOD v9.0.0.1 and wonder if anyone knows if the fix for it ever made it past the patch level and into release 9.0.0.1?  Normally I would open a ticket with IBM but my customer is not currently paying for support plus v9.0.0.1 is way out of support.... Yah........

8

Other / Re: ARSMAINT is not Expiring/Removing Documents Past their Retention Period

« on: March 04, 2020, 09:40:38 PM »

We are not getting any warnings or errors.  As for running an outdated version, I'm afraid it's what I'm stuck with for now.  But thank you for some very good sounding suggestions as to other things I can try.  I'll let you know what I learn.

9

Other / Re: ARSMAINT is not Expiring/Removing Documents Past their Retention Period

« on: February 28, 2020, 11:24:24 AM »

Expiration type is Load.

10

Other / ARSMAINT is not Expiring/Removing Documents Past their Retention Period

« on: February 27, 2020, 11:13:24 PM »

We run CMOD v9.0 on AIX with the Windows and ODWEK clients.  Our ARSMAINT seems to process only a finite number of application groups when expiring reports that have passed the retention period.  Sometimes it processes only 1 or 2 groups, sometimes a dozen or a few dozen.  But we have 352 application groups in total.  And there is one application group in particular with 7-year retention period that should be getting reports expired from the January 2013 – February 2013 time period; those reports are not getting expired/unloaded.  Below is the command that is run as root.  You can see that we are not passing any specific application group(s), which should mean (I think) that all application groups get processed.

/usr/lpp/ars/bin/arsmaint –cdeimrs

Can anyone think of any reason why all application groups would not be getting processed?  How does ARSMAINT determine which application groups get processed?  And in what order (or is it just random)?

11

General / Re: Do I need to bounce OnDemand to refresh a changed exit routine (ARSLOG)

« on: February 18, 2020, 04:52:48 PM »

Figured it out.  And figured it must be something silly that I just wasn't seeing.  Turns out there is a duplicate set of directories on our test server - one set matches the production server and one set does not.  And it turns out that the test server is running from the other (non-matching) set of directories.  So I've been updating arslog in a bin directory that is not used by the CMOD instance.  So sorry for wasting your time on this.  I do appreciate all your help, for what it's worth.....

12

General / Re: Do I need to bounce OnDemand to refresh a changed exit routine (ARSLOG)

« on: February 17, 2020, 07:33:11 PM »

Been there, done that.  All boxes under User Exit Logging are selected.  Why this arslog exit is not getting executed is a mystery.
 Only thing left I can think to try is bounce OnDemand, which will only help if this exit truly gets stored in memory when CMOD starts rather then being executed dynamically in CMOD's bin directory, which seems kind of hard to believe........

I appreciate the warning about server performance.  We'll keep a close eye on that when we implement this in production as I have the same concern.  First though, I need to get this thing tested on our test server, which basically has zero activity right now except for my own logins, logouts, queries, and that "every-30-minute ping" from arssockd.

13

General / Re: Do I need to bounce OnDemand to refresh a changed exit routine (ARSLOG)

« on: February 13, 2020, 09:41:12 PM »

We're running a rather dated version of CMOD - 9.0.  We use arslog to send notifications for certain Alert and Error level messages.  The latest requirement is an audit requirement which has us writing every single message (believe it or not) to a new log file.  I can run arslog from the command line, passing it test parameters, and it works fine.  But CMOD seems to be ignoring the change.  I have verified that logging is turned on, both system logging and application group logging, in the System Parameters.  Granted, we have nearly zero activity in our test environment, but even the act of logging on and logging off should invoke the exit and cause a message to be written to the new log file.

14

General / Do I need to bounce OnDemand to refresh a changed exit routine (ARSLOG)

« on: February 12, 2020, 10:44:02 PM »

I changed the ARSLOG exit but my change is not being used by OnDemand.  Do I need to bounce OnDemand to pull in a fresh copy of the exit?  More generally, does OnDemand pull the exits into memory on startup or does it dynamically execute whatever code is in the exit?  Our OnDemand instance is running on AIX.