I went a different route.  Each script checks a global variable.  If the
value is false, no other scripts are currently running on the machine
and the script can continue.  If the value is true, another script is
currently running and the script will check again every 2 minutes for an
hour before writing out a message to a common log.

 

It works to keep scripts from running on top of each other.  The
downside with this approach is if one fails overnight, all the scripts
on that machine will fail.  

 

 

John Taylor
Revenue Cycle Analyst, Information Systems | Augusta Health
Office:  (540) 332-4882 | www.augustahealth.com
<http://www.augustahealth.com/> 
 

 

From: [email protected] [mailto:[email protected]] 
Sent: Wednesday, January 05, 2011 2:07 PM
To: [email protected]
Subject: RE: [talkbws] Killing a script that has frozen with MediTech
Magic

 

I have a VBScript that I call EndMT.vbs. It runs, by using a Shell_
statement, at the beginning of each scheduled Boston Workstation script
that opens Meditech Magic. It loops through Task Manager processes and
terminates occurrences of T.exe. I don't know what Meditech would think
of this rather drastic method of terminating a client session, but it is
invaluable to me for those rare times when all other safeguards have
failed and a Meditech session remains open.

 

John Helfrick

VHS Information Services

508-363-9015

 

From: [email protected] [mailto:[email protected]] 
Sent: Wednesday, January 05, 2011 11:02 AM
To: [email protected]
Subject: RE: [talkbws] Killing a script that has frozen with MediTech
Magic

 

Does your run time computer have a locked screen saver?  That will stop
a download cold 100% of the time.

 

Shirley Hammack

I.T.  Financial Analyst

Duncan Regional Hospital

580-251-8939

 

From: [email protected] [mailto:[email protected]] 
Sent: Wednesday, January 05, 2011 10:00 AM
To: [email protected]
Subject: RE: [talkbws] Killing a script that has frozen with MediTech
Magic

 

Greetings,

I'd implement some logging first to see what's going on first - should
be able to capture what's going on and that should direct you to how to
solve it.  

 

This is a shameless plug for today's webinar which covers this very
subject J

http://www.bostonworkstation.com/customer_center/special_events.aspx

 

Regards,

Thom

 

Thom C. Blackwell

Product Manager

Boston Software Systems

(866) 653-5105 ex 807

www.bossoft.com <http://www.bossoft.com/> 

 

Sign up for my weekly webinar!
<http://www.bostonworkstation.com/customer_center/special_events.aspx> 

 

LEGAL NOTICE Unless expressly stated otherwise, this message is
confidential and may be privileged. It is intended for the addressee(s)
only. Access to this E-mail by anyone else is unauthorized. If you are
not an addressee, any disclosure or copying of the contents of this
E-mail or any action taken (or not taken) in reliance on it is
unauthorized and may be unlawful. If you are not an addressee, please
inform the sender immediately, then delete this message and empty from
your trash.

 

From: [email protected] [mailto:[email protected]] 
Sent: Wednesday, January 05, 2011 10:48 AM
To: Talk
Subject: [talkbws] Killing a script that has frozen with MediTech Magic

 

Can anyone share a routine that will kill boston runtime and the
meditech instance?

 

I have a boston script that runs every 15 minutes which downloads 3
reports from MediTech.  It works great 95% of the time.  The other 5%,
the meditech download freezes, or the boston script doesn't exit
properly.  Since this is on a runtime workstation, I don't see a way to
"debug" it.

 

I am thinking about adding another scheduled task that runs 1 minute
prior to the boston script to make sure boston and meditech are closed.
Does anyone have a bat file or a set of commands they are willing to
share to accomplish this?

 

Dan Neuman

Application Developer

HCA-Far West Division IT&S

 

---  To post a message to this list, send mail to: [email protected]
You are currently subscribed as: [email protected]
Unsubscribe in the customer center on our website:
http://www.bostonworkstation.com/customer_center/virtual_user_group_talk
.aspx   

 

---  To post a message to this list, send mail to: [email protected]
You are currently subscribed as: [email protected]
Unsubscribe in the customer center on our website:
http://www.bostonworkstation.com/customer_center/virtual_user_group_talk
.aspx   

 


Please consider the environment before printing this e-mail.

"CONFIDENTIALITY NOTICE: This e-mail and any files transmitted 
with it are the property of DRH and/or its affiliates, 
are confidential, and are intended solely for the use of the 
individual or entity to whom this e-mail is addressed. 
If you are not one of the named recipient(s) or otherwise have 
reason to believe that you have received this message in error, 
please notify 580.251.8773 and delete this message immediately 
from your computer. Any other use, retention, dissemination, 
forwarding, printing, or copying of this e-mail is strictly prohibited."

 

---  To post a message to this list, send mail to: [email protected]
You are currently subscribed as: [email protected]
Unsubscribe in the customer center on our website:
http://www.bostonworkstation.com/customer_center/virtual_user_group_talk
.aspx   

 

---  To post a message to this list, send mail to: [email protected]
You are currently subscribed as: [email protected]
Unsubscribe in the customer center on our website:
http://www.bostonworkstation.com/customer_center/virtual_user_group_talk
.aspx   

---  To post a message to this list, send mail to: [email protected]    You are 
currently subscribed as: [email protected]    Unsubscribe in the 
customer center on our website: 
http://www.bostonworkstation.com/customer_center/virtual_user_group_talk.aspx   

<<image001.gif>>

Reply via email to