Difference between revisions of "Information Systems:Overnight ENDOFDAY"
| Line 10: | Line 10: | ||
* [[EODDAILY]] |
* [[EODDAILY]] |
||
| + | |||
| + | This is called by the scheduler (job name ENDOFDAY) every day except Sunday, at 1:00AM. It puts the computer into an application restricted state. If it fails, it will be cancelled by the backup; which starts at 3:00AM. |
||
| + | |||
* [[EODEND2]] |
* [[EODEND2]] |
||
| + | |||
| + | This will end all processes that can use either ASW or extension files. This does not end Domino, so that I.T. staff will receive the emails being sent. This is called by EODDAILY and EODWEEKLY. |
||
| + | |||
* [[EOD]] |
* [[EOD]] |
||
| + | |||
| + | This does the overnight processing. It is called by EODDAILY and EODWEEKLY. |
||
| + | |||
* [[EODBUTEMP]] |
* [[EODBUTEMP]] |
||
| + | |||
| + | This does a 'temporary' backup of the production data libraries, on tape '999999' which is reused every day. It can be used to restore files if something goes terribly wrong in the overnight processing, reload a file if something happens to it the next day (we have had users accidentally do mass deletes), of to rebuild the test environment (PL). |
||
| + | |||
* [[EODUPD]] |
* [[EODUPD]] |
||
* [[EODRPT]] |
* [[EODRPT]] |
||
Revision as of 10:10, 9 February 2016
The scheduler starts this job at 1:00AM; every morning except Sunday - when the End of Week is called. It calls EODDAILY, which will -
- End all programs that use ASW or extension files, and end subsystems so users cannot sign on.
- Do a 'temporary' backup of data libraries only. This uses tape '999999', which has a retention period of one day so that it can be over written every night. It can be used if something happens during the overnight processing, to quickly restore a file the next day if needed (without having to call the tape from off site storage), and to rebuild the test environment.
- Run updates, reports, and housekeeping (clear work files and out queues, and delete unnecessary spool files).
The following sections only show the main functions in the programs; not any error checking. Whenever there can be an error that shouldn't affect processing, the programs have the MONMSG (monitor message) command to ignore it. When a file that is to be rebuilt can't be cleared (because it is in use by another job), the program will automatically skip the rebuild.
This is called by the scheduler (job name ENDOFDAY) every day except Sunday, at 1:00AM. It puts the computer into an application restricted state. If it fails, it will be cancelled by the backup; which starts at 3:00AM.
This will end all processes that can use either ASW or extension files. This does not end Domino, so that I.T. staff will receive the emails being sent. This is called by EODDAILY and EODWEEKLY.
This does the overnight processing. It is called by EODDAILY and EODWEEKLY.
This does a 'temporary' backup of the production data libraries, on tape '999999' which is reused every day. It can be used to restore files if something goes terribly wrong in the overnight processing, reload a file if something happens to it the next day (we have had users accidentally do mass deletes), of to rebuild the test environment (PL).