Date: Thu, 28 Mar 2024 17:38:14 +0000 (UTC) Message-ID: <184910085.11789.1711647494713@change.sos-berlin.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_11788_313830236.1711647494713" ------=_Part_11788_313830236.1711647494713 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
For example, if I have to do some database maintenance work? We're going= to have 100s of jobs, so we will need to be able to disable all jobs at th= e same time. The "Terminate" option of the main JOC menu isn't quite a grac= eful solution.
There are two possible parts to a solution Process Classes<= /span> and Examples = for the use of locks.
Process classes are objects which can be assigned to jobs. In the situat=
ion described here we are interested in using the process class to restrict=
the number of instances of a job that can be run at any one time. Setting =
the "tasks
" parameter to "0
" for a job will allow=
all instances of that job to end regularly but prohibit new instances from=
starting.
We recommend setting up "Resource Maintenance" jobs to automati=
cally set the tasks
parameter to 0
for all the jo=
bs using a resource and then reset the value after maintenance.
See also:
It is not necessary to stop or suspend the JobSchedulers
Note that in cluster operation all the JobSchedulers in a cluster will b= e using the same database, meaning that for database maintennace all jobs b= eing executed by all the JobSchedulers will have to be stopped. In addition= the JobSchedulers themselves will have to be suspended as the will otherwi= se continue to write their heartbeats into the database.
See also: