Just another thought... I had a similar situation where I had three scripts that needed to access the same file for use in three separate processes. What I ended up doing so that the file could be shared and have no issues was have each script start one minute apart. In the very first step, the script opens the file in datastation, stores all information necessary into Flags, then closes the file. That way, all scripts can share the file information without having the file open at all times. These three scripts run great and I have a fourth (almost like your bat file) that actually renames the shared file when necessary.
Hope that helps. Kim Scaccia, System Admin Recovery Reimbursement Patient Business & Financial Services Halifax Medical Center 386-226-4590 opt 1 ext 2018 ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thom C. Blackwell Sent: Thursday, October 11, 2007 7:04 PM To: [email protected] Subject: RE: [Talk] Scheduler / File Open Greetings, Ah!!! You're spot on, just call the bat file from within the script prior to (or before) the script opens the file (whichever is more appropriate). You can use: Shell_ Fullpath.bat To execute the bat file. Regards, Thom Thom C. Blackwell Product Manager Boston Software Systems (866) 653-5105 ex 807 www.bossoft.com 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] On Behalf Of Scott Ahlbrandt Sent: Thursday, October 11, 2007 7:01 PM To: [email protected] Subject: RE: [Talk] Scheduler / File Open It's just a .bat file that renames the file daily - are you saying that if the .bat file process was included in the with script this wouldn't be a issue ? ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thom C. Blackwell Sent: Thursday, October 11, 2007 3:57 PM To: [email protected] Subject: RE: [Talk] Scheduler / File Open Greetings, Hum... this seems tricky because it sounds like the script would need to "know" somehow about the external process needing the file and then execute d.Close to release the file. So my questions would be: Is there a way to predict when the other process would need the file? Is there a way perhaps for the script to "know" that this is about to occur? Maybe this could be as simple as altering the scheduler timing? What's the situation here? Regards, Thom Thom C. Blackwell Product Manager Boston Software Systems (866) 653-5105 ex 807 www.bossoft.com 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] On Behalf Of Scott Ahlbrandt Sent: Thursday, October 11, 2007 6:37 PM To: [email protected] Subject: [Talk] Scheduler / File Open Thomas, what's the best way to have BWS let go of a file, say for example a script runs by the scheduler - and another process wants to rename that file but can't because BWS still has the file open - what's the best way to manage that situation from your experience..? Scott Ahlbrandt MCSA Patient Accounting Systems Analyst John C. Lincoln Health Network 250 East Dunlap Phoenix, Arizona 85020 602-870-6060 x1286 http://www.jcl.com -------------------- If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately forward the original message back to the sender and delete your copy of the email. -------------------- If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately forward the original message back to the sender and delete your copy of the email.
<<image001.gif>>
