Cisco Tidal Enterprise Scheduler 6.2 REST API Reference Guide
- Updated:
- June 9, 2014
Chapter: JobRun
Overview
Associated with a Job is JobRun. Job Run is used to monitor and assign status, and take actions (e.g. cancel, rerun) based on the current status.
JobRun Type
Currently supported job run types include:
- FTPJobRun
- JobGroupRun
- MPEJobRun
- OS400JobRun
- OSJobRun
- OVMSBatchRun
- OVMSCommandRun
- OVMSJobRun
- ServiceJobRun
JobRun is the base of TES 6.2 job run types. The FTPJobRun, JobRunGroup, MPEJobRun, OS400JobRun, OSJobRun, OVMSCommandJobRun, OVMSJobRun and ServiceJobRun objects are derived from JobRunand and share a common base structure.
REST API Examples
From the browser, issue and then click Manual Commands (Post) to take you to the API post screen of the Client Manager. You can test the REST API examples from that screen. For valid parameters and successful execution of a request, you will get a response/result. For invalid parameters and unsuccessful execution of a request, you will get error messages and/or exceptions.
Example JOBRUN–1: Override JobRun instance
The JobRun object provides a method called override. The parameter called id (e.g. 120) specifies the JobRun instance to be overridden. The following REST API call will override JobRun 120.
Example JOBRUN–2: Override JobDependency instance of a JobRun
The JobRun object provides a method called overrideDependency . The method has two parameters. The first parameter called id (e.g. 124) specifies the JobRun instance. The second parameter called jobrundepid (e.g. 40)specifies the JobDep (Job dependency) instance. The following REST API call will override JobDependency 40 of JobRun 124.
Feedback