Scope
Events for In Conditions are created or deleted from Job Streams depending on the result of a previous Out Condition. Alternatively, Events can be manually created or deleted by use of the JOC Cockpit user interface. Follow the steps to create or delete an Event.
Steps to add or remove an Event
- Login to JOC Cockpit and switch to the Job Streams tab.
- Select the graphical view of the Job Stream.
- Events are represented by a hexagon. If any Out Condition is added to a job to create an Event then it will be displayed in the Job Streams graph.
- The Events in the Job Stream provide an action menu to Add Event or Delete Event.
- The hexagon action menu offers the option Add Event if the Event does not exist.
- The action menu offers the option Delete Event if the Event already exists.
Use-Cases
The Add Event and Delete Event operations have their own use cases. The Add Event and Delete Event operations can be used to explicitly trigger the start of the Job Stream or to stop the execution of a Job Stream.
Use Case 1: Add an Event
- To execute the further jobs in the Job Stream with the In Condition as the event created by the previously failed job then event of the failed job can be added manually to make the expression result true for the In Condition of further jobs in Job Stream.
- For example:
- There are two jobs in a Job Stream, job1, and job2 with the following conditions:
S. No. | Job Name | Condition | Expression | Command |
|---|---|---|---|---|
1. | job1 | In Condition | - | - |
Out Condition | rc:0 | job1 | ||
2. | job2 | In Condition | job1 | startjob: now |
Out Condition | rc:0 | job2 |
- For any reason, if the job1 is failed then the event job1 will not be created and the further execution of Job Stream will stop.
- Therefore, to continue the further execution of Job Stream the event can be added manually without executing the job1 again.
Use Case 2: Delete an Event
- To stop the execution of Job Stream or to make the result of the expression in the In Condition as false the events can be deleted from Job Stream.
- For example:
- There are two jobs in a Job Stream, job1, and job2 with the following conditions:
S. No. | Job Name | Condition | Expression | Command | Mark Expression |
|---|---|---|---|---|---|
1. | job1 | In Condition | - | - | |
Out Condition | rc:0 | job1 | |||
2. | job2 | In Condition | job1 | startjob: now | unchecked |
Out Condition | rc:0 | job2 |
- The event job1 is created by the successful execution of job1.
- The Mark Expression for job2 is unchecked which means that the execution of the job in the Job Stream will continue running until the result of expression for the In Condition is false.
- Therefore, to stop the further execution of Job Stream the event can be removed manually using Delete Event option from action menu.