Details
-
Feature
-
Status: Released (View Workflow)
-
Minor
-
Resolution: Fixed
-
1.9.9, 1.10.3
-
None
Description
Current Situation
The job JobSchedulerCheckRunHistory has the parameters job_name and query. One job name and one query can be set
Desired Behaviour
It should be possible
- to define a delimiter seperated list of jobs
- to define a delimiter seperated list of queries
- if only one query is set then this will be executed for each job
- if less queries then jobs are set then these will be taken for the first number of jobs. The last query will be used for each further job
The delimiter can be , or ; or mixed.
Example
job1,job2;job3
This is an example for checking whether the last completedRun of job1 ended with an error and job2 completed today
<order job_chain="job_chain_check_job_chain_history" id="lastCompletedRunEndedWithError_multiple"> <params > <param name="query" value="lastCompletedRunEndedWithError,isCompletedToday"/> <param name="job_name" value="job1,job2"/> </params> </run_time> </order>
Attachments
Issue Links
- relates to
-
JITL-212 Provide a function for checking the job history in job monitors by use of web services
- Released
-
JITL-217 Provide a function for checking the job history in job monitors by use of the XML interface
- Released
-
JITL-228 Provide a function for checking the job chain and order history in job monitors by use of the XML interface
- Released
-
JITL-289 The job JobSchedulerCheckRunHistory should have some new possible values for the parameter query
- Released
-
JITL-219 The JITL job JobSchedulerCheckRunHistory should make use of the new class com.sos.jitl.checkrunhistory.JobHistory
- Released