I agree that using the Report Scheduler is important whenever driving scripts from Meditech data. I also kill Meditech at the end of every script and start fresh with each new script even if it might use the same module. I've also recently switched over to scheduling scripts based upon code I found here. http://www.bostonworkstation.com/customer_center/script_center/script_details.aspx?id=150&cat=3 It basically looks for a shared variable to determine whether it is ok to start a new script. You'll want the script to be robust enough not to hang or at least add timeouts when you do so that it doesn't hold things up. I do have a way around a script holding others scripts up though. I use virtual servers also to run my scripts and because it's a standard image I can move scripts from box to box without a problem. So for example I'll have the Report Scheduler generate a report on a daily basis (or another script if it's another application). The script that uses that report to drive its functionality will check for the existence of that file. But since it will quit if it doesn't find a file I can schedule the script on multiple boxes as long as the script renames the file when it finds it so other script doesn't try to pick it up. Chad Kemp Information Systems Analyst Firelands Regional Medical Center 419-557-7874
________________________________ From: [email protected] [mailto:[email protected]] Sent: Wednesday, March 31, 2010 9:42 AM To: [email protected] Subject: RE: [talkbws] Running multiple scripts with Meditech 6.0 Meditech 5.6/6.0 is a scripting nightmare (*cough, an abomination of programming*). Between the inconsistent cursor positions and instability of the application, scripting is a p.i.t.a. What we have done: * Put everything you can possibly put into Meditech's Report Scheduler * For stuff that is left over, user lots, and I mean LOTS of stables, condition loops, etc to force some stability into the application * Make sure you have a good recovery routine (we kill meditech and start from the beginning since it's the only sure way) * Time your scripts and space them out so you leave them plenty of room to finish before the next one starts. Good Luck. You'll need it. Pre Meditech 5.6 (CS): 2400 scheduled scripts Post Meditech 5.6 (CS): 140 scheduled scripts Thank you, Mitch Lawrence Lead Applications Analyst Enterprise Data Standards - NPR/Automation CHRISTUS Information Management *: [email protected] <mailto:[email protected]> ________________________________ From: [email protected] [mailto:[email protected]] Sent: Wednesday, March 31, 2010 8:31 AM To: [email protected] Subject: RE: [talkbws] Running multiple scripts with Meditech 6.0 Greetings, Meditech Client Server 5.6 / 6.0 is a Windows application even though we have a specific connection to it that makes it "look" like Magic to a script. Well it's sort of a Windows application but that's a story for a different day... Meditech NUI became sort of like a windows app - but most of the time, not much like a windows application, so there are ways to prevent the behavior you described. But... It is not possible to script simultaneously into Windows applications. This has nothing to do with a lack of functionality on our part. It is the way of the world. Anyone that says otherwise is leaving out important details. Let me put a disclaimer here. Yes we can do stuff to a Windows application when it's not in the foreground - a lot of stuff. But being able to do lot does not equal being able to do everything you'll need. I hate the cliché, but the devil is in the details. That's why you'll never hear us say you can script windows applications and this includes Meditech Client Server 6.0 simultaneously. 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, March 31, 2010 9:01 AM To: Talk Subject: [talkbws] Running multiple scripts with Meditech 6.0 Greetings, We currently have over 50 BWS scripts located on 2 Virtual servers. We have many occurrences where more than one script runs at the same. This is not an issue because we script into the 3.x workstation. When we tried to use the 4.x workstation we ran into too many issues where the scripts would lose focus of its particular window and the script would halt. So to avoid the "focus" issue we stayed with 3.x. Next year we are upgrading to Meditech 6.0. I foresee a scripting nightmare ahead of me. Does anyone currently script simultaneously into 6.0 without focus issue? If so, what technique do you use? Thank You, Michael Burgett Programmer Analyst Information Technology Tel: (740)-779-7812 Email: [email protected] <mailto:[email protected]> ****************************************************************** This email and any files transmitted with it are proprietary and confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager at [email protected]. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. No employee or agent is authorized to conclude any binding agreement on behalf of Adena Health System with another party by email without express written confirmation from Adena Health System authorized individuals. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. Adena Health System, 272 Hospital Road, Chillicothe, Ohio, USA, http://www.adena.org ****************************************************************** --- 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 --- 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
<<image002.jpg>>
