Page 5 of 100. Showing 992 results (0.011 seconds)
How to start jobs and job chains on a file event
In the sample below there are two different approaches described how you can start jobs on a file event. Using a file order source See also Documentation http://www.sos-berlin.com/doc/en/scheduler.doc/file_orders.xml File_order_source.jpg The job chain job_chain_file_order_source has a file order sourceJob Chains
Use of Job Chains Job chains can be seen as an assembly line on which multiple job nodes are passed, with each job making up one step in the processing of a chain. Job chains allow the reuse of jobs in different job chains with different parameter sets. Job chains allow dependencies to be mapped by, for exampleJob Streams
Scope Job Streams are a means to implement dependencies with jobs. This feature improves existing forward dependencies (job chains) by introducing backward dependencies (conditions). Job Streams bring a number of new objects to the user interface: Events Events are tokens that are created on-the-fly to signalHow to handle errors in a job chain made up from shell jobs
Introduction This example uses a simple job chain which starts shell jobs to demonstrate the different behaviors that can be configured for JobScheduler if an error occurs in one of the jobs. In particular, the effect of the stop_on_error and on_error parameters is demonstrated along with the use of suspended ordersExample showing how to run parallel jobs in a job chain
Example: Multiple parallel processes in a job chain The job chain is to start with a job with the name truncate_export_table. After this job has been completed four jobs with the name table partition are to be run in parallel. A single job that indexes the new partition tables is then to run. Finally, a furtherExample showing how to run parallel jobs repeatedly in a job chain
Availability See How to Execute Jobs in a Job Chain in Parallel for more information. Example: Multiple parallel processes in a job chain The job chain is to start with a job with the name truncate_export_table. After this job has been completed four jobs with the name table partition are to be runJob SOSSQLPlusJob
Introduction The SOSSQLPlusJob http://www.sos-berlin.com/doc/JITL/SOSSQLPlusJob.xml JITL job provides a standardized and parameterized interface … and passing on the results of a script execution to next job step as a JobScheduler Order parameter. The SOSSQLPlusJob can be used to execute existing SQL*PlusShould I use multiple jobs or one job with multiple orders?
We recommend using order jobs, i.e. one or more jobs in a job chain with multiple orders rather than multiple standalone jobs, (i.e. jobs that are started individually). Overview The advantages of order jobs are that these jobs and job chains: are independent of parameter values - only "What the job itself doesJob JobSchedulerManagedDatabaseJob
JITL: The Managed Database Job This job uses the deprecated sos.scheduler.managed.JobSchedulerManagedDatabaseJob that has been deprecated with Release 1.12. The JobSchedulerManagedDatabaseJobSOSHibernate job is provided as an alternative. This job is used to execute (SQL-)statements in a database and can be usedHow to skip nodes in a job chain and stop and temporarily disabled jobs
Stopping Jobs Stop_on_error.jpg When you stop a job using the JOC (JobScheduler Operations Center) this job will not run any more. When you stop a running job, the task will first be ended normally and the job will be stopped. When the stopped job is used in a job chain, all orders will wait before the node until