Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1

14.7.1 Setting automatic startup and termination of the JP1/AJS3 service

The JP1/AJS3 service can be started automatically when the system starts, and can be terminated automatically when the system terminates.

Organization of this subsection

(1) Setting automatic startup and termination of the JP1/AJS3 service (JP1/AJS3 - Manager)

(2) Setting automatic startup and termination of the JP1/AJS3 service (JP1/AJS3 - Agent)

(3) Setting automatic startup and termination of the queueless agent service and queueless file transfer service

(4) Setting automatic startup and termination of the JP1/AJS3 Console services

(5) Setting automatic startup and termination of the JP1/AJS3 Check Manager service or the JP1/AJS3 Check Agent service

(6) Outputting the JP1/AJS3 process status when JP1/AJS3 is started automatically

(7) Setting the process behavior when memory becomes insufficient (AIX only)

(8) Setting automatic startup and termination of the JP1/AJS3 service that do not depend on the JP1_HOSTNAME environment variable

(1) Setting automatic startup and termination of the JP1/AJS3 service (JP1/AJS3 - Manager)

The following describes how to set automatic startup and termination of the JP1/AJS3 service (JP1/AJS3 - Manager).

(a) Setting automatic startup of the JP1/AJS3 service (JP1/AJS3 - Manager)

To ensure that the JP1/AJS3 service is started automatically when the system starts:
Open the following file with a text editor such as vi:
 
/etc/opt/jp1ajs2/jajs_start
 
In the file (automatic start shell script), delete the shaded part shown below.

If you choose to delete the comment symbol, review beforehand operation of the script after the deletion.
Note that in a standard configuration, if you delete the comment symbol from the : # WAIT_READY=YES line, startup of JP1/AJS3 - Manager fails. If JP1/AJS3 - Manager has been installed as a new installation, do not delete the comment symbol from this line. If the comment has been deleted from this line in an environment in which JP1/AJS3 - Manager has been upgraded from JP1/AJS2 - Manager, add the comment symbol (: #) to the line after migration to comment that line out.
This completes the setting for automatic startup of the JP1/AJS3 service.

(b) Setting automatic startup of the JP1/AJS3 service (JP1/AJS3 - Manager) to change the settings for the function that waits for connection to the RDB

The following describes how to change the maximum wait time for connection to the RDB and how to change the setting for the function that waits for connection to the RDB.

Note that both the embedded database and the function are enabled by default if JP1/AJS3 is installed as an upgrade from JP1/AJS2 07-10 or an earlier version.

To change the maximum wait time for connection to the RDB:
Execute the following command:
 
jajs_config -k [{JP1_DEFAULT|logical-host}\JP1AJSMANAGER\scheduler-service] "RDBCONNECTWAITTIME"=maximum-wait-time-for-connection-to-the-RDB
 
The specification of the {JP1_DEFAULT|logical-host} part depends on whether the host is a physical host or a logical host. For a physical host, specify JP1_DEFAULT. For a logical host, specify the logical host name.

For example, if you change the maximum wait time for the AJSROOT1 scheduler service on the physical host, you might be able to execute the following command:
jajs_config -k [JP1_DEFAULT\JP1AJSMANAGER\AJSROOT1] "RDBCONNECTWAITTIME"=dword:00000001
 
For details about the RDBCONNECTWAITTIME environment setting parameter, see 2.2 Setting up the scheduler service environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

Note

To use the function that waits for connection to the RDB in a cluster environment, perform the above task on both the primary and secondary nodes. Make sure that you specify the same value on both nodes.
Before the function that waits for connection to the RDB can be used, automatic startup of JP1/AJS3 at system startup must be enabled. To enable automatic startup, in the /etc/opt/jp1ajs2/jajs_start file, delete the shaded part shown below:

The following notes also apply:

On a physical host
When the system is restarted, if the function that waits for connection to the RDB is used and WAIT_READY=YES (the system waits for jajs_spmd startup) is specified, the scheduler service fails to start. If you want to use the function, add the comment symbol to disable the specification as follows: : # WAIT_READY=YES

On a logical host
No problem is caused if the WAIT_READY=YES specification is enabled.

This completes changing of the settings. The new settings are applied the next time that JP1/AJS3 starts.

Cautionary notes:

If the scheduler service fails to start at system startup, and the KAVS0999-W (a wait started) and KAVS0998-E (a wait failed) messages have been output, check the following points:

Whether the embedded database has been set up
If the embedded database specified in the scheduler service is not running, regardless of how long JP1/AJS3 waits, connection to the database will not succeed.
Confirm that the scheduler service is up and running without problem during setup.

Whether the embedded database definition has been changed
If the startup method is changed after the embedded database has been set up, the embedded database might be unable to start when the system starts. If this problem occurs, restore the initial values that were set during setup.

Whether the embedded database terminated abnormally when it terminated previously
If the embedded database terminates abnormally during the execution of a job, it might take time for the embedded database to start the next time. If startup of the embedded database takes time, the embedded database might not start within the default maximum wait time. Accordingly, make sure that you do not force the embedded database to terminate.

Whether the comment symbol (: #) on the WAIT_READY=YES line in the jajs_start file has been deleted
If the comment symbol (: #) has been deleted, add it to disable the WAIT_READY=YES specification.

If you know how long startup of the embedded database is delayed, you can also increase the maximum wait time for connection to the database.

(c) Setting automatic termination of the JP1/AJS3 service (JP1/AJS3 - Manager)

To ensure that the JP1/AJS3 service is terminated automatically when the system terminates:
Open the following file with a text editor such as vi:
 
/etc/opt/jp1ajs2/jajs_stop
 
In the file (automatic termination shell script), delete the shaded part shown below.

If you choose to delete the comment symbols, review beforehand operation of the script after the deletion.
Note that if you delete the comment symbols from the : # WAIT_READY=YES specification, the system will wait until the JP1/AJS3 service starts. That is, system startup will require a longer time. If system startup has precedence, do not delete the comment symbol.
This completes the setting for automatic termination of the JP1/AJS3 service.

(2) Setting automatic startup and termination of the JP1/AJS3 service (JP1/AJS3 - Agent)

The following describes how to set automatic startup and termination of the JP1/AJS3 service (JP1/AJS3 - Agent).

(a) Setting automatic startup of the JP1/AJS3 service (JP1/AJS3 - Agent)

To ensure that the JP1/AJS3 service is started automatically when the system starts:
Open the following file with a text editor such as vi:
 
/etc/opt/jp1ajs2/jajs_start
 
In the file (automatic start shell script), delete the shaded part shown below.

If you choose to delete the comment symbol, review beforehand operation of the script after the deletion.
Note that if you delete the comment symbol from the : # WAIT_READY=YES specification, the system will wait until the JP1/AJS3 service starts. That is, system startup will require a longer time. If system startup has precedence, do not delete the comment symbol.
This completes the setting for automatic startup of the JP1/AJS3 service.

(b) Setting automatic termination of the JP1/AJS3 service (JP1/AJS3 - Agent)

To ensure that the JP1/AJS3 service is terminated automatically when the system terminates:
Open the following file with a text editor such as vi:
 
/etc/opt/jp1ajs2/jajs_stop
 
In the file, delete the shaded parts shown below.

If you choose to delete the comment symbols, review beforehand operation of the script after the deletion.
Note that if you delete the comment symbols from the : # WAIT_READY=YES specification, the system will wait until the JP1/AJS3 service starts. That is, system startup will require a longer time. If system startup has precedence, do not delete the comment symbol.
This completes the setting for automatic termination of the JP1/AJS3 service.

(3) Setting automatic startup and termination of the queueless agent service and queueless file transfer service

The queueless agent service or queueless file transfer service can be started when the system starts or can be terminated when the system terminates if the automatic start or termination script is set to perform this.

Note that the queueless file transfer service is available in JP1/AJS3 - Manager but is not available in JP1/AJS3 - Agent. The setting for the service is required in JP1/AJS3 - Manager only.

(a) Setting automatic startup and termination of the queueless agent service

The following describes how to set automatic startup and termination of the queueless agent service.

Setting automatic startup of the queueless agent service
To ensure that the queueless agent service is started automatically when the system starts, you must set the automatic start script.
To set automatic startup of the queueless agent service in the automatic start script:

Open the following file with a text editor such as vi:
/etc/opt/jp1ajs2/jajs_start

In the file, delete the shaded part shown below.

If you choose to delete the comment symbol, review beforehand operation of the script after the deletion.

Close the file.

Setting automatic termination of the queueless agent service
To set automatic termination of the queueless agent service in the automatic termination script:

Open the following file with a text editor such as vi:
/etc/opt/jp1ajs2/jajs_stop

In the file, delete the shaded part shown below.

If you choose to delete the comment symbol, review beforehand operation of the script after the deletion.

Close the file.

(b) Setting automatic startup and termination of the queueless file transfer service

The following describes how to set automatic startup and termination of the queueless file transfer service.

Setting automatic startup of the queueless file transfer service
To ensure that the queueless file transfer service is started automatically when the system starts, you must set the automatic start script so that this is done.
To set automatic startup of the queueless file transfer service in the automatic start script:

Open the following file with a text editor such as vi:
/etc/opt/jp1ajs2/jajs_start

In the file, delete the shaded part shown below.

If you choose to delete the comment symbol, review beforehand operation of the script after the deletion.

Close the file.

Setting automatic termination of the queueless file transfer service
To set automatic termination of the queueless file transfer service in the automatic termination script:

Open the following file with a text editor such as vi:
/etc/opt/jp1ajs2/jajs_stop

In the file, delete the shaded part shown below.

If you choose to delete the comment symbol, review beforehand operation of the script after the deletion.

Close the file.

(4) Setting automatic startup and termination of the JP1/AJS3 Console services

The JP1/AJS3 Console services can be started when the system starts or can be terminated when the system terminates if the automatic start or termination script is set to do this.

The JP1/AJS3 Console services include the JP1/AJS3 Console Manager service and the JP1/AJS3 Console Agent service. The script must be set for each of these services.

(a) Setting automatic startup and termination of the JP1/AJS3 Console Manager service

The following describes how to set automatic startup and termination of the JP1/AJS3 Console Manager service.

Setting automatic startup of the JP1/AJS3 Console Manager service
To ensure that the JP1/AJS3 Console Manager service is started automatically when the system starts, you must set the automatic start script.
To set automatic start of the JP1/AJS3 Console Manager service in the automatic start script:

Open the following file with a text editor such as vi:
/etc/opt/jp1ajs2cm/jajscm_start

In the file, delete the shaded part shown below.

If you choose to delete the comment symbol, review beforehand operation of the script after the deletion.

Close the file.

Setting automatic termination of the JP1/AJS3 Console Manager service
To set automatic termination of the JP1/AJS3 Console Manager service in the automatic start script:

Open the following file with a text editor such as vi:
/etc/opt/jp1ajs2cm/jajscm_stop

In the file, delete the shaded part shown below.

If you choose to delete the comment symbol, review beforehand operation of the script after the deletion.

Close the file.

(b) Setting automatic startup and termination of the JP1/AJS3 Console Agent service

The following describes how to set automatic startup and termination of the JP1/AJS3 Console Agent service.

Setting automatic startup of the JP1/AJS3 Console Agent service
To ensure that the JP1/AJS3 Console Agent service is started automatically when the system starts, you must set the automatic start script.
To set automatic startup of the JP1/AJS3 Console Agent service in the automatic start script:

Open the following file with a text editor such as vi:
/etc/opt/jp1ajs2/jajsca_start

In the file, delete the shaded part shown below.

If you choose to delete the comment symbol, review beforehand operation of the script after the deletion.

Close the file.

Setting automatic termination of the JP1/AJS3 Console Agent service
To set automatic termination of the JP1/AJS3 Console Agent service in the automatic start script:

Open the following file with a text editor such as vi:
/etc/opt/jp1ajs2/jajsca_stop

In the file, delete the shaded part shown below.

If you choose to delete the comment symbol, review beforehand operation of the script after the deletion.

Close the file.

(5) Setting automatic startup and termination of the JP1/AJS3 Check Manager service or the JP1/AJS3 Check Agent service

The following describes how to set automatic startup and termination of the JP1/AJS3 Check Manager service or the JP1/AJS3 Check Agent service.

(a) Setting automatic startup of the JP1/AJS3 Check Manager service or the JP1/AJS3 Check Agent service

To ensure that the JP1/AJS3 Check Manager service or the JP1/AJS3 Check Agent service is started automatically when the system starts, you must set the automatic start script.

To set automatic startup of the JP1/AJS3 Check Manager service or the JP1/AJS3 Check Agent service in the automatic start script:

Open the following file with a text editor such as vi:
/etc/opt/jp1ajs2/jajs_start

In the file, delete the shaded part shown below.

If you choose to delete the comment symbols, review beforehand operation of the script after the deletion.

Close the file.

(b) Setting automatic termination of the JP1/AJS3 Check Manager service or the JP1/AJS3 Check Agent service

To set automatic termination of the JP1/AJS3 Check Manager service or the JP1/AJS3 Check Agent service in the automatic termination script:

Open the following file with a text editor such as vi:
/etc/opt/jp1ajs2/jajs_stop

In the file, delete the shaded part shown below.

If you choose to delete the comment symbol, review beforehand operation of the script after the deletion.

Close the file.

(6) Outputting the JP1/AJS3 process status when JP1/AJS3 is started automatically

For JP1/AJS3 - Agent, the JP1/AJS3 service status can be output when JP1/AJS3 services are started automatically. Output of the JP1/AJS3 service status cannot be set for JP1/AJS3 - Manager.

To enable output of the JP1/AJS3 process status, you must set the automatic start script.

To set the automatic start script to output the JP1/AJS3 process status when JP1/AJS3 is started automatically:

Open the following file with a text editor such as vi:
/etc/opt/jp1ajs2/jajs_start

In the file, delete the shaded part shown below.

If you choose to delete the comment symbol, review beforehand operation of the script after the deletion.

Cautionary note:

To enable output of the process status when JP1/AJS3 is started, you must delete the comment symbol (:#) from the :# WAIT_READY=YES specification.

Close the file.

(7) Setting the process behavior when memory becomes insufficient (AIX only)

In AIX, if memory becomes insufficient, the system might issue SIGKILL, causing the JP1/AJS3 process to terminate. To prevent termination, set early for the PSALLOC environment variable, and start JP1/AJS3.

Note that the NODISCLAIM environment variable must be set to true if the PSALLOC environment variable is set to early.

The following shows an example of setting the process behavior in the automatic script.

To set the process behavior in the automatic start script:
In the automatic start script, find the following line:
 
export PATH SHLIB_PATH LD_LIBRARY_PATH LIBPATH HCCLIBCNF
 
Insert the following entries after the line:
 
------------------------- Start of entries to be inserted
PSALLOC=early
NODISCLAIM=true
export PSALLOC NODISCLAIM
------------------------- End of entries to be inserted
unset LC_MESSAGES
cd /opt/jp1ajs2/bin
/opt/jp1ajs2/bin/jajs_spmd >/dev/null 2>/dev/null

(8) Setting automatic startup and termination of the JP1/AJS3 service that do not depend on the JP1_HOSTNAME environment variable

The JP1/AJS3 service can be automatically started or terminated without being depending on the JP1_HOSTNAME environment variable set in the environment.

To ensure that the JP1/AJS3 service is automatically started or terminated without being dependent on the JP1_HOSTNAME environment variable:

Open the following file with a text editor such as vi:

(a) For automatic startup of the JP1/AJS3 service

/etc/opt/jp1ajs2/jajs_start

(b) For automatic termination of the JP1/AJS3 service

/etc/opt/jp1ajs2/jajs_stop

In the file, delete the shaded part shown below.

If you choose to delete the comment symbol, review beforehand operation of the script after the deletion.

Close the file.

[Contents][Back][Next]

[Trademarks]