Job Details - Related Jobs and Jobstreams

The Related Jobs and Jobstreams tab provides exhaustive information about the context in which the job runs, its predecessors, successors and, if applicable, about the container where it runs. You can find this information in the Gantt chart view too; there, you see the context in the incoming and outgoing lines and in the boxes that indicate containers (for example, boxes in AutoSys or Workflows in Automic Automation). On this tab you can see all job dependencies at a glance. The predecessor, successors and children that are displayed on this tab are links that open the details of those jobs, which lets you easily navigate though the structure of your jobstreams and the dependencies of your jobs. This is particularly useful when you discover that a job is trending longer because it lets you find very quickly all the jobs and jobstreams that are affected by it.

This list describes the fields on the Related Jobs and Jobstreams tab: AutoSys AAI

• Parentage

  Fully qualified path from the root object all the way down to a particular job. It lets you uniquely identify the job. This information is extremely important for schedulers that allow jobs to run more than once in multiple contexts (from different places and in multiple jobstreams). The parentage identifies the exact instance of the job. IWS, ESP, Tidal and Automic Automation allow jobs to run multiple times in different contexts. AutoSys does not allow this, therefore, in AutoSys parent and parentage are always the same.

  The last job in this path is a link that opens the parent of the job. (The parent of a job in a jobstream is the container object where that job runs. For example, the parent of a job in AutoSys is called a BOX; in Automic Automation it could be a Workflow or a Schedule. Not all schedulers use this type of container job, so this parameter is available only for schedulers where the container concept applies.).

  Important !

  If the jobstream has been manipulated (for example, by using the trimming feature or the start job option), it can happen that it is not possible to display the entire path up to the root of the job schedule. For more information, see Trimming Jobstreams and Start Jobs in Jobstreams.

• Predecessor Jobs

  Previous job(s) in the jobstream that need to run before the current job runs. In the Gantt chart view they are identified by the incoming lines.

• Successor Jobs

  Job(s) that follow the current job in the jobstream. In the Gantt chart view they are identified by the outgoing lines.

• Children Jobs

  In schedulers that have containers (such as boxes in AutoSys or Workflows in Automic Automation), children are the jobs that run within those containers.

• PART OF THE JOBSTREAMS

  This table contains the list of jobstreams that this job is present in. This information is very useful in various situations:

  • It lets you discover situations where you might be covering one application in more than one jobstream. Usually you do not want to have overlaps of this kind, since it means that you get duplicate alerts from two (or more) different places when the job fails.

    Note:

    Although it is a best practice not to have jobs in multiple jobstreams, there are situations in which you will definitely need it. For example, a job runs twice a day, once in the morning and then later again in the evening for two different shifts in your company. In this case there can be two jobstreams, one in the morning and another one in the evening.

  • You are looking at some trending information and discover that a job is growing. This table tells you the jobstreams that are affected by this job.