But that would run the next Project, no matter what time it was
scheduled?  Some of the jobs I am running, will only run once a day,
while others are every 30 min, and still others are every 45
min....Makes for a weird mix.....I also have to factor in how long the
Project takes to run, (i.e. execution time).  That is where my dilemma
begins.  As jobs are "spawned" to run, their run times are all
different, so they always seem to stack on each other, after a certain
duration of time.   I would like to have a "wish list" to have a
scheduler added to Boston Workstation, that would queue jobs to run, but
would only run them one at a time, in a FIFO setup.    That would be a
utility that quite a few users, from the sounds of it, would use.  

 

Ron

 

From: Bennett, Brian [mailto:[EMAIL PROTECTED] 
Sent: Friday, April 04, 2008 1:50 PM
To: '[email protected]'
Subject: RE: [Talk] Task Schedulers for Boston Scripts

 

Have you tried, or thought about using the RunProject command at the end
of each project?  You would then only need MS scheduler to use killtask
to shutdown BWS (the last project) and then launch the first project of
the day.

 

Brian Bennett 
Affinity Health Systems 
Systems Analyst 
PBS\Clinic Billing 
(920)628-9055 
[EMAIL PROTECTED] 

 

 

________________________________

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brian Stevenson
Sent: Friday, April 04, 2008 12:58 PM
To: [email protected]
Subject: RE: [Talk] Task Schedulers for Boston Scripts

I can't really help you set it up but have been told a few times that
the several different scripts I am working on can basically be setup in
the Scheduler to run consecutively and will not over step each other as
I only have one license...  sorry if I mislead you...

 

Brian Stevenson | Systems Administrator

University Health System <http://www.universityhealthsystem.com/>  |
Business Information Services

355-2 Spencer Lane | San Antonio, TX 78229

Office | (210) 358 - 9282

Pager | (210) 756 - 0582

 

         

        
________________________________


        From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
        Sent: Friday, April 04, 2008 12:53 PM
        To: [email protected]
        Subject: RE: [Talk] Task Schedulers for Boston Scripts

        Brian~

            What I was told, and I may be wrong, but the job you want to
run, has to be up, and minimized, before Boston's scheduler can do
anything with it.  Is that correct information?  I need the scheduler to
load the job and run it, then close it when finished.  If this can be
done within Boston, can you show me how to set it up?

         

        Ron

         

        From: Brian Stevenson [mailto:[EMAIL PROTECTED] 
        Sent: Friday, April 04, 2008 12:44 PM
        To: [email protected]
        Subject: RE: [Talk] Task Schedulers for Boston Scripts

         

        to my knowledge the scheduler does this...

         

        Brian Stevenson | Systems Administrator

        University Health System
<http://www.universityhealthsystem.com/>  | Business Information
Services

        355-2 Spencer Lane | San Antonio, TX 78229

        Office | (210) 358 - 9282

        Pager | (210) 756 - 0582

         

                 

                
________________________________


                From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
                Sent: Friday, April 04, 2008 12:42 PM
                To: [email protected]
                Subject: [Talk] Task Schedulers for Boston Scripts

                What is the best task scheduler to use for Boston
Workstation scripts?  I have 5 scripts that run multiple times during
the day {disaster recovery, file downloads, hard copy prints, etc}, and
they all seem to run at different durations and times, so the
possibility of one running on top of another exists.  I have used the
task scheduler within Windows 2003 server, and it is pretty limited.  I
am looking for an alternative that will allow jobs to specifically run
at the desired times, and if another job comes up to run at the same
time, the scheduler will queue the new job to run after the current is
finished.  My current setup (the windows task scheduler), doesn't care
if another job comes up.  It runs them both simultaneous.  Then, both
jobs seem to lose focus and stall out, or they get a run-time errors.  I
looked at the scheduler within the Boston software, but it didn't suit
my requirements.   Any suggestions??? 

                 

                Thanks, 

                 

                Ron Barrett, MICT

                Programmer/Analyst

                Coffeyville Regional Medical Center 

                (620) 252-1603 

                 

                This email and any files transmitted with it are the
property of Coffeyville Regional Medical Center, Inc. and are
confidential, intended solely for the use of the individual that or
entity to whom this email is addressed. If you are not one of the named
recipients or otherwise have reason to believe that you have received
this message in error, please notify the sender and delete this message
immediately from your computer. Any other use, retention, dissemination,
forwarding, printing, or copying of this email is strictly prohibited.

                 

                  

                 

Reply via email to