IWeb Administrator Guide

Site Administration Settings

Registry Client users who do not have database access can use a special user interface to run the STOPALL job to manually stop all incomplete jobs run with the RUNALL job. After using this STOPALL job, the RUNALL job resumes at the next regularly scheduled interval, which is usually nightly.

The STOPALL job immediately stops all jobs that have not yet completed during the RUNALL job, which includes RDEDUP. If RDEDUP has not completed before the start of the workday, system performance may be impacted. Other RUNALL jobs that may be impacted by STOPALL include:

exec h33_process_possible(1)
exec h33_update_rc_patient
exec h33_dedup_vaccinations(2)
exec h33_dedup_contra(2)
exec h33_dedup_lead(2)
exec h33_dedup_patients(1)
exec h33_dedup_vaccinations(1)
exec h33_dedup_contra(1)
exec h33_link_race
exec h33_dedup_lead(1)
exec h33_process_provider_mapping
exec h33_dedup_patients(1)
exec h33_dedup_vaccinations(1)
exec h33_dedup_simple_masters(1)
exec h33_master_duplicate_scan(")

The STOPALL screen displays which process is currently running and its status. If no processes are running, a message displays stating that no processes are currently running.

Run STOPALL

Running STOPALL immediately terminates any database procedures that were started by the RUNALL task. The procedures are run again normally the next time RUNALL is scheduled to run.

To run STOPALL, click Administration > Site Administration > STOPALL. The Currently Running Procedure page opens and displays the name of the currently running procedure, if any. Click one of the available buttons on this page:

Run Stopall - Stops all currently running procedures. Click the Refresh button to view the current status.
Refresh - Refreshes the currently running procedure.
Back - Returns to the previous page.