There are two sides to this: 1) Monitoring locks 2) Remote notifications As with any process where you have data generation and an interface with data consumers, separate the components and the task gets much easier. Nick provided info about how to generate the data so I'll comment on notifications.
You can use email or you can popup notifications on the PC of an admin when something on the server requires attention. I blogged about this here: nospamNebula-RnD.com/blog/tech/mv/2008/09/remotecontrol1.html Note, that talks about remote control (and notifications) as being a new product offering. Though that was the intent and the software works well and is very cool, this has not been productized for lack of interest. Oh well. To do this yourself, write a program that runs in the tray or as a Windows service. Ping the server periodically (using your favorite language and connectivity tools) for data of interest. Report that data back to the user on the PC with the level of annoyance only commensurate with the level of urgency. If you want a tool that already does this, let me know. HTH Tony Gravagno Nebula Research and Development TG@ remove.pleaseNebula-RnD.com See PickWiki.com - Lots of recent updates: http://PickWiki.com Intro to PickWiki, notes about error handling, PDA development, PDF reports, rich spreadsheets and much more: nospam.pleaseNebula-RnD.com/blog/ > From: Steve Romanow > I am trying to devise a way to remotely monitor long > held locks and lock contention. > > My best thought so far was to write a basic program to > parse the output of LIST.READU and start notifying > people with mailx. > > Has anyone got any better ideas on detecting users who > have left records locked for an inordinate amount of > time? ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
