17.2.5 Setting up the queueless job execution environment

With the default settings, all processing for queueless jobs is disabled. Edit the jajs_start.cluster and jajs_stop.cluster commands to match operating requirements.

Organization of this subsection

(1) To ensure that the queueless agent service does not stop when the nodes are switched
(2) To ensure that the queueless agent service stops when the nodes are switched
(3) Notes

(1) To ensure that the queueless agent service does not stop when the nodes are switched

The following describes how to switch the nodes by detaching and re-attaching logical hosts.

If you use both physical and logical hosts at the same time or if you use multiple logical hosts at the same time, use the procedures described below.

(a) Edit jajs_start.cluster

Open the following file with a text editor such as vi:
```
/etc/opt/jp1ajs2/jajs_start.cluster
```
In the file, delete the shaded parts shown below.
Close the file.

Supplementary note:: After deletion of the comment symbol (: #) indicated by (1) in step 2, the start processing of the JP1/AJS3 service stops if the attachment of a logical host fails. If you want the start processing to continue, do not delete the comment symbol (: #).

(b) Edit jajs_stop.cluster

Open the following file with a text editor such as vi:
```
/etc/opt/jp1ajs2/jajs_stop.cluster
```
In the file, delete the shaded parts shown below.
Close the file.

Supplementary notes:

After deletion of the comment symbol (: #) indicated by (2) in step 2, error code 1 is returned if the detachment of a logical host fails.
After deletion of the comment symbol (: #) indicated by (3) in step 2, the start processing of the JP1/AJS3 service stops if the detachment of a logical host fails. If you want the start processing to continue, do not delete the comment symbol (: #).
After deleting the comment symbol (: #) indicated by (3) in step 2, you must also delete the comment symbol (: #) indicated by (2).

To Page Top

(2) To ensure that the queueless agent service stops when the nodes are switched

The following describes how to switch the nodes by stopping the queueless agent service.

If you use only logical hosts, use the procedures described below.

(a) Edit jajs_start.cluster

Open the following file with a text editor such as vi:
```
/etc/opt/jp1ajs2/jajs_start.cluster
```
In the file, delete the shaded parts shown below.
Close the file.

Supplementary note:: After deletion of the comment symbol (: #) indicated by (1) in step 2, the start processing of the JP1/AJS3 service stops if the attachment of a logical host fails. If you want the start processing to continue, do not delete the comment symbol (: #).

(b) Edit jajs_stop.cluster

Open the following file with a text editor such as vi:
```
/etc/opt/jp1ajs2/jajs_stop.cluster
```
In the file, delete the shaded parts shown below.
Close the file.

Supplementary notes:

After deletion of the comment symbol (: #) indicated by (2) in step 2, error code 1 is returned if the detachment of a logical host fails.
After deletion of the comment symbol (: #) indicated by (3) in step 2, the start processing of the JP1/AJS3 service stops if the detachment of a logical host fails. If you want the start processing to continue, do not delete the comment symbol (: #).
After deleting the comment symbol (: #) indicated by (3) in step 2, you must also delete the comment symbol (: #) indicated by (2).

To Page Top

(3) Notes

Before deleting a comment symbol (: #), review operation of the script without the comment symbol.
If you are performing an upgrade installation, copy the jajs_start.cluster.model and jajs_stop.cluster.model files, and then edit these files according to operating requirements. After editing the files, rename them to jajs_start.cluster and jajs_stop.cluster.
Attaching a logical host by setting the AJSQL_ATTACH environment parameter to yes requires that, for example, cluster software be used to stop the queueless agent service on the switch-from node, and to start the service on the switch-to node.

As a result of this operation, however, the status of a queueless job being executed on another logical host attached to the queueless agent service on the physical host or switch-from node might become Failed to start, Ended abnormally, or Unknown end status.

If you use queueless jobs on multiple hosts, use the procedures described here instead of using AJSQL_ATTACH.

For details about the AJSQL_ATTACH environment setting parameter, see 2.7 Setting up the queueless job execution environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.
Do not operate the system in a state with only logical hosts created by detaching the physical host from the queueless agent service.

If you do so, error messages normally output if startup of a queueless job fails and the information output to the standard error output during job execution might not be reported to the manager host.

To Page Top