System Maintenance Run Overview

There are several functions in M3 Business Engine that are controlled by date, and when the date changes several checks and updates have to be done. System Maintenance Run in M3 Business Engine executes a number of programs which 'clean up' certain elements of M3 database. Some of the programs are always executed when the System Maintenance Run starts, while others are started optionally.

Using System Maintenance Run

The system maintenance run is an alternative to the normal night run (CRS999 - Night Run. Start). It adds some flexibility since you can define your own runs. For example, you can have different night runs for different occasions like a Weekend Night run or a Monday Night run etc.

Note:  It is recommended to execute the System Maintenance Run each night.

System Maintenance Run and Job Scheduler

The M3 Business Engine Job Scheduler is used to run programs on schedule. In order for a function to run on a schedule, M3 Business Engine System Maintenance Run must be defined in the M3 Business Engine Job Scheduler as a scheduled job. M3 Business Engine System Maintenance Run runs a number of predefined programs once each night, while other scheduled jobs in M3 Business Engine Job Scheduler often runs one defined program.

For further information on Job Scheduler, refer to M3 Business Engine Administrator's Guide for Job Scheduler.

Solution for Parallel Run

It is possible to run all System Maintenance Runs in parallel.

Parameters on the E panel in 'Night Run.Start (CRS999)' and the Run function field in SHS101 indicate whether the auto jobs required to be shut down automatically during the System Maintenance Run.

Shutting down the auto jobs are not necessary from a data consistency point of view but could be selected if you want to minimize the impact on the System Maintenance Run from other activities in the system.

Note: Running MRP with automatic release of proposals with A2 messages where the grouping of, e.g. purchase order proposals might be affected.

In case of Multi Company installation, the M3 Business Engine database must have its own System Maintenance Run job set up and scheduled. Different database System Maintenance Runs can be submitted to run concurrently. It is also possible to select which companies and divisions are to be included in the System Maintenance Run for the database.

Ordering a System Maintenance Run

A System maintenance run can be ordered by in one of the following ways:

For more details, refer to Enabling System Maintenance Run.

System Maintenance Run Process

The System Maintenance Run parameters are specified in SHS100, SHS101 and SHS105. Before performing System Maintenance Run, the job needs to get scheduled. This is done in 'Job Schedule Category. Open' (SHS050) and 'Job Schedule. Open' (SHS030).

After a System Maintenance Run is scheduled in 'Job Schedule Category. Open (SHS050)' and in 'Job Schedule Function.Open (SHS030)' it needs to get ordered in 'System Maintenance.Open (SHS100)'. When completed, the SHS999CL is added to the CSHCTL file in 'Job Schedule Entry. Update (SHS010)'.

The job CSCHJOB 'Scheduled Job Driver' in the auto-job subsytem controls if there are any jobs in the CSHCTL file that should get started. At start time, the job CSCHJOB 'Scheduled Job Driver' in SHS999CLsubmits the file to CMNGJOB 'Batch Job Driver' which starts the System Maintenance Run.

When the System Maintenance Run process is finished, the job SHS999CL is again placed in the CSHCTL file in 'Job Schedule Entry. Update (SHS010)'.

Note: You can run System Maintenance without stopping the auto start jobs, however it is recommended to stop the auto start jobs before System Maintenance Run.
  • System performance is better if auto start jobs are stopped during System Maintenance Run.
  • If the auto start job 'Create MO/PO from planned orders (MMS940)' is stopped, no planned order will be released during System Maintenance Run. As a result, the grouping of released orders will work better.

System Maintenance Run Operations

System Maintenance Run History

If the Record history is selected on the E panel in 'System Maintenance.Open (SHS100)', information about the night run is stored in 'System Maintenance Run. Analyze' (SHS300). Here you can see the different night runs. A status indicates if the night run has performed ok, has failed, or is currently running. You can also see the start/finish time of the night and a run time.

If the night run has failed you can restart the night run from the beginning via option 9 'Run'.

Option 11 'Details' takes you to 'System Maintenance Details. Analyze' (SHS301) where you can se the same information about each individual job and also the number of records that has been processed. Here it is possible to restart a failed night run, via option 9=Restart, starting from the program that failed (or any other program). This will run the selected program and all programs with a higher sequence number. There are two additional inquiry types present also, so that you can compare several runs for one function within one job identity or one function within several job identities.

Related topics