Difference between revisions of "Information Systems:Overnight Schedule"
| Line 35: | Line 35: | ||
[[Overnight ENDOFMONTH|ENDOFMONTH]] runs on the first of the month. The program called is EOM from library UNIPHARMIT. |
[[Overnight ENDOFMONTH|ENDOFMONTH]] runs on the first of the month. The program called is EOM from library UNIPHARMIT. |
||
| − | [[Overnight EODSAVE|EODSAVE]] runs after the daily or weekly processing, and calls EODBU from library UNIPHARMIT, which calls [[BRMS]] to do a backup. |
+ | [[Overnight EODSAVE|EODSAVE]] runs after the daily or weekly processing, and calls EODBU from library UNIPHARMIT, which calls [[BRMS]] to do a backup. The secondary function of this is to cancel the previous job if something goes wrong. EODSAVE goes into the system restricted state (which will cancel all running jobs), with a time limit of two and a half hours. |
[[Overnight EODEMAIL|EODEMAIL]] runs every morning to email users the tape used for backup. The program called is EODEMAIL from library UNIPHARMIT. |
[[Overnight EODEMAIL|EODEMAIL]] runs every morning to email users the tape used for backup. The program called is EODEMAIL from library UNIPHARMIT. |
||
Other [[Overnight Emails|emails]] are sent all through the overnight processes. If they are NOT received at the expected times, there MAY be a problem. |
Other [[Overnight Emails|emails]] are sent all through the overnight processes. If they are NOT received at the expected times, there MAY be a problem. |
||
| − | |||
| ⚫ | |||
| − | |||
| − | '''This is where you could change the times that these jobs run.''' But do this with care, as they are dependent upon each other. |
||
==Timing Interdependencies== |
==Timing Interdependencies== |
||
| Line 49: | Line 45: | ||
ENDOFDAY and ENDOFWEEK should run at the same time, and must be run after midnight. If not, the temporary backup won't work the first time (because the tape won't be expired), and, as everything is posted to 'yesterday', all the dates in ASW will be wrong. |
ENDOFDAY and ENDOFWEEK should run at the same time, and must be run after midnight. If not, the temporary backup won't work the first time (because the tape won't be expired), and, as everything is posted to 'yesterday', all the dates in ASW will be wrong. |
||
| − | EODSAVE must |
+ | EODSAVE must run at least two hours after the end of day and of week. Of course, if the length of time they take to run approaches two hours, this will have to be adjusted. |
| − | ENDOFWEEK must |
+ | ENDOFWEEK must run at least two and a half hours after EODSAVE. If the system is still in the restricted state at it's scheduled time, it will not run. It will then have to called manually. |
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| + | The length of time these jobs take to run must be monitored to make sure there is enough time, plus some leeway, before the next job is started. |
||
| ⚫ | |||
| ⚫ | |||
Revision as of 15:15, 5 January 2016
Current Schedule
The overnight processing - which include end of day, week, month, and year - is run from the job schedule. To see these jobs, key in WRKJOBSCDE and press enter. Page down until you get to 'END'. Note that ENDOFMONTH will automatically run the end of year (both fiscal and calendar) automatically.
Work with Job Schedule Entries BART
10/27/15 12:48:35
Type options, press Enter.
2=Change 3=Hold 4=Remove 5=Display details 6=Release
8=Work with last submission 10=Submit immediately
Next
-----Schedule------ Recovery Submit
Opt Job Status Date Time Frequency Action Date
__ ENDOFDAY SCD USER DEF 01:00:00 *WEEKLY *NOSBM 10/28/15
__ ENDOFMONTH SCD *MONTHSTR 05:30:00 *MONTHLY *NOSBM 11/01/15
__ ENDOFWEEK SCD *SUN 01:00:00 *WEEKLY *NOSBM 11/01/15
__ EODEMAIL SCD *ALL 08:00:00 *WEEKLY *NOSBM 10/28/15
__ EODSAVE SCD *ALL 03:00:00 *WEEKLY *NOSBM 10/28/15
Parameters or command
===> _______________________________________________
F3=Exit F4=Prompt F5=Refresh F6=Add F9=Retrieve
F11=Display job queue data F12=Cancel F17=Top F18=Bottom
Programs Called
ENDOFDAY runs Monday through Saturday. The program called is EODDAILY from library UNIPHARMIT.
ENDOFWEEK runs Sunday. The program called is EODWEEKLY from library UNIPHARMIT.
Both of these must run after midnight, as they use yesterday's date instead of today's. Also because the temporary backup tape has a retention period of one day.
ENDOFMONTH runs on the first of the month. The program called is EOM from library UNIPHARMIT.
EODSAVE runs after the daily or weekly processing, and calls EODBU from library UNIPHARMIT, which calls BRMS to do a backup. The secondary function of this is to cancel the previous job if something goes wrong. EODSAVE goes into the system restricted state (which will cancel all running jobs), with a time limit of two and a half hours.
EODEMAIL runs every morning to email users the tape used for backup. The program called is EODEMAIL from library UNIPHARMIT.
Other emails are sent all through the overnight processes. If they are NOT received at the expected times, there MAY be a problem.
Timing Interdependencies
ENDOFDAY and ENDOFWEEK should run at the same time, and must be run after midnight. If not, the temporary backup won't work the first time (because the tape won't be expired), and, as everything is posted to 'yesterday', all the dates in ASW will be wrong.
EODSAVE must run at least two hours after the end of day and of week. Of course, if the length of time they take to run approaches two hours, this will have to be adjusted.
ENDOFWEEK must run at least two and a half hours after EODSAVE. If the system is still in the restricted state at it's scheduled time, it will not run. It will then have to called manually.
EODEMAIL must be run when the Catapult server is active.
Change Scheduled Start Time
The length of time these jobs take to run must be monitored to make sure there is enough time, plus some leeway, before the next job is started.