trap not displaying missing process...

[gmorg]

Hi,


I attempting to set up event notification for agents reporting monitored process missing.

message comes to event consol as follows:-
OpenVMS SysAgtVMS Critical Message OpenVMS System Monitored-Process Alert on fred.smkts.com.au : Monitored Process has reported a Critical status

should this not display the actual process that is missing ?
we are Running TNG 2.4.2 integration to VMS on NT machines.
VMS system agent version 2.4.2 running on Alpha / Vax boxes.

Have noticed that the trap message coming into the console logs from the VMS system agent do not mention the name of the monitored process that has gone missing or critical.

This means we are unable to write meaningful message action records to take appropriate corrective action based on the process name.

Is this the way it is supposed to work ? How can we get the process name to appear in the message ?

2dmap / Nodeview / Agentview etc. are able to show the name of the process gone critical - only the TNG console log seems to be missing this information.

just noting that if we start up the missing process, the trap that is sent does display the process.

egevent from conlog)

Host:OpenVMS OpenVMS SysAgtVMS Trap Agent:SysAgtVMS:vmsLocal:vmsLclProcessFsm Critical Repaired SLNSERVER
if it can display it once it has been repaired, should it not also be able to display the process when it is broken ?????

Any advise would be appreciated.

 

[JonnoGT]

If you get a proper repaired message:
Host:OpenVMS OpenVMS SysAgtVMS Trap Agent:SysAgtVMS:vmsLocal:vmsLclProcessFsm Critical Repaired SLNSERVER
then you should get a proper critical message. EG:
Host:OpenVMS OpenVMS SysAgtVMS Trap Agent:SysAgtVMS:vmsLocal:vmsLclProcessFsm Up Critical SLNSERVER

If not then there is either message record policy hiding it or a bug with the agent.
I'd ask CA support

 

[gmorg]

F.Y.I.

well Im still currently working this issue with CA, Status at the moment is 2 files - the .cnf and .dat file for the VMS System Agent, are from 2.4, CA has suggested I upgraded to 2.4-2, which i am in the process of doing. have tried selecting the 2.4-2 files & copying them in

Stop awservices and then run the command "resetdsm", however this did not resolve my issue....

can only hope 2.4-2 upgrade will resolve !!!! here's hoping...