Job Late Event

When the deadline time instructions of the monitored job is exceeded, and if the job is not yet started or still in progress, it triggers an event.

Overview

You can configure the event conditions with late job statuses KILL or CONTINUE or both. You can customize both mandatory and optional attribute filters to define specific conditions to trigger an event.

The mandatory attribute filters that you must provide to configure the event are:
  • Workstation
    Specify the workstation of the job stream that contains the job to be monitored. This detail must be preceded by the workstation folder details. The supported value type is string and for available operators see Event driven orchestration configuration attributes. Wildcard characters are permitted.
    The multipleFilters property is enabled and if required, you can provide multiple filters or values separated by a semicolon (;) for a single instance of the workstation attribute.
    The singlePredicate property is disabled, so you can also add multiple instances of the workstation attribute.
    Note: To add a workstation that is not saved in the folder specified by the current_folder property in the config.yaml file, provide the complete path to the workstation folder.
    Example: If the RS_AGT_1 workstation is saved under FOLDER1 under the root folder and the folder specified by the current_folder property in the config.yaml differs, then specify the workstation as follows in the event definition:
    /FOLDER1/RS_AGT_1
  • Job stream
    Specify the job stream that contains the job to be monitored. This detail must be preceded by the job stream folder details. The supported value type is string and for available operators see Event driven orchestration configuration attributes. Wildcard characters are permitted.
    The multipleFilters property is enabled and if required, you can provide multiple filters or values separated by a semicolon (;) for a single instance of the job stream attribute.
    The singlePredicate property is disabled, so you can also add multiple instances of the job stream attribute.
    Note: To add a job stream that is not saved in the folder specified by the current_folder property in the config.yaml file, provide the complete path to the job stream folder.
    Example: If the JOBSTREAM_AGT job stream is saved in the FOLDER1 under the root folder and the folder specified by the current_folder property in config.yaml differs, then specify the job stream as follows in the event definition:
    /FOLDER1/JOBSTREAM_AGT
  • Job
    Specify the name of the job that is monitored for a change in its status. When the specified status or statuses for the job is reached, it satisfies the condition. If you do not specify any value for internal or external status, whenever the job changes its status the filter is considered satisfied. The supported value type is string and for available operators see Event driven orchestration configuration attributes. Wildcard characters are permitted.
    The multipleFilters property is enabled and if required, you can provide multiple filters or values separated by a semicolon (;) for a single instance of the job attribute.
    The singlePredicate property is disabled, so you can also add multiple instances of the job attribute.
The optional attribute filters that you can add to trigger the event for specific scenarios are:
  • Job workstation
    Specify the workstation where the job to be monitored runs. This detail must be preceded by the workstation folder details. The supported value type is string and for available operators see Event driven orchestration configuration attributes. Wildcard characters are permitted.
    The multipleFilters property is enabled and if required, you can provide multiple filters or values separated by a semicolon (;) for a single instance of the job workstation attribute.
    The singlePredicate property is disabled, so you can also add multiple instances of the job workstation attribute.
    Note: To add a workstation that is not saved in the folder specified by the current_folder property in the config.yaml file, provide the complete path to the workstation folder.
    Example: If the RS_AGT_1 workstation is saved under FOLDER1 under the root folder and the folder specified by the current_folder property in the config.yaml differs, then specify the workstation as follows in the event definition:
    /FOLDER1/RS_AGT_1
  • Priority
    Specify the priority of the job. You can specify any value between 0-101. If you add a value, the change in status of the monitored job only with that priority satisfies the condition. The supported value type is nonnegativeinteger and for available operators see Event driven orchestration configuration attributes. Wildcard characters are not permitted.
    The multipleFilters property is enabled and you can specify single or multiple values or a specific range separated by a semicolon (;) for a single instance of the priority attribute.
    The singlePredicate property is disabled, so you can also add multiple instances of the priority attribute.
  • Late action
    You can add the expected late action for the monitored job to trigger an event. The valid attribute values are KILL and Continue. If you do not specify any value, when the job status change to either KILL or CONTINUE, it satisfies the condition. The supported value type is string and for available operators see Event driven orchestration configuration attributes. Wildcard characters are not permitted.
  • Recoverable
    This optional attribute is only valid if the job you want to monitor has recovery or rerun option. The supported value type is boolean and for available operators see Event driven orchestration configuration attributes. Wildcard characters are not permitted.
    You can either give true or false, if the job has any one of the following:
    • Recovery options stop and continue with a recovery job.
    • Rerun option.
  • Output conditions
    You can specify the name of the output conditions of the monitored job, if any exist. Make sure to add only those output conditions that are satisfied for the job. The supported value type is string and for available operators see Event driven orchestration configuration attributes. Wildcard characters are not permitted. You can add single or multiple values and if any one is matched, the filter is considered satisfied.
    The singlePredicate property is disabled, so you can also add multiple instances for the same attribute.