jpqjobget

Format

jpqjobget
     [-mh manager-host-name]
     [{-q queue-name|-ah agent-host-name}]
     -j job-number
     [-oso standard-output-file-name]
     [-ose standard-error-output-file-name]
     [-di]
     [-cc]
     [-ea]

To Page Top

Description

Outputs job information about a certain job to the standard output file.

You can also output job information about the JP1/OJE for VOS3 hosts. In that case, however, the user can operate only the jobs he or she owns.

This command also outputs job information about the AS/400 system to the standard output file. 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

When the database is in a standard configuration without ISAM:

None

To Page Top

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)

To Page Top

Arguments

To Page Top

Notes

• As a result of job execution, if the standard output file and standard error output file are moved or deleted, you cannot obtain information about these files.

• If a file of several megabytes is transferred either during job registration or as the result of job information collection, the transfer may fail or take time.

To Page Top

Return values

0	Normal end
1	Invalid parameter value
2	Job information could not be output successfully owing to an internal cause of the output requester.
5	Initialization has failed. The definition of the logical host name or the environment setting contains an error.
6	Job information output requester's insufficient memory
7	The job information output requester encountered a logic error.
13	The file used to acquire data in the standard or standard error output file cannot be created because no file path exists.
14	The file used to acquire data in the standard output file or standard error output file cannot be created because you do not have the privilege required to access it.
15	The data in the standard output file or standard error output file cannot be written to the file owing to the insufficient disk size.
16	The file used to acquire data in the standard output file or standard error output file cannot be opened because it is used by another process.
17	The file used to acquire data in the standard output file or standard error output file cannot be created owing to a cause other than return values 13, 14, 15 and 16.
18	The standard output file or standard error output file could not be written successfully owing to a cause other than return values 13, 14, 15 and 16.
19	The file cannot be created because data in the standard output file or standard error output file could not be acquired from the manager host.
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 output job information. 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	Job information could not be output successfully owing to an internal cause of the manager host.
206	You do not have the privilege required to output job information.
207	The specified job is not found. The specified job is not in the database. The specified job information is deleted.
219	The manager host is busy.
220	Insufficient manager host memory
222	A fatal error has occurred. A system call error has occurred.
223	The manager host encountered a logic error.
224	An unsupported host was told to output job information.
226	Invalid execution environment

To Page Top

Output example

The following gives an example of file output.

The following gives the meanings of output contents.

JOBID

Indicates a job number.

OWNER

Indicates the job's owner name.

JOBNAME

Indicates a job name.

When you use a QUEUE job or the jpqjobsub command to specify a job name, that job name is set. If no job name is specified, the execution file name is set.

When you define a PC job in a jobnet, the execution file name is set. When you define a Unix job in a jobnet, the script file name is set. If you do not specify a script file name, and then define a job name in a command statement, script_job is set as the job name.

For an action job, the name of the fixed execution file executed by each action job is set as the job name. For an execution file name, the first 63 bytes of the characters from the beginning in the file name, excluding the path information, are set as the job name.

QUEUE

Indicates a queue name (or an agent host name).

STATUS

Shows the job status.

• ROUTING: Being distributed

• SCHEDULED: Waiting for a time

• WAITING: Waiting to be executed

• EXECUTING: Being executed

• HOLDING: Placed on hold

• END: End

EXITCODE

Indicates a job return code. or details about the job return code, see 7.11.3 Checking the return code of a job in the JP1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

ENTRYTIME

Indicates the time of job submittal in the format of YYYY/MM/DD.hh:mm:ss.

STARTTIME

Indicates the job execution start time in the format of YYYY/MM/DD.hh:mm:ss.

ENDTIME

Indicates the job execution end time in the format of YYYY/MM/DD.hh:mm:ss.

DETAILEDSTATUS

Indicates detailed information about the job. This item is output only when you specify the -di option

• END IN ANOTHER SYSTEM: Ended by another system (detail information not acquired)

• WAITING: Waiting to be executed

• HOLDING: Placed on hold

• SCHEDULED: Waiting for a time

• ROUTING: Being routed

• EXECUTING: Being executed

• NORMAL END: Ended normally^#1

• WARNING END: Ended with warning^#1

• ABNORMAL END: Ended abnormally^#1

• EXECUTION TIMED OUT: Ended with the abortion of execution

• CANCELED END: Canceled (cancel request given before start of execution)

• FORCIBLY TERMINATED: Killed (cancel request given after start of execution)

• FAILURE WHILE STARTING EXECUTION: Failure during starting execution

• FAILURE WHILE ENDING EXECUTION: Failure during ending execution^#2

#1

If you set an end judgment in a job created in a jobnet, the end status is based on the judgment method.

For the jpqjobsub command, you cannot set an end judgment in a job. Therefore, the warning threshold value and the abnormal threshold value are 0. The detailed job information indicates a normal end when the job ends with an return code of 0. However, if the job ends with a value other than 0, then an abnormal end occurred.

#2

This status might occur if an error occurs during the end processing after the execution of a job process or the exchange of end information between the agent host and the manager host, after the job has ended. For details about the error, check the applicable message KAVUxxxx output in the integrated trace log.

For the job executed by the agent host, the process itself is ended. To check the end status of the process, check the execution history of job processes or other resources.

CHARCODE

Indicates the character set used by the agent that has executed the job. This item is output only when you specify the -cc option

• ASCII: ASCII

• SJIS: Shift JIS

• JP_EUC: EUC

• UTF-8: UTF-8

If the job execution is not ended or if the job is executed by another system:

• UNKNOWN: Unknown character set

AGENTNAME

Indicates the name of the agent host where the job is executed. This item is output only when you specify the -ea option

If the agent host name cannot be obtained, "AGENTNAME : " is displayed.

Note that the YYYY/MM/DD.hh:mm:ss part means calendar-year/month/day.hours:minutes:seconds.

To Page Top