Tidal Enterprise Scheduler: Ordered Agent List Does Not Always Run Jobs on the First Agent

Available Languages

Download Options

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

Updated:February 21, 2012

Document ID:113409

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

This document describes the solution when the ordered agent list does not always run jobs on the first agent.

Prerequisites

Requirements

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

Components Used

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

Conventions

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

Problem

The ordered agent list does not always run jobs on the first agent.

Reason

Build 5.3.1.182 of the Master added a check of the agent's job limit in order to determine if an agent was available for selection from an agent list.

Solution

Added new sysval ID 114. Set to (N) in order to ignore the agent job limit when selecting an agent from an ordered agent list. The default is (Y), which means if the agent has reached its job limit, it will check the next agent in the ordered list.