1. Before the full system backup runs (step before rebuilds), one must suspend ALL scheduled reports. It is best to suspend ALL in case the rebuilds take longer than expected or a full system restore is done later--no unexpected reports will suddenly jump into action. Also, by suspending all and later, unsuspending them in the right order, the reports will ALWAYS run in the correct order even when one report takes more than its usual time; the fact that the reports are then picked up by the date they were created, scheduled, or unsuspended will not create problems.
2. If rebuilds start during the weekend, some "one time" run of the usual reports can be done. Like all the normal Friday night and Saturday morning reports when rebuilds are planned for Saturday afternoon. Here is an example of the one up runs before upgrade/rebuilds of Aug 2003:

   652. statlog ADMIN OK Thu Aug 21 2003 at 17:02
   653. usercatchupsel ADMIN OK Thu Aug 21 2003 at 17:07
   654. dordersCUSTOM2 ADMIN OK Thu Aug 21 2003 at 17:17
   655. mordersCUSTOM2 ADMIN OK Thu Aug 21 2003 at 17:23
   656. dcancel ADMIN OK Thu Aug 21 2003 at 17:26
   657. mcancel ADMIN OK Thu Aug 21 2003 at 17:30
   658. claimlate ADMIN OK Thu Aug 21 2003 at 17:35
   659. 1stacqclaimdou ADMIN OK Thu Aug 21 2003 at 17:41
   660. 2ndacqclaimdou ADMIN OK Thu Aug 21 2003 at 17:46
   661. sercancelv2001 ADMIN OK Thu Aug 21 2003 at 18:15
   662. 1stacqclaim ADMIN OK Thu Aug 21 2003 at 19:45
   663. 2ndacqclaim ADMIN OK Thu Aug 21 2003 at 19:51
   664. setdelinq ADMIN OK Thu Aug 21 2003 at 20:22
   665. holdpickupGALL ADMIN OK Thu Aug 21 2003 at 20:22
   666. holdrecall2001 ADMIN OK Thu Aug 21 2003 at 20:28
   667. holdpickupLAW ADMIN OK Thu Aug 21 2003 at 20:40
   668. holdpickupMED ADMIN OK Thu Aug 21 2003 at 20:40
   669. holdpickupDOUC ADMIN OK Thu Aug 21 2003 at 20:45
   670. holdpickupBUS ADMIN OK Thu Aug 21 2003 at 20:45
   671. holdpickupMACKetal ADMIN OK Thu Aug 21 2003 at 20:50
   672. GLOBALordFRI2 ADMIN OK Thu Aug 21 2003 at 21:50
   673. MEMBordcusFRI2 ADMIN OK Thu Aug 21 2003 at 21:55
   674. STANDordcusFRI2 ADMIN OK Thu Aug 21 2003 at 22:00
   675. SUBordcusFRI2 ADMIN OK Thu Aug 21 2003 at 22:05
   676. adutextam ADMIN OK Fri Aug 22 2003 at 4:30
   677. recallsam ADMIN OK Fri Aug 22 2003 at 4:31
   678. searchplacedchrlst ADMIN OK Fri Aug 22 2003 at 4:36
   

3. After the successful rebuild and reviving of the system, ALL suspended reports are unsuspended working in the proper order from 00:00 through to 24:00. SELECT THE DATE TO BEGIN FOR ALL DAILY reports as the NEXT day (ie. system revived on Monday, unsuspended reports begin Tuesday). This will keep the reports in the proper order in the schedlist and it allows one to do special reports for date sensitive cases.
4. For the day the system is revived, run some reports in the AM:

5. newcash (copy/CHANGE/run ASAP)--one for each day the system was down and for the day BEFORE the system was down (if required and not yet produced).
6. NOTE: if #ed stations on newcash output--copy and run ASAP CIRCPAYUSERLOG and search for #ed station and record which branch took in this payment. Notate the same information on the e-mailed reports too.

Example from Aug 2003 Post rebuilds day:

704. dailybackup ADMIN OK Mon Aug 25 2003 at 12:06
705. 3plusholdlist2002 ADMIN OK Mon Aug 25 2003 at 12:59
707. ckinexpectlist ADMIN OK Mon Aug 25 2003 at 13:08
708. DOWNchrglistNDL ADMIN OK Mon Aug 25 2003 at 13:16
709. Mackfinalist2 ADMIN OK Mon Aug 25 2003 at 13:16
710. DOUfinallist ADMIN OK Mon Aug 25 2003 at 13:21
712. doverdues2NOcnt ADMIN OK Mon Aug 25 2003 at 14:07
 This had zero results so didn't have to do another "real" report.
713. moverdue2 ADMIN OK Mon Aug 25 2003 at 14:23
714. moverdueRECALLED ADMIN OK Mon Aug 25 2003 at 14:31
715. moverdueRECALLPRTpostupgrd ADMIN OK Mon Aug 25 2003 at 14:34
716. expireholds ADMIN OK Mon Aug 25 2003 at 14:36
717. cleanholdshelf ADMIN OK Mon Aug 25 2003 at 14:42
718. purgeholds ADMIN OK Mon Aug 25 2003 at 14:43
721. newcashTHURaug21 ADMIN OK Mon Aug 25 2003 at 15:47