Hi All,
I had a problem in the past with scripts that seemed fine durring single and manual run, but found that they died in the middle of the night.
I ended up upgrading the box that they ran on to a more powerful machine. The reports did run a bit slower due to MT background jobs running in the night, and the more powerful box helped.
Bruce Krigman
Information Systems
South Shore Hospital
781-340-8299
"Rich McNeil" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED] 12/29/2005 12:29 PM
|
|
Shirley,
Looking at the code for the Meditech Connection, there shouldn't be any way
that Key "@_LASTSCREEN" could get to the keyboard, so I'm also puzzled about
what you saw.
I also try to avoid having to get up in the middle of the night to check on
a script. There shouldn't be any theoretical reason why a script running
from the Scheduler would act any different from one directly started, but
sometimes, in the middle of the night, the operating environment is
different...due to running reports, for example. As an extra precaution,
I'd suggest slowing this part of the script down with added Wait's.
Rich McNeil
Boston Software Systems
866 653 5105 x813 -or- 508 318 5327
www.bostonworkstation.com
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Shirley Hammack
Sent: Tuesday, December 27, 2005 12:40 PM
To: Boston Work Station (E-mail)
Subject: [Talk] key "@_LASTSCREEN"
I am working in Meditech Magic with Workstation 3.x. I have a script that
closes my LSS databases. In the screen where I am looking for the transfer
of the data from the clinics (which use PRV) to complete, there is a pop up
that says "Again?". This causes the screen I want to look at to not be the
current screen. I have used the command Key "@_LASTSCREEN" to check for the
word COMPLETE in the status field.
This works absolutely perfectly when I start the script manually. However
the script has to run between midnight and 7am and I'm tired of getting up
in the middle of the night to run it manually. So last night I scheduled it
for just a one-time run at 3am. At about 5am I dialed in to check on it.
It was stuck in the loop looking for "COMPLETE" and there was an "@" typed
in after the word "Again?"
I went into debug mode and stepped through the loop a few time. I backed
out the "@" sign but the script kept putting it back in. I then patched the
script and restarted it manually. It ran perfectly.
What is going on here?????
Shirley Hammack
I.T. Financial Analyst
Jackson County Memorial Hospital
580-482-4781 ext 2554
The documents accompanying this transmission contain confidential
information, belonging to the sender, that is legally privileged. This
information is intended only for the use of the individual or entity named
above. The authorized recipient of this information is prohibited from
disclosing this information after its stated need has been fulfilled.
If you are not the intended recipient, you are hereby notified that any
reading, disclosure, copying, distribution, or action taken in reliance on
the contents of these documents is strictly prohibited. Violators may be
prosecuted. If you have received this email in error, please notify the
sender immediately and destroy the transmitted information.

