Difference between revisions of "UC4"
>Jeremyb |
>Jeremyb |
||
| Line 3: | Line 3: | ||
'''Daily Jobs''' | '''Daily Jobs''' | ||
| − | + | *HISTORY | |
| + | |||
<code> | <code> | ||
##Run nightly- between 12:01 and 1 am. | ##Run nightly- between 12:01 and 1 am. | ||
| Line 11: | Line 12: | ||
/VSJOBS/JVSLOAD_HIST | /VSJOBS/JVSLOAD_HIST | ||
</code> | </code> | ||
| + | |||
| − | + | *MEMBERSHIP ANALYSIS | |
| + | |||
<code> | <code> | ||
##Run nightly – after JVSLOAD_HIST and prior to 5am | ##Run nightly – after JVSLOAD_HIST and prior to 5am | ||
| Line 22: | Line 25: | ||
</code> | </code> | ||
| + | |||
'''Month End Jobs''' | '''Month End Jobs''' | ||
| − | + | *MEMBERSHIP ANALYSIS | |
| + | |||
<code> | <code> | ||
##Run after report databases have been created | ##Run after report databases have been created | ||
Revision as of 19:47, 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
