Monitoring and Controlling Jobs › Reset Time Dependencies

Reset Time Dependencies

Before the job runs, you can use the Reset Times command to display, remove, change, or add time dependencies for the current run.

To reset time dependencies

1. Right-click the job in the Monitor perspective.

   A list of job commands appears.

2. Select Reset Times.

   The Reset Times dialog opens.

3. Add or modify the date or time in the following fields:

   Do not submit before

   Specifies the job's submission time. The submission of the job is delayed until this time.

   Overdue if not started by

   Specifies the latest acceptable time by which the job must start before it is considered overdue (late start time).

   Note: If the job is currently overdue because it is late starting, you cannot reset the late start time.

   Overdue if not completed by

   Specifies the time by which a job should complete successfully before it is considered overdue (late completion time).

   Note: If the job is currently overdue because it is late completing or has exceeded its maximum execution time, you cannot reset the late completion time.

   Abandon predecessor dependencies at

   Submits a job without its predecessor dependencies once it meets a specified time.

   Note: This field does not override a manual hold or submission time dependency.

   Abandon submission at

   Specifies the latest time this job can be submitted. If the job is not submitted by this time, it is bypassed.

   Abandon resources at

   Specifies the time at which you no longer want the job to wait for its resource dependencies.

   Abandon variables at

   Specifies the time at which you no longer want the job to wait for its variable dependencies.

   Overdue if execution time exceeds

   Specifies the maximum acceptable execution time in minutes. If the job exceeds this elapsed execution time, it is considered overdue.

   Note: If the job is currently overdue because it is late completing or has exceeded its maximum execution time, you cannot reset the maximum execution time.

   Premature if execution time is less than

   Specifies the minimum acceptable execution time in minutes. If the job completes before this elapsed execution time, it is considered premend (premature end).

   Reason

   (Optional) Specifies the command reason.

   Limit: 1024 characters (including the timestamp and the user name)

   Note: We recommend that the reason text not exceed 250 characters. The number of commands displayed in the command log is limited to the size of the command log buffer, which is 1024 characters. For example, if the reason text averages 10 characters per command, the command log displays up to 50 commands; if the reason text averages 250 characters per command, the command log displays up to 4 commands.

4. Click OK.

   The server resets the job's time dependencies.

More information:

Time Dependencies

Overdue Jobs Monitoring