Difference between revisions of "Information Systems:Overnight ENDOFDAY"
| Line 1: | Line 1: | ||
| − | The scheduler starts this job at 1:00AM; every morning except Sunday - when the End of Week is called. It calls [[ |
+ | 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. |
- End all programs that use ASW or extension files, and end subsystems so users cannot sign on. |
||
Revision as of 17:17, 4 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.