In a flexible management environment, you can check the
overall status of jobs, the status of specific job nodes, and the
job history of nodes. You can suspend, resume, or delete jobs on the
Job Status collection page.
Before you begin
Before you can check the job status, you must have registered
at least one node with the job manager and submitted a job for the
node.
To suspend a started job, resume a suspended job, or delete
selected jobs, your ID must be authorized for the operator role.
About this task
After you submit a job using the job manager administrative
console, the Job status collection page is displayed. The page contains
information about only the job that you submitted. The page shows
the unique job ID; for example, 122763380912576341. You can use the
job ID to query, suspend, resume, or delete the job. The page also
shows the job description, state, time of activation, time of expiration,
and status.
If you access the Job status collection page by
selecting in the job manager administrative console navigation,
you can use the Find option to limit the number of jobs that are displayed
based on the criteria you specify. The first time you access the Job
status collection, no jobs are listed. You must enter parameters for
the Find option to obtain a list of jobs based on the parameter information
that you provide. The next time you select , a list of jobs is displayed
based on the parameters you last specified on the Find option for
this job manager administrative console page. You can then optionally
modify the Find option criteria to display a different set of jobs.
After at least one job displays, you can check the status of the displayed
jobs, the status of specific job nodes, and the job history for nodes
of a particular job.
This topic describes how to use the job
manager console to check job status. Instead of using the console,
you can run a getJobTargetStatus wsadmin command; for example:
AdminTask.getJobTargetStatus('[-jobToken 122763380912576341]')
The
job token is the job ID for the submitted job. Run the Jython script
command from the
bin directory of the job manager
profile. For more information, see the AdministrativeJobs command
group for the AdminTask object topic.
Procedure
- Optionally use the Find option to display a set of jobs.
If no jobs are displayed, you must use the Find option to
display jobs based on the parameter information that you enter.
- Click in the job manager console.
- For the parameters on which you want to do a Find operation,
specify an operator and a text string.
- Click Find.
The list of jobs along with their status information are
in the collection table.
- Check the status of a job at its nodes.
- Select in the console to access the Job status collection
page if you did not get to the page as a result of a job submission.
- Select either a job from the Job ID column or a number
on the graph in the Status Summary column for a particular job.
The graph is divided in up to four sections, indicating success,
partial success, failure, or other, in that order, of the nodes in
the job.
- Click the status refresh icon
to refresh the displayed status.
- Optionally use the Find option to display the status
of specific job nodes based on the parameter information that you
enter.
- To run the Find operation on specific parameters, specify an operator
and a text string as appropriate.
- Click Find.
A list of nodes for the job, along with the status for each
node, are displayed on the Job status settings page.
- Check the job history of nodes.
- Select in the job manager console to access the Job status
collection page if you did not get to the page as a result of a job
submission.
- Select either a job from the Job ID column or a number
on the graph in the Status Summary column for a particular job.
The graph is divided in up to four sections, indicating success,
partial success, failure, or other, in that order, of the nodes in
the job.
- On the Job status detail page, click a node name link
in the Status column.
The Job status history page is
displayed, showing a history of the job processing on a managed node.
A typical job history is for the status to progress from Distributed
to In progress to Succeeded. Table 1 describes the job status values.
Table 1. Job status descriptions. The status indicates whether the job completed successfully.
Job status |
Description |
Not attempted |
The node has not received the job. The status
is NOT_ATTEMPTED. |
Distributed |
The node has received the job. The status is
DISTRIBUTED. |
In progress |
The node is running the job concurrently with
other jobs. The status is ASYNC_IN_PROGRESS. |
Failed |
The job failed and is no longer running. The
status is FAILED. |
Rejected |
The node rejected the job because, for example,
the node does not support the job type. The status is REJECTED. |
Succeeded |
Job completed successfully. The status is SUCCEEDED. |
Partially succeeded |
Applies only to startCluster and stopCluster
jobs where the cluster has multiple cluster members and to startApplication
and stopApplication jobs where the application is installed on multiple
targets. If only some cluster members are started or stopped or the
application does not start on all application targets, the status
of the job is PARTIALLY_SUCCEEDED. |
- Click the status refresh icon
to refresh the displayed status.
Refresh the job status until the status is Failed, Rejected,
or Succeeded.
- Optionally use the Find option to display job history
based on the parameter information that you enter.
- To run the Find operation on specific parameters, specify an operator
and a text string as appropriate.
- Click Find.
The status of the job for the node is displayed
on the Job status history page.
- Suspend a job.
- Select in the job manager console to access the Job status
collection page if you did not get to the page as a result of a job
submission.
- Select the check box next to a job with an active or
pending state.
- Click Suspend.
- Resume a job.
- Select in the job manager console to access the Job status
collection page if you did not get to the page as a result of a job
submission.
- Select the check box next to a job whose state is Suspended.
- Click Resume.
- Delete a job.
By default, submitted jobs
remain active for one day (24 hours). An active job is a running Java
process that consumes machine resources. Delete jobs that you no longer
need. You can use the job manager console Job status page.
- Select in the job manager console to access the Job status
collection page if you did not get to the page as a result of a job
submission.
- Select the check box next to the job that you want to
delete.
- Click Delete.
Results
You might have run a Find operation to display job status
based on criteria that you specify, checked the status of jobs at
their nodes, checked the jobs history of nodes, suspended a job, resumed
a job, or deleted a job.
What to do next
You can continue to check job status and do other job
management tasks such as submit other jobs, create node groups for
job submission, view node resources, or view nodes.