Yes, you are correct. Please keep in mind there exist other ways to deal with such issues. For example you may want to run a job that send email message and it hangs or simply takes a long time to run you want to kill it. A solution to this would be to run an external program to send the email (Exchange Admin Kit for example includes sendmail.exe utility, there are also many other similar utilities available on the Internet). RunAndWait command can run such program with a timeout and kill it after the specified time if the program does is still running. If you don not want to use an external program you can create a "helper" job in 24x7 which you would run as RunAndWait "24x7.exe /JOB \"helper job id\"", "", timeout, pid BTW: I would be very surprised if the problem is with the SMTP server. I guess email functions should fail rather than hang if SMTP server does not work properly. What's more likely is a network problem causing the network communication to break while resolving host name or during data transmission. : No problem with the typos here :) : So, if I understand it correctly the notification portions of an : "Async" job are not run async, therefore the job may cause a : queue blockage if it hangs during that portion of the job. Since I don't : control our SMTP server (or our network), this is something I must : consider as being likely to happen. : So if I want a "pure" Async job, with no possibility of queue : blockage, I need to get more sophisicated. I can do it by setting up a : Parent/Child relationship between the "worker" job and a new : "notification" job. I would setup the notification events to : "create a semaphore file" in the parent job, and then setup the : child job to monitor for the existence of the semaphore file. The child : job then interogates the event and job name to determine what notification : action is appropriate. : If I am correct (which would be a first), then I will know what to do as soon : as you/me figure out the problems with @V"event" and : @V"job_name" not working for me. : Thanks for helping here, : Mike
|