Difference between revisions of "UC4"
>Jeremyb |
>Jeremyb |
||
| Line 5: | Line 5: | ||
| + | '''HISTORY''' | ||
| − | + | <pre> | |
| − | + | ##Run nightly- between 12:01 and 1 am. | |
| − | <pre> | + | ##Login as bolive |
| − | ##Run nightly- between 12:01 and 1 am. | + | set -e |
| − | ##Login as bolive | + | cd /var/summit/spectrum/LIVE |
| − | set -e | + | /VSJOBS/JVSLOAD_HIST |
| − | cd /var/summit/spectrum/LIVE | + | </pre> |
| − | /VSJOBS/JVSLOAD_HIST | ||
| − | </pre> | ||
Revision as of 19:52, 22 August 2012
Vital Signs relies on nightly run UC4 jobs to extract the Core data which is warehoused and provided to the applications.
Daily Jobs
HISTORY
##Run nightly- between 12:01 and 1 am.
##Login as bolive
set -e
cd /var/summit/spectrum/LIVE
/VSJOBS/JVSLOAD_HIST
MEMBERSHIP ANALYSIS
##Run nightly – after JVSLOAD_HIST and prior to 5am ##Do not run on days when the EOM job (see below) is scheduled ##Login as bolive set -e cd /var/summit/spectrum/LIVE /VSJOBS/JVSLOAD_MBRSHLN
Month End Jobs
MEMBERSHIP ANALYSIS
##Run after report databases have been created ##Login as bolive set -e cd /var/summit/spectrum/LIVE /VSJOBS/JVSLOAD_MBRSHLN eom &YYYYMMDD #Where &YYYYMMDD is a UC4 variable containing the last day of the month being closed
Note: There is no need to have your job plans pause and wait for completion of these jobs before continuing with the next step
