Submitting batch jobs

The most common way to submit a job is through the M3 job scheduler (CSCHJOB) or from an interactive program. The submitted jobs are managed by the batch job manager (CMNGJOB).

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

• Submit by job scheduler

  CSCHJOB is continuously examining the queue of scheduled job to determine if the condition to start a job is met. The most common conditions are only dependent on the start time/date and periodicity of the scheduled job. Another condition can be to run the job in a certain sequence. If all conditions are met, CSCHJOB submits the job.

• Manually submitted by user or automatically as part of a workflow

  When the job is submitted from the interactive environment, the user normally controls the submission, such as ordering a printout or another batch job. But it can also be a part of a process as described above, to reduce the time the user has to wait by submitting non time-critical updates and other processes in a background job.

  When running a batch job from the AUX – Auxiliary Functions menu in M3 BE, we recommend that you:

  • have no other user logged onto the system
  • stop all auto start jobs (ASJ) for the component
  • have no more than one active job allowed for the job queue (defined in MNS300/E)

  Example:

  When running 'Allocated Quantity. Re-created' (MMS925), the allocation auto start job should not be running, and no users should be performing any allocations (run it on a restricted system). The reason for this is that all selected records are first cleared, and then they are rebuilt one-by-one. Allocations that occur between clearing and rebuilding for any particular item/warehouse record will be counted twice. These restrictions are not normally necessary when rebuilding a single item/warehouse, since the risk that an allocation occurs between clearing and update is minimal.