Information Systems:Overnight ENDOFDAY

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.

• 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

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

This does the overnight processing. It is called by EODDAILY and EODWEEKLY.

• 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), or to rebuild the test environment (PL).

We used to do the regular backup at this point instead of after all the overnight processing. Then we discovered (during a year end audit) that transactions for the day had not updated G/L, A/R. etc on the tape.

This is called by EOD.

• EODUPD

This does the updating that requires all users to be off the system. It is called by EOD.

• EODRPT

This generates reports. It is called by EOD.

• EODREBLD

This rebuilds/updates master and statistic files used by Web Orders and InfoNet. These are built as part of the overnight processing instead of when a user requests the information. This also clears work files and spool files. It is submitted to QBATCH by EOD, to run after the restricted state has ended; about 5:00AM.

• EODCLR

Deletes reports that are generated but will never be printed; for example pick and putaway lists that we don't use because we use RF. Clears temporary work files. The programs that use these files delete records for the user. This program clears the files, which gets rid of these deleted records. This is called by EODREBLD.

• OUTQCLEAR

Runs a query against a file of all entries in out queues PRT01 and QPRINT, and builds a file of reports that can be deleted. Then reads that file, and deletes them. This is called by EODCLR.

• WSOVERNIT1

This is part of the process to rebuild files for Web Orders. On the Power 8, the shell commands sometimes come to a hard stop and need an operator response. That would stop the over night processing from completing. So EODREBLD submits this program, does something else that takes about 20 minutes, then runs the next part. If some of the shell commands are not run, the only effect on Web Orders is that some pictures or specifications may be missing. This is called by EODREBLD.

• WSOVERNIT2

This rebuilds files used in Web Orders. They are built once here, so they don't have to be rebuilt every time a store makes a request. This is called by EODREBLD.

• EODEMAIL

This is called by the scheduler (job name EODEMAIL) every day at 8:00AM. It will email IT saying which tape volume was used for the backup, and archive the BRMS recovery reports to SuperServer.

Summary

Order of events:

Scheduled job name: ENDOFDAY, 1AM

1. CL: EODDAILY
   1. CL: EODEND2
   2. CL: EOD
      1. CL: EODBUTEMP
      2. CL: EODUPD
      3. CL: EODRPT
      4. SBMJOB: EODRBLD (queued until system up)

Scheduled job name: EODSAVE, 3AM

1. CL: EODBU
   1. CL: EODEND3
   2. SBMJOB: STRBKUBRM (full system save)

System up: ~5AM

1. EODRBLD from earlier job runs
   1. SBMJOB: WSOVERNIT1
   2. CL: WSOVERNIT2
   3. CL: EODCLR