On Wed, 26 Apr 2006 02:25:37 -0500, Brian Westerman <[EMAIL PROTECTED]> wrote:
>> >Any suggestions? > >Brian > Well Brian....since you asked.... I was looking at the current version of this facility to replace a not- terribly-robust homegrown process. The one thing I found to be "missing" was the ability to wait for a message before continuing. For instance, when starting some products, the presence of the task (i.e. IFSTARTED) is not enough to determine whether it is operational (a la "Control is being given to CICS") And, along with that, the ability to either continue or terminate after some specified period of time waiting for that message would be necessary. The things I'm trying to automate here (we don't have any "real" automation product -- just some rudimentary function in our scheduling product and the homegrown program I mentioned above), are with an eye toward eliminating the need for operators on certain shifts, so putting the anomaly-catching responsibility on them isn't going to get the job done. Thanks for a great tool and for considering this suggestion. Debbie Mitchell Utica National Insurance Group ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
