Cisco Cisco Workload Automation 6.3 Entwickleranleitung

Seite von 24
11
 
Operations
Operations
<operation name="inactrule">
      <input message="tns:inactrule"/>
      <output message="tns:inactruleResponse"/>
    </operation>
jobadd
The jobadd operation lets you add a job or job group to the production schedule. You can add a job either by alias or by 
ID. You can obtain the job occurrence ID and/or alias by using the listrule operation. Unlike the submit operation, the job 
is submitted adhoc. An adhoc job is not dependent on a calendar because a new instance is submitted manually into the 
schedule.
<operation name="jobadd">
      <input message="tns:jobadd"/>
      <output message="tns:jobaddResponse"/>
    </operation>
jobcancel
The jobcancel operation cancels a job occurrence with the specified job ID from the production schedule. You can also 
specify whether canceling th
e job affects other dependent jobs. You can obtain the ID by running the jobmon operation.
<operation name="jobcancel">
      <input message="tns:jobcancel"/>
      <output message="tns:jobcancelResponse"/>
    </operation>
jobdep
The jobdep operation displays all the dependencies of the specified type belonging to a job or job group.
<operation name="jobdep">
      <input message="tns:jobdep"/>
      <output message="tns:jobdepResponse"/>
    </operation>
jobgo
The jobgo operation overrides all dependencies for a job or job group, allowing the job or job group to launch. Obtain 
job run IDs by running the jobmon operation.
<operation name="jobgo">
      <input message="tns:jobgo"/>
      <output message="tns:jobgoResponse"/>