Job Management Partner 1/Automatic Job Management System 3 Command Reference 2
Format
jpqjobalt
[-mh manager-host-name]
{-q queue-name|-ah agent-host-name}
{-h|-hr}
-j job-number
Description
Holds a job or releases a held job.
You can also apply this command to the JP1/NQSEXEC host job. In that case, however, the user can operate only the jobs he or she owns.
This command is applicable for the following jobs:
- When the database is in a standard configuration:
- Submit jobs and queue jobs
- 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)
Arguments
-mh manager-host-name
Specify the host name of the manager to which you have submitted a job to be held or released.
You can specify a character string of 1 to 255 bytes.
By default, the system assumes the local host name.
-q queue-name
Specify the name of the queue to which you have submitted a job to be held or released.
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 held or released.
You can specify a character string of 1 to 255 bytes.
During linkage with JP1/NQSEXEC, you cannot use this command for JP1/NQSEXEC queues.
-h
Holds a job.
-hr
Releases a held job.
-j job-number
Specify the job number of a job to be held or released.
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.
Note
During linkage with JP1/OJE for VOS3, you cannot use this command for JP1/OJE for VOS3 queues.
Return values
0 Normal end 1 Invalid parameter value 2 The job could not be held or released successfully owing to an internal cause of the hold or release requester. 5 Initialization has failed.
- The definition of the logical host name or the environment setting contains an error.
6 Hold or release requester's insufficient memory 7 The hold or release requester encountered a logic error. 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 hold or release 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 held or released successfully owing to an internal cause of the manager host. 206 You do not have the privilege required to hold or release the job. 207 The job to be held or released does not exist.
- The specified job is not in the database.
- The specified job has already ended.
208 The specified job is running. 219 The manager host is busy. 220 Insufficient manager host memory 222 A fatal error has occurred.
- An error has occurred in a system call.
223 The manager host encountered a logic error. 224 You have issued a job hold or hold release request to an unsupported host. 226 Invalid execution environment
Additional information
Even if you set the -h option for a held job or the -hr option for a job waiting for execution or time, the command ends normally. The job status is not, however, changed.
Copyright (C) 2009, 2010, Hitachi, Ltd.
Copyright (C) 2009, 2010, Hitachi Solutions, Ltd.