"Pulling" Centralized data.mdb: Difference between revisions
Ttenbergen (talk | contribs) |
|||
Line 6: | Line 6: | ||
== Instructions / Steps to Pull == | == Instructions / Steps to Pull == | ||
* double-click on ''Centralized_CCMDB'' (folder shortcut icon) | * double-click on ''Centralized_CCMDB'' (folder shortcut icon on Pagasa's desktop) | ||
* double click on [[Pull_down_centralized_data.vbs]] | * double click on [[Pull_down_centralized_data.vbs]] | ||
* Prompts ''do you want to ...'' | * Prompts ''do you want to ...'' |
Revision as of 15:27, 2016 January 28
This article describes how the Data Processor "pulls down" (ie moves to her local c:\ drive) Centralized_data.mdb and PHI.mdb for editing. The file gets moved to local because it's faster there and because it prevents collectors from sending in the middle of update actions.
Data should not be pulled during designated sending times.
** Before going home ALWAYS make sure you are in the 'push' mode
Instructions / Steps to Pull
- double-click on Centralized_CCMDB (folder shortcut icon on Pagasa's desktop)
- double click on Pull_down_centralized_data.vbs
- Prompts do you want to ...
- Answer Yes
- Wait for the program to pull which takes approx. 5 minutes
- Prompts finished processing pull script
- click OK
- The Push/Pull log will show whether you are in 'push' or 'pull' mode.
Background
The data processor takes control of the data by "Pulling" Centralized data.mdb, and releases it back for sending or for others to access by "Pushing" Centralized data.mdb.
The current state of pushing/pulling can be seen in the Push/Pull log
At the beginning and end of the day, it should ALWAYS be in the 'push' mode.
"Back up"
When in the Pull mode, data processor can edit.
- The Centralized and Phi.mdb back up in Pull and Push state.
PTorres 15:08, 2015 June 11 (CDT)