The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
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.
Currently supported job run types include:
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.
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.
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.
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.