Roy,
When your script raises a Timeout error, control should be passed to a
Do...Loop that does the usual things to log off Meditech...If At("Exit")
Then Enter "y"...If At("Main [EMAIL PROTECTED],30") Then Enter "0"...If
At("H(0)") Then
Enter "???"...the kind of script you could pass control to when you've
completed your script's objectives and just want to exit. (Back when I used
to do this, my shutdown script started randomly slamming "{F11}" , "Y", "0"
and "{Enter}" keys if things went on too long.) When you finally shutdown
Meditech report it to a log and End the script.
Maybe we can talk Sara into publishing one of her old Meditech Reset
scripts.
Rich McNeil
Boston Software Systems
866 653 5105
www.bostonworkstation.com
_____
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Roy Hayward
Sent: Wednesday, June 29, 2005 1:25 PM
To: [email protected]
Subject: [Talk] Unattended script Question
Hi,
We are deploying our first meditech script as an unattended script, that is
to be run on a short 5 minute schedual. For the most part error are being
handled, but there are sometimes that the script gets lost. I have set a
timeout in the schedual, but it seems to leave the session open.
We are running BWS 7 with Meditech Magic 5.4 is there a way to close the
session when the script has lost its way so that a new session can get
started on at the correct time?
The session does eventually time itself out, but it waits and then prompts
for time out as it back out of each menu, in the mean time our script
connects and tries to find where it is and times out again. This process
making the Meditech time out take even longer.
Roy Hayward
Application Support Engineer
Global Healthcare Exchange
615-279-2752
[EMAIL PROTECTED]
<<attachment: winmail.dat>>
