I am developing an object library that provides the services of the AMI. I am also porting this to NT by providing an ATL object wrapper for the base C++ class. The main idea being to provide consistancy of error/alarm handling across a multi platform MQseries system. Is anybody interested in this, have any comments, alternative approaches?
_________________
Alistair Rigney
Information Analyst
EDS Australia
[ This Message was edited by: AlistairRigney on 2001-05-17 18:00 ]
My intention was only to provide a standard interface that will use the low level AMI interface. Raising alarms and errors would be customised for each system. You could write to the unix syslog (on unix) or create NT events.
The best approach is to call some script that means that further customisation is possible. For example we are calling our unicenter api through a script interface to generate alarms. Alarms can also often be filtered by the system receiving the alarms, as our unicenter product does.
Hope this helps but its really up to your requirements. The point is that my interface does things like send acks where they are required. Standardises on the use of the AMI and hence in a large project your not reinventing the wheel and you get more functionality.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum