Tidal Enterprise Scheduler: Jobs Defined Not to Carry over with "waiting on dependencies" States Go into Skip Status at Midnight

Available Languages

Download Options

PDF (5.8 KB)
View with Adobe Reader on a variety of devices

Updated:February 21, 2012

Document ID:113407

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Introduction

Prerequisites

Requirements

Components Used

Conventions

Problem

Reason

Solution

Related Information

Introduction

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.

Prerequisites

Requirements

Cisco recommends that you have knowledge of Tidal Enterprise Scheduler (TES) 5.3.1.144 and later.

Components Used

The information in this document is based on the TES 5.3.1.144 and later.

Conventions

Refer to Cisco Technical Tips Conventions for more information on document conventions.

Problem

Jobs defined not to carry over with "waiting on dependencies" states go into skip status at midnight.

Reason

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.

Solution

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).