Job Details (Thick Client)

As an AAI operator or jobstream administrator, when monitoring and working with a jobstream, you may want to drill down into its jobs to investigate what job properties or run parameters might be affecting its execution. This is particularly true if a job fails or if it runs for much longer than normally does.

This topic explains how to access the job details and describes them:

Accessing the Job Details

You can access the job details from the following places:

  • Gantt chart view, by right-clicking a job and selecting Job Details. Alternatively, select a job and then select the job details button in the toolbar. For more information, see the Job Details Dialog section below.

  • By performing a search for jobs from the Tools menu. F

Job Details Dialog

The Job Details dialog displays the properties of the selected job. If no job or box (group) is selected, the fields are empty. The properties are displayed for the selected job on a per jobstream basis, so, if you change the jobstream you are viewing, the contents of the Job Details dialog also change based on what is selected in the current tab. Depending on the selected job, the details are displayed in two or more tabs.

Properties Tab

The Properties tab is displayed for all jobs and shows details for the selected job based on the job definition in the scheduler, independent of any particular run.

Note:

When viewing a historical run, the information on the Properties tab reflects the latest job definition, and may not match the definition that was in place when the run occurred.

The Properties tab is divided into three expandable/collapsible sections:

  1. Common shows properties that are common to all scheduler jobs, regardless of the type of job being displayed. These properties are defined within the scheduler and simply displayed within AAI.

  2. The second section is specific to the type of job being displayed. For example, if an FTP job is being displayed, properties such as FTP Host Name, FTP User, and FTP Password are displayed.

    For AutoSys, the Job Properties are essentially the same attributes you would see when performing an autorep –J [jobname].

  3. AAI contains all of the properties that are created and maintained within AAI only. These properties do not exist within the underlying job scheduler.

Run(s) Tab

The Run(s) tab is displayed for all jobs and shows properties related to the specific run(s) of the job that you are viewing.

In the event that there are multiple runs for the job in the jobstream run, the runs will be displayed side by side. For example, if there were two failures and one success, you would see each run displayed side by side in the Runs tab.

  • Critical Path: Indicates if the selected job was in the Critical Path of this particular run.

  • Retrys: Usually 1, this value indicates when a job has been restarted more than once due to failures or other unusual conditions.

  • Start Time: When the job or box (group) started.

  • Running Time: When the job entered Running status. Note: boxes (groups) will not have a Running Time value.

  • End Time: When the job or box (group) completed.

  • Duration: The length of time that the job was running.

  • Finish to Start Delay: This statistic (in HH:MM:SS format) reflects the time that passed after the jobs’ last predecessor finished and before the job started. This is included in System Delay for the jobstream as a whole. The time when job is on-hold is captured and represented in finish-to-start delay, not operational delay.

  • Start to Running Delay: This statistic (in HH:MM:SS format) reflects the difference between the Start Time and the Running Time for the selected job. This is also included in System Delay for the jobstream.

  • Designed Delay: This statistic (in HH:MM:SS format), captured only in Automic Automation Intelligence, can reflect delays in the jobstream that are not caused by system delays, but rather are a function of how a job has been defined to the scheduler. As an example, if a job is in a box (group), and the scheduler has a start time of 11:00 p.m., the job inside of that box (group) would normally start immediately after the job starts. However, if the job inside the scheduler has a hard start time of 12:00 a.m., then there is a delay of 1 hour before the job inside the box (group) starts, caused by the definition of the job. AAI reports such a time difference as Designed Delay.

  • Operational Delay: This statistic (in HH:MM:SS format), captured only in Automic Automation Intelligence, reflects delays that are neither caused by the system, nor are designed into the job definition. Rather, it reflects a delay that is most likely due to an operator, or human delay. As an example, let’s say that a job fails at 1:00 a.m., and it has no restarts defined in the scheduler. An operator notices that the job has failed and manually intervenes to re-start the job at 1:10 a.m. The 10 minutes between the failure of the first run of that job and the initiation of the second run of the same job in the same run of the jobstream will be reflected as Operational Delay.

  • Resource Delay: This statistic (in HH:MM:SS format) reflects the amount of time a job waited for a resource to become available before running. Unexpected Delay: This statistic (in HH:MM:SS format) reflects the amount of time where the run could have started but did not. For example, if all resources were available and all other dependencies were satisfied, then any additional delay is accounted for here. Another case in which it is calculated is if the Finish to Start Delay exceeds the value set in the parameter tidal.unaccountedDelayThresholdDuration then the Finish to Start Delay is not populated and, instead, the Unexpected Delay is populated.

  • Exit Code: Exit code of the scheduler job.

  • Run Status: Last known job status: Success, Failure, Terminated, and so on.

  • Run Machine: The machine that the job actually ran on.

  • Entry Mode: Manner in which the job was started. The following values are possible:

    AutoSys

    • FORCE_STARTED

    • BYPASS

    • FS_PRED

    CA7

    • DEMD

    • AUTO // triggered

    • SSCN // schedule scan

    • EXTL // external

    • RPET // repeat

    • DTRG // DATASET_TRIGGER

    • JTRG // JOB_TRIGGER

    • NTRG // NETWORK_TRIGGER

    • PSCH // PERSONAL_SCHEDULING

    • RUN

    IWSd

    • RERUNSUCC // rerun successors in the same job stream

    • RERUNSUCC_ALL // rerun all successors

    Universal Schedulers

    • TRIGGERED

    • SCHEDULED

    • ADHOC

    • CHANGE_STATUS

  • Predicted Run Status: Status of the predicted run. At this time, all job runs are predicted to complete with a status of SUCCESS.

  • Run Status: For an in-progress job run, the current status of the job. For a completed job run, the final status of the job run.

  • Run Agent: Name of the machine the job executed on.

  • Run ID: Unique identifier of the job run (scheduler-specific format).

  • Generation Number: Generation number of the application as it was executed in ESP.

  • Wired to Target Job:

    • Yes means that the job run is considered to be upstream of the target job run.

    • No means that the job run ran during the time frame of the jobstream run, but is not considered to be upstream of the target job run.

Tip:

You can use the Job Details dialog together with navigation to easily spot differences between jobs as you navigate upstream and downstream. Open the Job Details dialog and the information will change as you navigate upstream and/or downstream.

Conditions Tab

The Conditions tab is displayed only for universal jobs (from universal schedulers) that have at least one condition . Jobs can have status, dependency, date and time conditions that determine when and how they run. If the job has no conditions, this tab is not displayed. The Conditions tab shows the following information:

  • Job Status Conditions: Status that the job must have so that it can start

  • Job Dependencies: Predecessor jobs that must start/end so that this job can start

  • Date Time Conditions: Date and time on which the job can start

  • Time Conditions: Time on which the job can start

  • Recurring Time Conditions: Recurring times that job is scheduled to run, for example every five minutes

JCL Tab

The JCL tab is displayed only for CA7 CPU jobs and shows the LOADed STEP and DD information from CA7 for the selected CPU job.

Schedules Tab

The Schedules tab is displayed only for CA7 CPU jobs and shows all of the DATE/TIME schedules that apply to the selected CPU job in view.

Job Details - Job Properties Table

When you make a search for jobs using the Tools > Job Search function in the menu bar, AAI displays the result of your search in a table on the Job Search dialog. The columns in this table provide comprehensive data about the properties of the found jobs.

For more information, see Searching for Jobs (Thick Client).

See also: