Checking job status

In a flexible management environment, we can check the overall status of jobs, the status of specific job targets, and the job history of targets. We can suspend, resume, or delete jobs on the Job status collection page.

Before we can check the job status, you must have registered at least one target with the job manager and submitted a job for the target.

To suspend a started job, resume a suspended job, or delete selected jobs, the ID must be authorized for the operator role.

After you submit a job using the job manager console or the deployment manager 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. We 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 we access the Job status collection page by selecting Jobs > Status in an console navigation, we can use the Find option to limit the number of jobs that are displayed based on the criteria specified. The first time you access the Job status collection page, no jobs are listed. We 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 Jobs > Status, a list of jobs is displayed based on the parameters you last specified on the Find option for this job manager console page. We can then optionally modify the Find option criteria to display a different set of jobs. After at least one job displays, we can check the status of the displayed jobs, the status of specific job targets, and the job history for targets of a particular job.

This topic describes how to use the job manager console to check job status. Instead of using the console, we 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 (AdminTask) topic.

• Optionally use the Find option to display a set of jobs.

  If no jobs are displayed, use the Find option to display jobs based on the parameter information that you enter.

  1. Click Jobs > Status in the job manager console.

  2. For the parameters on which to do a Find operation, specify an operator and a text string.

  3. Click Find.

  The list of jobs along with their status information are in the collection table.

• Check the status of a job at its targets.

  1. Select Jobs > Status 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.

  2. 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 targets in the job.

  3. Click the status refresh icon

     

     to refresh the displayed status.

  4. Optionally use the Find option to display the status of specific job targets based on the parameter information that you enter.

     1. To run the Find operation on specific parameters, specify an operator and a text string as appropriate.

     2. Click Find.
  A list of targets for the job, along with the status for each target, are displayed on the Job status settings page.

• Check the job history of targets.

  1. Select Jobs > Status 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.

  2. 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 targets in the job.

  3. On the Job status settings page, click a target name link in the Status column.

     The Job status history page is displayed, showing a history of the job processing on a managed target. A typical job history is for the status to progress from Distributed to In progress to Succeeded. Table 1 describes the job status values.

     Job status	Description
     Not attempted	The target has not received the job. The status is NOT_ATTEMPTED.
     Distributed	The target has received the job. The status is DISTRIBUTED.
     In progress	The target 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 target rejected the job because, for example, the target 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.

  4. Click the status refresh icon

     

     to refresh the displayed status.

     Refresh the job status until the status is Failed, Rejected, or Succeeded.

  5. Click an output file name to view the contents of a file that provides information about the job processing.

     Not all jobs produce output files.

  6. Optionally use the Find option to display job history based on the parameter information that you enter.

     1. To run the Find operation on specific parameters, specify an operator and a text string as appropriate.

     2. Click Find.
     The status of the job for the target is displayed on the Job status history page.

• Suspend a job.

  1. Select Jobs > Status 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.

  2. Select the check box next to a job with an active or pending state.

  3. Click Suspend.

• Resume a job.

  1. Select Jobs > Status 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.

  2. Select the check box next to a job whose state is Suspended.

  3. 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. We can use the job manager console Job status page.

  1. Select Jobs > Status 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.

  2. Select the check box next to the job to delete.

  3. Click Delete.

Results

We might have run a Find operation to display job status based on criteria specified, checked the status of jobs at their targets, checked the jobs history of targets, suspended a job, resumed a job, or deleted a job.

What to do next

We can continue to check job status and do other job management tasks such as submit other jobs, create target groups for job submission, view target resources, or view targets.

Subtopics

• Job status collection
  Use this page to display information about submitted jobs, including the job ID, description, state, activation time, expiration time, and status summary. Jobs are submitted to administer targets that have been registered with the job manager.

Related concepts

Job manager

Related tasks

Set up a job manager environment

Administer nodes remotely using the job manager

Administrative roles

Job status settings

Job status history collection

AdministrativeJobs (AdminTask)