Operations agent on OpenVMS cluster

[Risto Tolonen]

Hello,
I'm wondering if I could get any help here.
I've tried installing openview operations for unix agents on a cluster. The other one is almost working now, just little communication problems, but the other one isn't. I installed it after the first one with the command PRODUCT INSTALL OVOAGENTS, and the installation went without errors. But when I try to start the agent, nothing happens. No errors, no logs, nothing. The process isn't running. It simply returns to the prompt. Have I installed it somehow wrong, taking in consideration that this is a cluster, and the first one works? Can anyone help me troubleshoot this?
BR,
Risto

[Anton van Ruitenbeek]

Risto,

Aren't there any .COM procedures in SYS$STARTUP: ? The best thing (and to be honist the only way) is to go for these files, look into and try to figure out what is going on.

Otherwhise is don't even get a glue wat is going on.

Most of these things (HP Openview, SAN monitor) are ported from .nix and it looks like they ad some startup procedures to it without any knowledge of VMS and (real) clusters.

AvR

[Risto Tolonen]

Hi Anton,
I've opened a support case with HP, and delivered them the info they requested. I'm waiting for answers now.
I'll leave this thread open and post the solution when it is figured out, so someone with a similar problem might get help.
But thanks for the help!

BR,
Risto

[Mobeen_1]

Risto,
As suggested in the earlier post try to look up with the following commands

$dir sys$update:*AGEN*.com

Not sure what the startup file for OVOAGENTS is .. else try the following command and look through....the output for the file you think starts the OVOAGENTS

$dir sys$update:*start*.com

If i were you, i would try the following first :)

$ search sys$update:*.com OVO

In any case the startup file for your product should be here by default

Let us know how it went :)

rgds
Mobeen

[Risto Tolonen]

Hi,
Don't worry, the files are there, I've checked all the startup files, and the problem occurs exactly at the point where opcagt -start is run. So the problem is quite awkward. But the case is handled at the moment by OpenVMS agent's development team (at least I think that's who they are, since I don't contact them directly, but through support), so I'll get answers probably soon. We'll see. :)

BR,
Risto