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.
A job is a set of instructions about how, when and where to perform an automated task. In the job rule definition, one can specify an alias (short name) for the job, a command or script to run, an agent or a list of agents needed to run the job, the days and times to run the job, the dependencies (job, file, variable, time) and constraints that need to be satisfied before the job can be run, and other runtime criteria (such as parameter overrides, interception and job control).
A job can be defined and saved. The saved job definition can be scheduled for running as scheduled job or unscheduled (ad hoc) job. Jobs may be grouped into a hierarchy, where each job in the group can inherit properties from its parent group. Job groups can belong to other job groups.
A job's or job group's definition can be added to the production schedule either manually on demand or automatically through a calendar.
Currently supported job types include:
Job is the base of TES 6.2 job types. The FTPJob, JobGroup, MPEJob, OS400Job, OSJob, OVMSBatch, OVMSCommand, OVMSJob and ServiceJob objects are derived from Job and share a common base structure.
A job instance has its own life cycle, with the associated statuses, in the production schedule.
A typical life cycle is one where the job:
Other statuses (e.g. Completed Abnormally) are also possible depending on certain conditions and exceptions.
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 Job object provides a method called getList . This method has no parameters. The following REST API call will return a list of job definitions.
The Job object provides a method called get . The parameter called id (e.g. 732) is required, and specifies the job definition to be retrieved. The following REST API call will return the specified job definition if it exists and an exception if the job definition cannot be found.
The Job object provides the create method. The method has many parameters, but not all are required. Default values can be used by TES 6.2 for optional parameters.