All RevSoft products have a Distributed Architecture with 2 basic differences to the Centralized model:

1. They run on your existing Hardware,
2. There is NO Central Scheduler Server.

The main reasons for the Distributed Architecture are:

1. Eliminate the Central Point of Failure,
2. Make all Servers decision makers,
3. Speed and Efficiency - as decisions are made locally it is faster,
4. Eliminate Roll Outs to update the scheduled jobs and objects.

In the Centralized model you can View, Control & Manage all the jobs from the Central Scheduler Server.

In the Distributed model you are in control of how many Focal Points that you have and Enterprise Jobs that can be Viewed, Controlled & Managed from any of the Focal Points.

See how an IBMi Series job is Viewed, Forced to run and Managed from Focal Points that are AIX, IBMi and WINDOWS Servers.

Jobs that execute and then Trigger other jobs locally will be executed a lot faster than having to go an external Server to evaluate - What happens next?

See how on a P05 IBMi Server a job can complete and then 10 Trigger Dependent Jobs in under 1 second.

We have seen how cumbersome this can be in the Centralized model - Roll Outs, Recompiles etc., lots of work.

The Distributed model has simplified this down to 2 steps:

1. Create the new Job,
2. If the REVSCH Operations is open prior to creating the new Job then click on Refresh.

(Step 2 is optional and only if you like to watch the Job Execute as Step 1 has already created the Job to run).

See how a new Job is created and watch it execute.

This is probably the most difficult process in the Centralized model.

The Distributed model has simplified this down to 1 step:

1. In the REV SCH Operations select the Job → Right Click → Skip → Check the boxes for the Multi Run executions to be skipped.

In Single Run Jobs you can Skip Future Scripts,

In Multi Run Jobs you can Skip Future Executions,

In Group Jobs (Single & Multi Run) you can Skip Future Group Member Executions.

See how a Job that is executing has 3 multi run executions skipped and watch it execute.

Calendars can be created on a Server and Published to other Servers.

See how a Calendar and Calendar Data is created on an IBMi Server and published to AIX, IBMi and WINDOWS Servers.