Page History

...

• Display feature availability
  StartingFromRelease 1.9

Related Issues

• Jira
  server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JS-1324

• Jira
  server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JS-1323

• Jira
  server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JS-1322

Implementation

Enforced Monitors are implemented in two stages:

...

• Return codes are handled after all Post-Processing Monitors have been executed, even if one of the Monitors returns false.
• The return code of the last Üost-Processing Monitor sets the return code of the job
• The value of spooler_process_result argument comes from the Monitor that was executed before the current Monitor.

See also

• The How to use Job Postprocessing Post-processing to handle Exit Codes article

References

Change Management References

Documentation

• The Monitors article
• The How to configure a Named Monitor article
• The How to add conditions for job execution with date calculation article
• The How to use Job Postprocessing Post-processing to handle Exit Codes article
• The Monitor XML Element in the JobScheduler Reference Documentation

...