ajsqlalter
- Organization of this page
Format
ajsqlalter
[-l Maximum-number-of-executing-jobs]
[-b Maximum-number-of-waiting-jobs]
[-r]
[-c class-name]
[-h logical-host-name]
Description
Temporarily modifies the operating environment for the queueless agent service.
Execution privileges
In Windows: Administrators privileges
In UNIX: Superuser privileges
Storage directory
- In Windows:
-
JP1/AJS3 - Manager-installation-folder\bin\
JP1/AJS3 - Agent-installation-folder\bin\
- In UNIX:
-
/opt/jp1ajs2/bin/
Arguments
-l Maximum-number-of-executing-jobs
Specify the maximum number of queueless jobs that can be executed concurrently.
You can specify a value from 0 to 1,024.
If you execute the command without specifying this option, the command terminates normally, but the maximum number of queueless jobs that can be executed concurrently is not changed.
If you specify the option without specifying its value, the command terminates abnormally.
If you attempt to execute queueless jobs when the number of concurrently executing queueless jobs has already reached the maximum, the jobs are stacked to wait on the queueless agent service. Jobs can be stacked until the maximum number of waiting jobs is reached.
To change the maximum number of concurrently executable jobs for a specific class, execute the command with the -c option specified.
To change the maximum number of concurrently executable jobs for the overall queueless agent service (default class), omit the -c option.
To change the maximum number of concurrently executable jobs for a class on a logical host, execute the command with both the -c and -h options specified.
-b Maximum-number-of-waiting-jobs
Specify the maximum number of queueless jobs that can be stacked on the queueless agent service.
You can specify a value from 0 to 102,400.
If you execute the command without specifying this option, the command terminates normally, but the maximum number of queueless jobs that can be stacked on the queueless agent service (maximum number of waiting jobs) is not changed.
If you specify the option without specifying its value, the command terminates abnormally.
If an attempt is made to execute a queueless job when the maximum number of waiting jobs has already been reached, the job fails to start.
To change the maximum number of waiting jobs for a specific class, execute the command with the -c option specified.
To change the maximum number of waiting jobs for the overall queueless agent service (default class), omit the -c option.
To change the maximum number of waiting jobs for a class on a logical host, execute the command with both the -c and -h options specified.
-r
Erases the user mapping cache.
By default, the system does not erase the user mapping cache.
If you specify this option with the -h or -c option, the system ignores the specifications of the logical host and class.
-c class-name
Specify the name of the class for which you want to temporarily change the operating environment.
If this option is not specified, the entire queueless agent service (default class) is assumed.
This option does not affect the -r option.
-h logical-host-name
Specify the name of the logical host for which you want to temporarily change the operating environment. You can only specify a logical host on the local host.
If you omit this option, the system assumes the physical host.
This option does not affect the -r option.
You must specify this option with the -c option.
Notes
-
Before you execute this command, make sure that the queueless agent service is started and the queueless job execution environment for the relevant logical host is set up. If the queueless job execution environment for the relevant logical host has not yet been set up, execute the ajsqlsetup command to set up the queueless job execution environment. For details on the ajsqlsetup command, see ajsqlsetup in 4. Commands Used for Special Operation.
-
When you execute the command with the -r option specified, make sure that a queueless job is not being executed.
-
After you change the login shell, password, and other information about the OS user who executes queueless jobs, you must clear the user mapping cache. The cache can be cleared by executing the command with the -r option specified. If you continue operation without clearing the cache, queueless jobs executed after the OS user information is changed might fail to start or end abnormally.
Note that the user mapping cache is also erased when the queueless agent service and queueless file transfer service are restarted.
Return values
|
0 |
Normal end |
|
Other than 0 |
Abnormal end |
Example
In this example, the command changes the maximum number of concurrently executable jobs for the overall queueless agent service (default class) to 50.
ajsqlalter -l 50