When jobs are defined not to carry over with "waiting on dependencies" states, they go into skip status at midnight. This document describes the solution to this problem.
Cisco recommends that you have knowledge of Tidal Enterprise Scheduler (TES) 184.108.40.206 and later.
The information in this document is based on the TES 220.127.116.11 and later.
Refer to Cisco Technical Tips Conventions for more information on document conventions.
Jobs defined not to carry over with "waiting on dependencies" states go into skip status at midnight.
This behavior was a result of a product enhancement in version 5.3.0 (ENH# 12221), which required the job to go into a final state of "skipped" if its dependencies were not met and they did not carry over. This was an alternative to being stuck in a waiting state forever.
The sysval 109 option was added in order to indicate if you should set the status to skipped for all non-carryover jobs with a wait status. sysval_string should be set to Y for skipped (default behavior) or N in order to leave them in there current state. If you want the job transitioned to an alternative state, you can specify that in the integer value for this sysval and it will be honored as long as it is >= to the done status range (for example, >= 100).