Difference between revisions of "UC4"
>Jeremyb |
>Jeremyb |
||
(12 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
− | Vital Signs relies on nightly run UC4 jobs to extract the Core data which is warehoused and provided to the applications | + | Vital Signs relies on nightly run UC4 jobs to extract the Core data which is warehoused and provided to the applications |
− | + | These jobs fall into two categories, Daily and EOM. The Daily is made up of 2 jobs, History and Membership Analysis. The EOM is made up of Membership Analysis. | |
− | |||
− | < | + | == Job Schedules == |
− | ##Run nightly- between 12:01 and 1 am | + | |
− | ##Login as bolive | + | '''Daily''' |
− | set -e | + | History |
− | cd /var/summit/spectrum/LIVE | + | *Run between 12:01 and 1am every day. |
− | /VSJOBS/JVSLOAD_HIST | + | |
− | + | Membership Analysis | |
+ | *Run prior to 5am | ||
+ | |||
+ | |||
+ | '''EOM''' | ||
+ | *Membership Analysis | ||
+ | **Run after report databases have been created | ||
+ | |||
+ | |||
+ | == Daily Job Examples == | ||
+ | |||
+ | <pre> | ||
+ | ## HIST DAILY | ||
+ | ## Run nightly- between 12:01 and 1 am, including weekends | ||
+ | ## Should be run prior to the MEMBERSHIP_ANALYSIS DAILY | ||
+ | ## Login as bolive | ||
+ | set -e | ||
+ | cd /var/summit/spectrum/LIVE | ||
+ | /VSJOBS/JVSLOAD_HIST | ||
− | + | ## MEMBERSHIP_ANALYSIS DAILY | |
+ | ## 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 | ||
+ | </pre> | ||
− | + | ''Note: There is no need to have your job plans pause and wait for completion of these jobs before | |
− | + | continuing with the next step'' | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | == EOM Job Example == | |
− | < | + | <pre> |
− | ##Run after report databases have been created | + | ## MEMBERSHIP_ANALYSIS EOM |
− | ##Login as bolive | + | ## Run after report databases have been created |
+ | ## Login as bolive | ||
set -e | set -e | ||
cd /var/summit/spectrum/LIVE | cd /var/summit/spectrum/LIVE | ||
/VSJOBS/JVSLOAD_MBRSHLN eom &YYYYMMDD | /VSJOBS/JVSLOAD_MBRSHLN eom &YYYYMMDD | ||
− | #Where &YYYYMMDD is a UC4 variable containing the last day of the month | + | #Where &YYYYMMDD is a UC4 variable containing the last day of the month |
− | </ | + | </pre> |
''Note: There is no need to have your job plans pause and wait for completion of these jobs before | ''Note: There is no need to have your job plans pause and wait for completion of these jobs before | ||
continuing with the next step'' | continuing with the next step'' |
Latest revision as of 22:42, 31 October 2012
Vital Signs relies on nightly run UC4 jobs to extract the Core data which is warehoused and provided to the applications
These jobs fall into two categories, Daily and EOM. The Daily is made up of 2 jobs, History and Membership Analysis. The EOM is made up of Membership Analysis.
Job Schedules
Daily History
- Run between 12:01 and 1am every day.
Membership Analysis
- Run prior to 5am
EOM
- Membership Analysis
- Run after report databases have been created
Daily Job Examples
## HIST DAILY ## Run nightly- between 12:01 and 1 am, including weekends ## Should be run prior to the MEMBERSHIP_ANALYSIS DAILY ## Login as bolive set -e cd /var/summit/spectrum/LIVE /VSJOBS/JVSLOAD_HIST ## MEMBERSHIP_ANALYSIS DAILY ## 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
Note: There is no need to have your job plans pause and wait for completion of these jobs before continuing with the next step
EOM Job Example
## MEMBERSHIP_ANALYSIS EOM ## 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
Note: There is no need to have your job plans pause and wait for completion of these jobs before continuing with the next step