Lori,
A simple approach:  Setup your script to call a "heartbeat" procedure as it's 
very-last step.  Something like:

Sub heartBeat()

hbeat = FreeFile

path = "\\yourpathgoeshere\"

FileName = path & "fileMonitor.txt"

Open FileName For Output As #hbeat

tstr = Date & " - " & Time

Print #hbeat, tstr

Close #hbeat

End Sub



All you are doing is writing a date and time-stamp to a file.

Then have a second script check the creation-time of the heart-beat file...   
or the time-stamp contents of the file.

If the 1st script did not run properly the second script can send an alert 
(email, text-page, etc).



Option B:  For mission-critical applications (ie: interfaces) A little more 
involved.

Have your scripts setup in a master / slave arrangement where the master 
attempts to process the files but if there is a problem the slave takes-over 
the processing (becomes the master), completes the process and sends an alert 
that the other server needs checked.



The support-folks at Boston can guide-you on using either approach.  Or give me 
a call if you have questions.   ;)


Roger D. Jordan
Siemens Medical Solutions - Health Services
Charleston Area Medical Center
[email protected]<mailto:[email protected]>
304-388-7358

From: [email protected] [mailto:[email protected]]
Sent: Monday, October 11, 2010 11:23 AM
To: [email protected]
Subject: [talkbws] Ideas for Boston Schedule Monitoring

I've run scheduled scripts for years for print jobs into ChartMaxx EMR.  But 
just recently added a Meditech Day Close routine to pick up other vendor charge 
batch.  (Meditech evidently cannot imagine how to pick up an OV file.)  Now 
Boston Scripting is even more important.

I have a test station and a live station that run schedules.  Just wondering if 
anyone had any ideas on using the test station to monitor that the live was up 
and working okay.

My current method is every night at 7pm, I get an email to my phone which 
indicates it is "alive" and working.  I've had network hangs, lost connections, 
etc... periodically that could hang the day close job.

Just wondering if anyone had a script used by a second machine to be proactive 
and check on the first machine?

Thanks.





Lori S Kent, Database Analyst
Catawba Valley Medical Center
810 Fairgrove Church Road SE
Hickory, NC 28602

phone:  828.326.2024
  email: [email protected]<mailto:[email protected]>

Catawba Valley Medical Center 810 Fairgrove Church Rd Hickory NC 28602 
828-326-3000 "This electronic message may contain information that is 
confidential and/or legally privileged. It is intended only for the use of the 
individual(s) and/or entity named as recipients in the message. Please notify 
the sender immediately and delete the material from your computer if you have 
received this message in error. Do not deliver, distribute, or copy this 
message, and do not disclose its contents or take any action as a result of the 
information it contains. Thank you."


---  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


Confidentiality Note: The information contained in this message 
may be privileged and confidential. If this e-mail contains 
protected health information, you are hereby notified that any 
dissemination, distribution or copying of this communication is 
strictly prohibited,except as permitted by law. If you have 
received this communication in error, please notify the sender 
immediately by replying to this message and deleting it from 
your computer. Thank you.
---  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   

Reply via email to