Feature requests

Hi Guys

I don't believe the products do the following and it would be very desirable if they did.

Event server; allow more 24x7 scheduler style macro-parameters within file-watch path and file ie
\\server\directory\@T"yymmdd"\file.txt

24x7/Event server; file watch option to watch for a file then when it is found don't watch again till it changes so I could use a data file as a semaphore.

Yes, currently it doesn't support macro-variables in event definitions, but its rich set of event monitors usually allows picking an event that can serve the purpose without using such values. For example, "watch for a file then when it is found don't watch again till it changes so I could use a data file as a semaphore", you can create a file contents watch monitor rather the file object watch. This way in both cases when a new file gets created and existing file is modified you can catch such event. You can also create 2 separate watches, one for new files and one for file changes. Both can run the same action, batch file or for instance trigger the same job in 24x7 Scheduler. You can also create a single file object watch monitor using generic event that would trigger the associated action whenever anything happens to the monitored file or files. You can also use file masks to monitor for multiple files using single event monitor.

In the end, you can also create a file watch using WMI event type with a custom WMI query. For instance, in the WMI query WHERE clause you can put the required date calculation, kind of create an equivalent of @T"mmddyyyy" It is not going to be as easy as it is in the scheduler, but it is surely also doable. For details on WMI and WSQL see http://msdn2.microsoft.com/en-us/library/aa394606.aspx

Yes, those are good ideas although the second one was for Scheduler as well, which I wouldn't have thought would lend itself to the double watch