Job Management Partner 1/Automatic Job Management System 3 Command Reference 2

jpqjobcan

Format

jpqjobcan
     [-mh manager-host-name]
     {-q queue-name|-ah agent-host-name}
     -j job-number
     [-em]

Description

Cancels execution of a job waiting for execution, being held, or waiting for time.

A job being executed is killed.

UNIX-based jobs can be forcibly terminated even with a signal-seizing application because SIGKILL is issued.

You can also cancel or kill the JP1/NQSEXEC and JP1/OJE for VOS3. In that case, however, the user can operate only the jobs he or she owns.

You can also cancel or kill jobs for the AS/400 system. You can specify only the -mh, -q, and -j options for the AS/400 system.

This command is applicable for the following jobs:

When the database is in a standard configuration:

Submit jobs and queue jobs

To forcibly terminate a PC job, UNIX job, action job, or custom job, use the ajskill command.

When the database is in a standard configuration without ISAM:

None

When the database is in a compatible ISAM configuration:

PC jobs (other than queueless jobs), UNIX jobs (other than queueless jobs), action jobs, custom jobs, submit jobs, and queue jobs

Execution privileges

You must have any of the following JP1 privileges:

• JP1_JPQ_Admin privilege
• JP1_JPQ_Operator privilege
• JP1_JPQ_User privilege (allows you to manipulate only the jobs you own)

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

• Windows: Administrators privileges
• UNIX: Superuser privileges

Arguments

-mh manager-host-name

Specify the name of the manager host to which you have submitted a job to be canceled or killed.

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.

-q queue-name

Specify the name of the queue to which you have submitted a job to be canceled or killed.

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

-ah agent-host-name

Specify the name of the agent host to which you have submitted a job to be canceled or killed.

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

During linkage with JP1/NQSEXEC and JP1/OJE for VOS3, you cannot use this option for JP1/NQSEXEC queues and JP1/OJE for VOS3 queues.

-j job-number

Specify the job number of a job to be canceled or killed.

You can use the jpqjobshow command to check the job number.

Make sure that you specify a job number in the range from 1 to 999999.

-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.

Note

You should use the -em option for the sole purpose of recovering from an agent 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	The job could not be canceled or killed successfully owing to an internal cause of the cancel or kill requester.
5	Initialization has failed. The definition of the logical host name or the environment setting contains an error.
6	Cancel or kill requester's insufficient memory
7	The cancel or kill requester encountered a logic error.
25	The specified manager host name is neither the local host name nor the logical host name.
100	The manager host cannot be connected for TCP/IP communication. Because TCP/IP is not validly set, the manager host cannot be connected. The manager host name is invalid, or the manager host process stopped.
102	The IP address could not be solved successfully by the manager host name.
200	The manager host does not accept a job cancel or kill request. 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 queue. The specified queue is not found.
202	No response from the manager host
203	The job could not be canceled or killed successfully owing to an internal cause of the manager host.
206	You do not have the privilege required to cancel or kill the job.
207	The job to be canceled or killed does not exist. The specified job is not in the database. The specified job has already ended.
219	The manager host is busy.
220	Insufficient manager host memory
221	Invalid user information about JP1/OJE for VOS3
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 job cancel or kill request to an unsupported host.
226	Invalid execution environment
230	You have attempted to kill a job, but the agent host has failed to kill the job. It cannot be determined whether the job has ended. (The jpqjobget command runs to check the job status, however, indicates that the job has ended.)

[Contents][Back][Next]

Copyright (C) 2009, 2010, Hitachi, Ltd.
Copyright (C) 2009, 2010, Hitachi Solutions, Ltd.