Viewing and Verifying Task Status

Each production job consists of several individual tasks that work together to generate job output. In addition to job status, eaDirect assigns a status to the individual tasks that run when the job runs. You can closely monitor and manage the task status for a job instance using the Command Center Task Status page.

Every configured task must complete successfully before eaDirect sets job status to Done on the Main Console.

If any of the production tasks is unable to complete, the job fails, and the status changes to Failed. eaDirect displays all failed jobs in red on the Main Console. If a job fails, you can run it again.

To view task status detail for a job:

· Click the status of the job in the Main Console Status column. The Task Status screen appears showing the status of each production task in the job.

To change the display order of tasks (processing order remains unchanged), click Task. To change the display order of information in the Last Run and Status columns, click Last Run or Status. Click the links again to restore each display to its original order.

Click Refresh to display an updated task status.

You have the option of rerunning or canceling a failed job. Click Retry Failed Job, or Cancel Failed Job.

The Task Status page displays each instance of a job started during the most recent scheduled run in reverse chronological order (youngest first), along with the status of each task in the instance.

The Task Status page identifies each job instance by a Job Instance ID, and displays the following information:

Command Center Task Status Page
Column	Description
Job Instance ID	A number uniquely identifying each job instance.
Last Updated	The time the task status last updated.
Status	Current execution state of the task. Task Status can be: Processing, Failed, Reprocessing, Reprocess, No operation, Canceled, Not yet started, or Done.
Action	Displays a button that lets you take action on that job instance or on all instances. The Retry button lets you retry that instance; the Retry All button lets you retry all failed instances of the job. The Cancel button lets you cancel that instance; the Cancel All button lets you cancel all failed instances of the job.

Which job instances appear on the Task Status page

The Task Status page displays:

· Up to the last N job instances that have Done, Canceled, or No operation status (where N is the maximum number of concurrent instances allowed for the job), plus

· Any instances in Processing, Failed, Reprocessing, or Reprocess status

If you are not using concurrency (N=1), the Task Status page shows up to five rows of job instances in Done, Canceled, or No operation status, plus any instances in Processing, Failed, Reprocessing, or Reprocess status.

When a scheduled run completes, the completed rows remain in view on the Task Status page until a new schedule begins. At this point, the Task Status page begins displaying the instances generated by the new schedule instead. The only exception is that any instances from the previous schedule still in Processing, Failed, Reprocessing, or Reprocess states remain even if a new schedule has begun. eaDirect removes those instances from the Task Status page once processing is complete, or in the case of a failed instance, once you cancel or retry it successfully.

Schedules can overlap if a second schedule begins before the current run completes. Another scheduled run can begin only if:

· The first run is not using the maximum number of instances (if enough "resource" is available). For example, if the first run has 3 instances in Processing and the maximum allowed is 10, the next run can start up to 7 new instances.

· No job instances in the first are in the Failed state.

Overlapping schedules mean that instances from both schedules could appear on the Task Status page. You can tell from the Last Updated field to which schedule the instance belongs.

The number of rows that appear on the Task Status page at any given time depends on the point of progress of the job plus:

· Whether you have enabled concurrency for the job (if the maximum number of instances specified in the schedule is >1).

· The maximum number of concurrent jobs you allow. This number is also the maximum number of Done, Canceled, or No operation jobs that can appear on the Task Status. If you are not using concurrency, the Task Status shows a maximum of 5 job instances in Done, Canceled, or No operation.

· For jobs that scan for an input file, such as Indexer, the number of input files placed in the input directory.

For jobs that process multiple statements in parallel with the StatementScanner task, such as the Report job, the number of statements to process up to the maximum number of instances.

· Whether the job schedule overlaps due to a long lasting run.

Examples: Number of Task Status rows for the Indexer Job

Concurrency Enabled?	Number of Input Files	Maximum Instances	Number of Rows that Can Appear on the Task Status Page
No	3	1	1, 2, or 3. Each job instance must complete before another can appear. If all have been completed, 3 Done instances will show; by default the Task Status page can show up to 5 completed instances when the job runs sequentially (not concurrently).
Yes	3	10	1, 2, or 3. Three job instances can run concurrently and appear at once on the Task Status screen. (Up to 10 rows could appear at once if the job schedules overlap and more input files subsequently appear in the input directory during the second scheduled run.)
Yes	10	3	1-6. As few as one row with status in Processing or, if processing is complete, 3 rows all in Done status can appear. For example, at some point you could see 6 rows; the first instance might be in Processing, the second, third, and fourth in Done, the fifth in Failed, and the sixth in Processing, with the rest not started and therefore not shown.

Additional ways to verify that a task completed successfully

In addition to checking the individual task status on the Task Status screen, you can check for individual task output to determine whether a task completed successfully, as described here:

Task	How to verify task completion
Scanner	Check the job’s status window. Verify that the data file was moved from the input directory to the data directory and renamed.
Indexer	Check the job status window. Verify the .IR file is in the /Data/Application Name directory.
IXLoader Task	Check the job status window. Verify the appearance of .CTL, .CMD, and .LOG files. Check for Index references (one per primary key) within the index table in database.
AutoIndexVolAccept	Check the job status window.
IVNScanner	Check the job status window.
Mail Notification	Check the job status window. Verify emails sent.
HTMLFormatter	Check the job status window. Verify the appearance of static HTML output files.
XMLFormatter	Check the job status window. Verify the appearance of static XML output.
StatementsToIR	Check the job status window. Verify the .IR file in the /Data/Application Name directory.
DXLoader	Check the job status window. Verify the existence of a populated database table.