Job Tracker

The Job Tracker tool allows you to view the history of jobs that have run in the past and jobs that are currently running. The tool allows you to view the runtime log history for jobs that the user is interested in seeing. Perform the following steps to track the jobs you are interested in:

1. Choose the Job Search Filter options you are interested in.
2. Search the job(s) of interest, using a pattern name search, including Partition(s) and JobGroup(s) of interest.
3. Once the search results have returned, they will be listed in the drop down list. Using the drop down list, select All Listed Jobs or select only one of the jobs of interest from the drop down list.
4. Specify a time range that you are interested in.
5. Click the Search button to find all the job runs that match the above criteria.

Job Search Filter

The Status Filter allows you to filter for jobs that have certain runtime conditions. You can search for jobs that have one or more of the following conditions:

• Successful: Job has thrown no errors or warnings
• Error: Job has logged at least one error message or has failed
• Warning: Job has logged at least one warning message
• Terminated: Job was ungracefully terminated before finishing (probably due to the JobServer being stopped abruptly)
• Expired: Job never had a chance to run because its schedule window had passed so it became "expired"

In addition to the conditions above you can also specify to view jobs that are still running. This will return any job that is running. The Job Search Filter criteria is ignored in this case.

Search Pattern

Search for the jobs that you are interested in. You can search by job name or by job ID. The pattern "*" is used as a wild card. If you enter "*" then all jobs within the JobGroup and Partition specified will be returned. For example, "foo*" will return any job that starts with the name "foo". If you enter a number, then it will try to find a job with the exact job ID. Once you execute the search (hit the "Enter" key), the results will be placed in the drop down list below it, showing all jobs that match the search criteria.

Results Matching Search Pattern

If the search pattern finds matching jobs, they will be in the drop down list. If you choose "All Listed Jobs", then all the jobs in the drop down list will be searched for, otherwise only one single job will be searched for

Paging Size

The "Paging Size" value allows you to limit how many jobs are shown at once on the screen. You will be able to page backwards and forwards through the entire list as defined by the paging size. For example, if your search result returns 1000 matches and your paging size is 200, then you will need to page 5 times to get to the end of the list.

Specify Time Range

Now specify what time range you want to search within. This will search for jobs that started running between the start and end dates specified.

Search

If there are jobs that are running or have run in the past that match the criteria specified, they will be displayed. You can drill down and view more details by clicking on the RunID in the first column. This will allow you to view the job's logging information all the way down to each individual TaskBean. If the job had multiple TaskBeans each one will have an entry.

Display Fields

By default you will see the following fields for each job run:

• RunID: Every job has a unique id when it runs. Clicking on this, will bring up a new window that shows the details of the TaskBean(s) that ran in the job. Clicking on the run id of the TaskBean will display any detailed messages logged by the TaskBean.
• Job Name: Name of the job. If the job's name is too long the end will be cut off. You can still see the full name as a tooltip by holding the cursor over the job name.
• Started: The exact time the job was executed by the scheduling engine (or launched manually by the user)
• Completed: Time job completed processing.
• Status: Status of job can be running, terminated, completed (with or without errors), for failure. If failure, the failure will often have a tooltip detailing the failure reason message.
• Exit Condition: NA (typically means job is still running), normal, exit request (job threw a job exit condition), failure/exit job (job through failure exception), killed by user, and internal error.
• Error: This will be marked if there have been any errors logged by the job or a failure of any kind has occurred.
• Warn: This will be marked if there have been any warnings logged by the job.

You can select additional fields to display by using the "Set Display Fields" button. You can add the following fields:

• JobID: Unique ID assigned to the job.
• Username: Name of user if job was launched manually.
• Schedule Date: The actual scheduled date the job should have run at. Normally same as start date but can be different in some cases.
• Queue Date: When the job got queued. Normally equal to start date but does not have to be, especially if the system is very busy.
• Execution Date: When the job actually started processing and TaskBeans began executing withing the Partition.
• Start Mode: Whether the job was scheduled, manually forced, or expired before running.
• Partition: The Processing Partition the job ran under.