【Hinemos6.1】Introduction to the Enhanced Job Features

From Hinemos version 6.1, the job feature has been enhanced dramatically.This article will introduce you to some of those features.



Of the various features added to the job feature of Hinemos ver.6.1, the following 4 features will be explained.

①Detecting end delay by pridicting the job execution duration

→ From version 6.1, by collecting the information of the execution time of each job, Hinemos can detect and notify the delay of the jobs.

②Repeating the command execution

→ Until ver.6.0, only the job itself could be set to be repeated. From Hinemos ver.6.1, users can now specify whether to repeat the command or not.

③Cooperation with events accross sessions

→ Can set jobs existing outside the JobNet as preceding/subsequent job.

④Displaying execution duration on graphs

→ The job execution history can be displayed on graphs just like the monitor history.


Let’s see how Hinemos detects the end delay of jobs using features ② and ③.

Follow the steps below.

1.Create a job which lasts 2 minutes (“sleep 120 “) and executed 30 times

2.Create a job which will delay (stop the agent) the job created above

3.Create a JobUnit including job 1 and 2


●1.Create a job which lasts 2 minutes (“sleep 120 “) and execute it 30 times

Configure the delay setting as follows.


With the setting above, Hinemos will send a critical alert, set the end value of the job as “abnormal”, and stop the job with a command when the condition above is fulfilled.


Also, it will be required to collect the data of the job’s execution duration before performing the prediction.

Configure the number of data required to calculate the average value of job execution time from the maintenance perspective of [Hinemos Property] view.

The default value is “30”.

This time, we will use the feature for ②repeating the command execution to execute the job 30 times.

Open the “Control(node)” tab in the Job[Create/Modify Command Job] dialog and select “Retry Command”.


With the setting above, a 2 minutes job repeating 30 times will be created.


●2. Create a job to delay the execution time.

Under a different JobNet, create a job which stops the Hinemos Agent.(job5)

Execute “job5” using the feature which enable ③Cooperation with events accross sessions.

Until ver.6.0, users were required to copy the same job under a different JobNet each time because the wait rule was effective only within the same JobNet.

However, with the latest version of Hinemos, users can configure whether to start a job based on the status etc. of a job from a different session!

Select “Cross SessionJob” as the wait rule.

This time, we have set “JN2-job2” as the subsequent job and the “Job history range” as 5 minutes.


●3.Execute a JobUnit including job created in step 1 and 2.

The execution result of the JobUnit is shown below.

You can see that “job5” has been executed properly as the subsequent job of “JN2-job2”.

Also, “JN2-job1” has been stopped by a command since the duration of the job has been delayed by stopping the Agent.

You can confirm in the Event History that a property “Warning” has been notified.


Last but not least, from ver.6.1, you can now check the execution time of the job on a graph!

The graph can be seen in the performance perspective.


* The job execution history can be displayed on a line graph or a stack area graph.


That’s it for the introduction to the new job features from Hinemos version 6.1!

Thank you for reading!


Hinemos Subscription

If you are interested in using Hinemos in the enterprise environment, visit our online store Hinemos Store for information regarding our subscription packages of Hinemos. Various types of subscription are available with additional option features, support, etc., for enhancing the operation of Hinemos.

Go to Hinemos Store!

Note: Currently, our subscription is available only to customers located in the United States.


Follow our SNS accounts for updates and more!