Difference between revisions of "Information Systems:Overnight Process Timing"
(Created page with "==Daily - Monday to Saturday== The first email message sent, informing IT that the process has started, also gives the expected times for the subsequent messages. If they ar...") |
m |
||
| (One intermediate revision by the same user not shown) | |||
| Line 3: | Line 3: | ||
The first email message sent, informing IT that the process has started, also gives the expected times for the subsequent messages. If they aren't received when expected, it's time to investigate. If the time jobs are started, or the length of time they take to run changes, this message should be changed to match. They are in CLLE programs EODDAILY and EODWEEKLY in library UNIPHARMIT. |
The first email message sent, informing IT that the process has started, also gives the expected times for the subsequent messages. If they aren't received when expected, it's time to investigate. If the time jobs are started, or the length of time they take to run changes, this message should be changed to match. They are in CLLE programs EODDAILY and EODWEEKLY in library UNIPHARMIT. |
||
| − | Program EODDAILY is started by the job scheduler at 1:00AM, and as of December 2015 takes about an hour and 15 minutes to run; completing at around 2:15AM. Program EODBU is started at 3:00AM. It calls BRMS, which goes into a restricted state to do a full backup. If EODDAILY is still running, it will be cancelled. Keep an eye on the ending time - if it starts getting close to 3:00AM, the timing will have to be adjusted. |
+ | Program EODDAILY is started by the job scheduler at 1:00AM, and as of December 2015 takes about an hour and 15 minutes to run; completing at around 2:15AM. Program EODBU is started at 3:00AM. It calls BRMS, which goes into a [[Information Systems:IBM i restricted state | restricted state]] to do a full backup. If EODDAILY is still running, it will be cancelled. Keep an eye on the ending time - if it starts getting close to 3:00AM, the timing will have to be adjusted. |
EODBU sets the timer for the restricted state to two and a half hours. The backup is currently a little under two hours. If this approaches two and a half hours, the timing will have to be adjusted. |
EODBU sets the timer for the restricted state to two and a half hours. The backup is currently a little under two hours. If this approaches two and a half hours, the timing will have to be adjusted. |
||
Latest revision as of 14:41, 8 December 2016
Daily - Monday to Saturday
The first email message sent, informing IT that the process has started, also gives the expected times for the subsequent messages. If they aren't received when expected, it's time to investigate. If the time jobs are started, or the length of time they take to run changes, this message should be changed to match. They are in CLLE programs EODDAILY and EODWEEKLY in library UNIPHARMIT.
Program EODDAILY is started by the job scheduler at 1:00AM, and as of December 2015 takes about an hour and 15 minutes to run; completing at around 2:15AM. Program EODBU is started at 3:00AM. It calls BRMS, which goes into a restricted state to do a full backup. If EODDAILY is still running, it will be cancelled. Keep an eye on the ending time - if it starts getting close to 3:00AM, the timing will have to be adjusted.
EODBU sets the timer for the restricted state to two and a half hours. The backup is currently a little under two hours. If this approaches two and a half hours, the timing will have to be adjusted.
However, there is not much leeway to push back the times - the first transmission to Atlas (Monday to Friday) is at 6:15. If something were to go wrong with the backup, and the restricted state had to be ended by the timer, the system wouldn't be up until 5:47AM. (That is 11 minutes to enter the restricted state, 150 minute timer, and 6 minutes to start up everything.) That currently gives us a cushion of under half an hour.