Eds AND raw push to x scheduled.vbs: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
← Older editNewer edit →
Bcloutier (talk | contribs)
admin
149 edits
m →What does it do?: cleaned up discussion, agree with Trish, let's keep it simple.
Line 11: Line 11:
The logging is useful for days when the [[Data Processor]] is away.  The scheduled task can be assessed without the requirement of accessing her PC.
The logging is useful for days when the [[Data Processor]] is away.  The scheduled task can be assessed without the requirement of accessing her PC.


For more details go to: [[Eds_and_raw_push_to_x_manual.vbs]]  
For more details go to: [[Eds_and_raw_push_to_x_manual.vbs]]
 
{{discussion}}
* Is that a good idea? If the files are copied when the program is currently open, will their status be defined? Ttenbergen 14:24, 2014 April 30 (CDT)
**yes it is a good idea.  Pagasa (multi tasker extraordinaire) has often forgotten to do the copy manually when she does edits to master ICU and medicine database, which is still Eds.  Others in office then end up working with files that are not up to date, and if she ends up being away for a day or two and main office is stuck and we are calling her at home.    She has the option to PUSH file manually when she finishes edits but she does forget and scheduled task is her backup, so if she does not come in for a few days we are not stuck phoning her or picking her up from home so she can come into office to log into her computer and gives us a copy updated data. --[[User:TOstryzniuk|Trish Ostryzniuk]] 19:21, 2014 April 30 (CDT)
***do you mean if Pagasa is actively open in one of the TMSX or MEDTMS dat files and she pushes manually while still open?.[[User:TOstryzniuk|Trish Ostryzniuk]] 19:44, 2014 April 30 (CDT)
 
* Rather than scheduling this, a better option might be to actually launch the program with a batch file that copies data upon closing. That is if the batch file will properly halt while the program is open. Ttenbergen 14:24, 2014 April 30 (CDT)
*don't really want to make it more complicated when in fact it will be turfed when we move away from Eds.[[User:TOstryzniuk|Trish Ostryzniuk]] 19:21, 2014 April 30 (CDT)
 
* How is this file different than [[Eds_and_raw_push_to_x_manual.vbs]]? Ttenbergen 14:24, 2014 April 30 (CDT)
**it is the same, only messages that prompt a manual pusher (Pagasa) are commented out in the scipt, otherwise scheduled task would hang waiting for someone to answers which is not needed. [[User:TOstryzniuk|Trish Ostryzniuk]] 19:21, 2014 April 30 (CDT)
***no need to fuss about this one any further I think,  it is working and doing what we need for now and it will be stopped when we do move totally to centralized and away from Ed's in a month or two.....maybe.--[[User:TOstryzniuk|Trish Ostryzniuk]] 19:21, 2014 April 30 (CDT)


==Where does it live?==
==Where does it live?==

Revision as of 16:11, 9 May 2014

Also referred to as the 2 in 1

What does it do?

Is a VBS batch file that has been also set up as a scheduled task (with message stops removed) and it copies SPECIFIC master dat files of Ed's from TMSX & MedTMS and also any exported csv files from Ed's (raw csv dat files), from data processor C drive to folder on X. This batch file can also be run manually.

This file is now set up for logging the following:

  • when it was run
  • the outcome of the script (success | failure)
  • any missing file/folder issues.

The logging is useful for days when the Data Processor is away. The scheduled task can be assessed without the requirement of accessing her PC.

For more details go to: Eds_and_raw_push_to_x_manual.vbs

Where does it live?

  • The Scheduled Task is set up on the Data Processor's desktop.
  • The VBScript is located here: X:\Eds_Master_data\Eds_AND_raw_push_to_x_schedule.vbs
  • The log file is located here: X:\Eds_Master_data\data_push.log
  • Note that X:\ is mapped to: \\Hsc1msfp0001\med_ccmed\

How often does it run?

Runs Each Weekday at 2130 hrs

Password

This task has a password (data processors network login), so that if processor logs off her computer the task will still run.

potential problems

The issue with logging off is that password changes can cause issues. If Pagasa has to change her network password, she will have to remember to update the password to same one for this task.

  • Locking the computer is the best approach. Bcloutier 17:53, 2014 April 29 (CDT)

Related Process

See:

Retrieved from "https://ccmdb.kuality.ca/index.php?title=Eds_AND_raw_push_to_x_scheduled.vbs&oldid=38609"