Difference between revisions of "Information Systems:Overnight Processing"

From uniWIKI
Jump to navigation Jump to search
Line 45: Line 45:
 
- 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.
 
- 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.
+
- Run updates, reports, and housekeeping (clear work files and out queues, and delete unnecessary spool files).
   
 
=ENDOFWEEK=
 
=ENDOFWEEK=
Line 61: Line 61:
 
- It will then go into a restricted state. If ENDOFDAY or ENDWEEK has not completed (because of error, or looping) it will be ended. The restricted state will have a batch timer limit of three hours - if it is not finished by 6AM, it will be ended, and the system brought back up.
 
- It will then go into a restricted state. If ENDOFDAY or ENDWEEK has not completed (because of error, or looping) it will be ended. The restricted state will have a batch timer limit of three hours - if it is not finished by 6AM, it will be ended, and the system brought back up.
   
  +
- A full system save is done. On the first of the month, it is written to a monthly tape; which has the period number as the label, and has permanent retention. Any other day, it is written to one of the 40 tapes that are cycled through and rewritten.
-
 
  +
  +
=Emails=
  +
  +
The overnight processing sends messages so that we know it is running normally. If a message is not received when expected, it could mean that processing is taking longer than usual, or that something has gone wrong.
  +
  +
==Daily overnite processing is starting==
  +
  +
The first message shows that the end of day has started at the expected time (1AM). Warehouse supervisors can delay the end of day processing to 2AM, but this has not happened in several years.
  +
  +
==Daily overnite processing ended Normally==
  +
  +
This message is sent about 4:00AM and means that processing that requires all users to be off the system has completed, and that the system is now available. If this message is not received from Monday to Saturday, it could mean that there was a problem, and the system was started by the batch time limit. This message cannot be sent when there is an IPL on Sunday.
  +
  +
==All systems are back up==
  +
  +
This message is issued at about 4:00AM by the program that starts up the system and back ground programs. It is issued both when the overnight program calls it, and when called by the batch time limit.
  +
  +
==Statistics files rebuild is complete==
  +
  +
This is sent around 5:15AM by the program that has built the analytical files used in InfoNet, that are too complex to build on user request. To save processor time, and speed up response, they are updated as part of the overnight process. To make the system available to users sooner, they are processed after the system comes out of the restricted state. This message can be an hour later on the first of the month.
  +
  +
==Tape 999999 used for Power8 backup==
  +
  +
This message is not sent until 8:00AM, as it has to wait for Catapult to be available. Catapult builds this email based on the BRMS recovery report, and archives it to SuperServer.

Revision as of 15:51, 27 October 2015

Schedule

The overnight processing - which include end of day, week, month, and year - is run from the job schedule. To see these jobs, key in WRKJOBSCDE and press enter. Page down until you get to 'END'. Note that ENDOFMONTH will automatically run the end of year (both fiscal and calendar) automatically.

                        Work with Job Schedule Entries                BART     
                                                            10/27/15  12:48:35 
                                                                               
Type options, press Enter.                                                     
  2=Change   3=Hold   4=Remove   5=Display details   6=Release                 
  8=Work with last submission    10=Submit immediately                         
                                                                               
                                                                   Next        
                         -----Schedule------             Recovery  Submit      
Opt  Job         Status  Date       Time      Frequency   Action   Date        
 
__   ENDOFDAY     SCD    USER DEF   01:00:00  *WEEKLY    *NOSBM    10/28/15    
__   ENDOFMONTH   SCD    *MONTHSTR  05:30:00  *MONTHLY   *NOSBM    11/01/15    
__   ENDOFWEEK    SCD    *SUN       01:00:00  *WEEKLY    *NOSBM    11/01/15    
__   EODEMAIL     SCD    *ALL       08:00:00  *WEEKLY    *NOSBM    10/28/15 
__   EODSAVE      SCD    *ALL       03:00:00  *WEEKLY    *NOSBM    10/28/15 
                
Parameters or command                                                          
===> _______________________________________________
F3=Exit   F4=Prompt          F5=Refresh   F6=Add    F9=Retrieve                
F11=Display job queue data   F12=Cancel   F17=Top   F18=Bottom

ENDOFDAY runs Monday through Saturday. The program called is EODDAILY from library UNIPHARMIT.

ENDOFWEEK runs Sunday. The program called is EODWEEKLY from library UNIPHARMIT.

Both of these must run after midnight, as they use yesterday's date instead of today's. Also because the temporary backup tape has a retention period of one day.

ENDOFMONTH runs on the first of the month. The program called is EOM from library UNIPHARMIT.

EODSAVE runs after the daily or weekly processing, and calls EODBU from library UNIPHARMIT, which calls BRMS to do a backup.

EODEMAIL runs every morning to email users the tape used for backup. The program called is EODEMAIL from library UNIPHARMIT.

ENDOFDAY

This 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).

ENDOFWEEK

This will run the same programs as ENDOFDAY, then run weekly updates and reports.

ENDOFMONTH

This runs after all other overnight processing, as it can run while users are on the system. It also runs updates (including period roll), and reports (including finance reports to check that A/R, A/P, and unmatched PO's are in balance). If the current month is January, a copy of the warehouse item file (SROSRO) is saved. The period roll for into fiscal period 1 will do processing for fiscal year end.

EODSAVE

- This will do a controlled shut down of Domino - which has been left up so that IT can receive emails from the overnight processing.

- It will then go into a restricted state. If ENDOFDAY or ENDWEEK has not completed (because of error, or looping) it will be ended. The restricted state will have a batch timer limit of three hours - if it is not finished by 6AM, it will be ended, and the system brought back up.

- A full system save is done. On the first of the month, it is written to a monthly tape; which has the period number as the label, and has permanent retention. Any other day, it is written to one of the 40 tapes that are cycled through and rewritten.

Emails

The overnight processing sends messages so that we know it is running normally. If a message is not received when expected, it could mean that processing is taking longer than usual, or that something has gone wrong.

Daily overnite processing is starting

The first message shows that the end of day has started at the expected time (1AM). Warehouse supervisors can delay the end of day processing to 2AM, but this has not happened in several years.

Daily overnite processing ended Normally

This message is sent about 4:00AM and means that processing that requires all users to be off the system has completed, and that the system is now available. If this message is not received from Monday to Saturday, it could mean that there was a problem, and the system was started by the batch time limit. This message cannot be sent when there is an IPL on Sunday.

All systems are back up

This message is issued at about 4:00AM by the program that starts up the system and back ground programs. It is issued both when the overnight program calls it, and when called by the batch time limit.

Statistics files rebuild is complete

This is sent around 5:15AM by the program that has built the analytical files used in InfoNet, that are too complex to build on user request. To save processor time, and speed up response, they are updated as part of the overnight process. To make the system available to users sooner, they are processed after the system comes out of the restricted state. This message can be an hour later on the first of the month.

Tape 999999 used for Power8 backup

This message is not sent until 8:00AM, as it has to wait for Catapult to be available. Catapult builds this email based on the BRMS recovery report, and archives it to SuperServer.