Setting the Job Parameter as the Wait Rule

In Hinemos, you can set various conditions and values as a job’s wait rule.

In the latest version (Hinemos ver.6.1), you can set the following as a wait rule.
– Job (end status)
– Job (end value)
– Time
– Time after session started (minutes)
– Job variable
– Cross session job (end status)
– Cross session job (end value)

In this article, we introduce you to the job parameter.

Let’s say there are jobs set as described below.


→Checks whether a particular flag file exists, and executes Job 2 if the file exists, but skips Job 2 if the file does not exist.

→The preceding job of Job 1. It will be executed only if the flag file exists.

→The preceding job of Job 2. It will be executed if the end status of Job 2 is “Normal”.

Condition: All the jobs end with end status “Normal” regardless of whether the flag file exists or not.

◯Preparing the Script

First, create a script that “checks whether a flag file exists or not, and then returns a different value depending on whether the file exists or not”.

This time, we created a script that returns the following value if “flag_file” exists,

and returns the following value if the file does not exist.

◯Creating jobs
Create a job unit including the following command jobs.

Configure each command jobs as follows.

1. Enter the command we tested on the console to Start Command field.

2. Click the “Command Result Extractor” button to display the “Command Result Extractor List”.

3. Enter the following values to the Name and Value fields, and check the checkbox saying “Read from standard output(Regular Expression)”.

1.Enter the following on the wait rule setting screen.

2. Check the “End if condition unmatched” checkbox and set the end status and the end value as shown below.

*Specify a command such as “sleep 1” as the start command.

1. Enter the following on the wait rule setting screen.

*Specify a command such as “sleep 1” as the start command.

That’s it for the setup!

Now let’s execute the job.

◯If the flag file (flag_file) exists

All jobs, including Job 2, were executed and ended with end status “Normal”.

◯If the flag file (flag_file) does not exist

Job 2 was not executed (number of executions: 0), and all the other jobs ended with end status “Normal”.

As you can see, the job parameter setting allows you to create a more complex sequence of jobs which was not possible with the end status and end value setting.

That’s it for today.
And as always, thanks for reading!