Dependencies are prerequisites that must be completed before a scheduled Job or Setup can execute. A single Job or Setup can have an unlimited number of Dependencies and a JAMS Job can serve as a Dependency for any other Job regardless of where or how the Job runs.
JAMS supports the following types of Dependencies:
- Job Completion
- Setup Completion
- Variable Value
- File Availability
- Remote Job Completion
- Remote Setup Completion
When adding a new Dependency (see the topic: Working with Dependencies) JAMS uses a wizard to step through the definition process. Based on the selected Dependency Type, the wizard displays different properties described below.
Depends on Job
Use the adjacent file browser button to select the name of the dependent Job. The defined Depends on Job must have completed since the last time the (current) Job ran.
Minimum Completion Severity
The Depends on Job must complete with a severity level that is equal to or less severe than the chosen minimum value.
Since the last time this Job ran
Select the file browser button next to the Since the last time this job ran property. Double-clicking a Job from the list populates this property.
Typically, the selected Job for this property is used as a reference to determine if the previously defined Depends on Job has actually completed.
 |
Note: If this property is left blank, the Or, within the last property can be used to determine if the dependency has been satisfied. |
Minimum Completion Severity
This optional property evaluates to the Since Job instead of the Depends on Job. In this case, the Since Job must complete with a severity level that is equal to or less severe than the chosen minimum value.
Or, within the last
The property is used to define a time range dependency, based on the number of days, hours, minutes and seconds [e.g., 1.2:30 =26.5 hours; or 2.10 =2 days + 10 hours).
An example of a time-based dependency might be where you have one update Job and a number of reporting Jobs. If update Job runs at the end of every month, followed by the reporting jobs, you could define a dependency for each reporting Job requiring that each update Job be completed within the previous 28 days.
Note: If both the Or within the last and the Since the last time this Job ran properties are blank, the current Job, when submitted, waits in the queue until the Depends on Job completes with a satisfactory status.
Wait for all instances of the Job to complete?
If this property is enabled, JAMS checks if the Depends on Job is scheduled or executing. If one or more of the Depends on Jobs are found, the current Job remains in a pending state until all occurrences of the Depends on Job have completed.
Depends on Setup
Use the adjacent file browser button to select the name of the dependent Setup. The defined Depends on Job must have completed since the last time the (current) Job ran.
Minimum Completion Severity
The Depends on Job must complete with a severity level that is equal to or less severe than the chosen minimum value. For Setup Dependencies, the choice is either Success or Failure.
Since the last time this Job ran
Select the file browser button next to the Since the last time this job ran property. Double-clicking a Job from the list populates this property.
Typically, the selected Job for this property is used as a reference to determine if the previously defined, Depends on Setup has actually completed.
Or, within the last
Enter a time range dependency (number of days, hours, minutes and seconds [e.g., 1.2:30 or 26.5 hours; or 2.10 or 2 days + 10 hours).
|
Note: If both the Or within the last and the Since the last time this Job ran properties are blank, the current Job, when submitted, waits in the queue until the Depends on Setup completes with a satisfactory status. |
Minimum Completion Severity
This optional property evaluates to the Since Job instead of the Depends on Setup. In this case, the Since Job must complete with a severity level that is equal to or less severe than the chosen minimum value.
Wait for all instances of the Setup to complete?
If this property is enabled, JAMS checks if the Depends on Setup is scheduled or executing. If one or more of the Depends on Setups are found, the current Job remains in a pending state until all occurrences of the Depends on Setups have completed.
Variable Dependencies are based on the condition and comparison value of a defined variable. These dependencies have the following properties:
Select Variable
This is the name of the JAMS variable on which the current Job depends.
Which Must Be: Comparison Operator and Compare to Value.
These two properties contains a condition and comparison value.
The first property is a dropdown list allowing you to select a Boolean operator or code that defines how the comparison is performed.
The Compare To Value is the value in which the Variable is compared.
File Dependencies include the following properties:
Depends on File
Use the adjacent file browser button to select the name of the dependent file. The chosen file must meet the specified criteria before the current Job can begin.
|
Note: In JAMS v5.3 and later a JAMS Parameter or Variable can also be specified for this property. |
The standard Parameter or Variable declaration can be used, for example,
<<VariableName>> or C:\<ParameterName>>\*.txt.
The file must be
The Depends on File must be either: Available, Present, or Absent in order for the current Job to start.
Minimum File Size
Specify the minimum required file size for the Job to start. If the file does not currently meet the required size then the current Job waits until the file becomes large enough (measured in bytes).
Agent node
This property determines which Agent node can request the file. This optional property if left blank is checked by the JAMS Scheduler.
Username
This property determines which Username is used to check the file. If it is left blank the Username selected for the current Job becomes the default.
Remote Job Dependencies pertain to Jobs running on another JAMS Scheduler. To define a remote Job dependency use the following properties.
JAMS Server
Use the dropdown to select the remote node where the Depends on Job runs.
Depends on Job
Enter the name of the dependent Job. This Job must have completed since the last time the (current) Job ran or within the time range as specified in the Since Job property.
|
Note: Since this Job resides on the remote node it is not validated during entry. |
Minimum Completion Severity
The Depends on Job must complete with a severity level that is equal to or less severe than the chosen minimum value.
Since the last time this job ran
Select the file browser button next to the Since the last time this job ran property. Double-clicking a Job from the list populates this property.
Typically, the selected Job for this property is used as a reference to determine if the previously defined Depends on Job has actually completed.
|
Note: If this property is left blank, the Or, within the last property can be used to determine if the dependency has been satisfied. |
Or, within the last
This property is used to define a time range dependency, based on the number of days, hours, minutes and seconds [e.g., 1.2:30 =26.5 hours; or 2.10 =2 days + 10 hours).
An example of a time-based dependency might be where you have one update Job and a number of reporting Jobs. If update Job runs at the end of every month, followed by the reporting jobs, you could define a dependency for each reporting Job requiring that each update Job be completed within the previous 28 days.
Note: If both the Or within the last and the Since the last time this Job ran properties are blank, the current Job, when submitted, waits in the queue until the Depends on Job completes with a satisfactory status.
Minimum Completion Severity
This optional property evaluates to the Since Job instead of the Depends on Job. In this case, the Since Job must complete with a severity level that is equal to or less severe than the chosen minimum value.
Wait for all instances of the Job to Complete?
If this property is enabled, JAMS checks to see if the Depends on Job is scheduled or executing. If one or more of the Depends on Jobs are found, the current Job remains in a pending state until all occurrences of the Depends on Job have completed.
Remote Setup Dependencies pertain to Setups running on another JAMS Scheduler. To define a remote Setup dependency use the following properties.
JAMS Server
Use the dropdown to select the remote node where the Depends on Setup runs.
Depends on Setup
Enter the name of the dependent Setup. This Setup must have completed since the last time the (current) Job ran or within the time range as specified in the Since Job property.
|
Note: Since this Setup resides on the remote node it is not validated during entry. |
Minimum Completion Severity
The Depends on Job must complete with a severity level that is equal to or less severe than the chosen minimum value. For Remote Setup Dependencies, the choice is either Success or Failure.
Since the last time this Job ran
Select the file browser button next to the Since the last time this job ran property. Double-clicking a Job from the list populates this property.
Typically, the selected Job for this property is used as a reference to determine if the previously defined Depends on Setup has actually completed.
|
Note: If this property is left blank, the Or, within the last property can be used to determine if the dependency has been satisfied. |
Or, within the last
This property is used to define a time range dependency, based on the number of days, hours, minutes and seconds [e.g., 1.2:30 =26.5 hours; or 2.10 =2 days + 10 hours).
|
Note: If both the Or within the last and the Since the last time this Job ran properties are unpopulated, the current Job, when submitted, waits in the queue until the Depends on Setup completes with a satisfactory status. |
Minimum Completion Severity
This optional property evaluates to the Since Job instead of the Depends on Setup. In this case, the Since Job must complete with a severity level that is equal to or less severe than the chosen minimum value.
Wait for all instances of the Setup to complete?
If this property is enabled, JAMS checks to see if the Depends on Setup is scheduled or executing. If one or more of the Depends on Setups are found, the current Job remains in a pending state until all occurrences of the Depends on Job have completed.