Hitachi

JP1 Version 12 JP1/Automatic Job Management System 3 Command Reference


jpqagtalt

Organization of this page

Format

jpqagtalt
     [-mh manager-host-name]
     -ah agent-host-name
     -cp time-time=concurrently-executable-job-limit...
     [-em]

Description

The jpqagtalt command changes the maximum number of jobs that can concurrently be executed on an agent host registered in the manager host.

Execution privileges

You must have the following JP1 privilege:

However, specifying the -em option requires the following privileges (but does not require JP1_JPQ_Admin privileges).

Arguments

-mh manager-host-name

When you want to change the maximum number of concurrently executable jobs on an agent host, specify the name of the manager host on which the agent host has been registered.

You can specify a character string of 1 to 255 bytes.

By default, the system assumes the local host name.

When you specify this option together with the -em option, you can specify only two types of host names: the local host name and the logical host name on the local host. Specifying any other value results in an error (error code: 25). Also note that you cannot specify an alias host name in the -mh option.

-ah agent-host-name

Specify the name of the agent host for which the number of concurrently-executable job limit is to be changed.

You can specify a character string of 1 to 255 bytes.

-cp time-time=number-of-concurrently-executable-job-limit

Specify the period in which to change the number of concurrently executable job limit and specify the number of concurrently-executable job limit.

Specifying the concurrently-executable job limit allows you to limit the number of jobs that can be concurrently executed by this agent host. The command applies to queue jobs and submit jobs only.

Once the specified concurrently-executable job limit is reached, any extra ones will be queued (for waiting for execution) until the job is completed.

Specify the period by time and time hyphened. Specify the time in units of 30 minutes in the hh:mm format.

hh: You can specify 0, or 00 to 23 hours.

mm: You can specify 0, 00 or 30 minutes.

For the number of concurrently-executable job limit, you can specify 0 to 4,294,967,295.

If the specified period contains the time when you execute the command, the number of concurrently-executable job limit is changed immediately.

You can specify multiple periods and numbers of concurrently-executable job limit. If you specify multiple periods, however, the values set later are reflected. (For example, if you set -cp 1:00-2:30=5 2:00-4:00=10, the number of concurrently-executable job limit for an overlapping period, 2:00 to 2:30 is 10.)

See Additional information covering examples of specifying the number of concurrently-executable job limit. Reference it as necessary.

-em

Specify this option for emergency execution.

Specifying this option enables emergency execution upon failure because a request is sent to a different communication path that is not used under normal conditions.

When you specify this option, note that you cannot assign an IP address to the manager host name.

Notes

  1. This command cannot be used for a request from JP1/AJS3 to JP1/NQSEXEC or JP1/OJE for VOS3.

  2. The concurrently-executable job limit specified by this command does not include concurrently-executable event job limit.

  3. If you omit the number of concurrently-executable jobs for a period, the default is 0. For example, the -cp 10:00-22:00=10 expression alone means that the limit value is 0 for the 00:00 to 10:00 period, 10 for the 10:00 to 22:00 period, and 0 for the 22:00 to 00:00 period.

  4. You should use the -em option for the sole purpose of recovering from an agent host failure. You should avoid specifying the -em option under any normal condition, because you may fail to take corrective action when a failure actually occurs.

Return values

0

Normal end

1

Invalid parameter value

2

An attempt to change the maximum number of concurrently executable jobs failed due to an internal cause of the host on which the jpqagtalt command was executed.

5

Initialization has failed.

  • The definition of the logical host name or the environment setting contains an error.

6

Memory became insufficient on the host on which the jpqagtalt command was executed.

7

A logical error occurred on the host on which the jpqagtalt command was executed.

25

The specified manager host name is neither the local host name nor the logical host name.

100

The host on which the jpqagtalt command was executed cannot connect to the manager host via TCP/IP communication.

  • The host on which the jpqagtalt command was executed cannot connect to the manager host because TCP/IP is not set up correctly.

  • The manager host name is invalid, or the manager host process stopped.

102

The IP address could not be resolved from the name of the manager host on which the jpqagtalt command was executed.

200

The manager host does not accept changes to the number of concurrently-executable job limit.

  • The manager host is now being started, now being stopped, has stopped, or is running in the reduced-operation mode.

201

You cannot use a specified agent host.

  • The specified agent host is not found.

202

The manager host has returned no response.

203

The number of concurrently-executable job limit could not be changed successfully owing to an internal cause of the manager host.

206

You do not have the privilege required to change the number of concurrently-executable job limit.

219

The manager host is busy.

220

The manager host memory is insufficient.

222

A fatal error has occurred.

  • A system call error has occurred.

223

The manager host encountered a logic error.

224

You have issued a request to a host other than JP1/AJS3.

226

Invalid execution environment

Additional information

The following gives examples of specifying the number of concurrently-executable job limit.