Cisco Tidal Enterprise Scheduler 6.2 User Guide

Glossary

 

A
Aborted status	The job occurrence was deliberately aborted and cannot be resumed.
action	An action is a user-defined response to a job or system event. An action can be an email message, an SNMP message (trap), an operator alert, the insertion of a new job, a log update, a variable change or a job control action.
Active status	The job occurrence is actively running in the production schedule.
adapter	A component that integrates one application with another application. An adapter provides connectivity and business logic so two different applications can work together.
agent	Agents are licensed computers with Scheduler installations that are attached to a Scheduler master and are licensed to run jobs for the Scheduler master. Every agent facilitates the execution of scheduled and unscheduled jobs, and relays vital information back to the Master (i.e. workload data, job output, and job status). Scheduler agents provide dynamic rerouting fault tolerance, workload balancing and a central point of schedule maintenance and control. Each agent has a job limit value, and communication port specifications which can be set from the Tidal Web client Connections window.
Agent Disabled status	The agent for the job is disabled, and the job occurrence cannot run. If a job is using an agent list, no agent in the agent list is active. An agent can be changed to enabled by selecting its Enabled property in the Agent Definition dialog.
agent limit	The number of jobs that are allowed to run on an agent, specified in the agent’s definition in Scheduler.
agent list	An collection of agent names which define a group of computers that jobs can run on. Agent lists are used for workload balancing, dynamic rerouting fault tolerance, and for broadcasting.
Agent Unavailable status	The agent is not connected, or is not running, and therefore the job occurrence cannot run on its agent. If the job is using an agent list, this status indicates that all agents in the list are unavailable.
agentd	Agent daemon (service). Handles file transfers and remote connections from master to agents.
audit message	A record of a Scheduler activity, such as:
A user adds, edits or deletes a Scheduler object.	A job is overridden by a user using the Job Details dialog while the job is in the schedule.
Job control is performed by a user or through a manual job control action.	All audit messages, error and diagnostic messages can be displayed from the Logs pane. Alternatively, you can view audit messages from the Job Activity window via the Job Details dialog.
auto arrange	A set of properties in the View Properties dialog that configures the logic used to arrange how objects in a graphical View are displayed.
Available status	The status of a defined resource that indicates it is available for use. Even if a resource needed by a job is available, a job may still not run. That job may require a greater amount of the resource than is currently available or one of the other resources that the job requires is not available. If a resource is not in an Available status, it is in either an Locked status or a Waiting status.

 

B
backup master	A computer licensed to run the Scheduler master software in Fault Tolerance mode. The backup master is available to run master processes if the primary master fails.
batch (.bat) job or file	In Windows, series of commands that are batched (or bunched) together in a single file to run in sequence without further user interaction. The equivalent in Unix is a shell script. In z/OS, an EXEC file serves the batch file function. A batch file ends with a .bat file extension.
Bird’s Eye View	An option in the graphical View to reduce or enlarge selected objects in a graphical View until all of the objects fit in the visible portion of the View window. A selection box with a dotted line boundary displays at the cursor. The size of the selection box varies according to the view magnification being used. Placing the selection box over a portion of the view and clicking, magnifies that area to the original zoom scale.
broadcasting	An agent list function where a job is run on every agent in the list.

C
calendar group	A collection of calendars that is used to specify a set of dates to run jobs. The calendar group includes and/or excludes the dates specified by each individual calendar in the group.
callout	A text balloon associated with one of the objects defined in a graphical View. A callout provides additional information that can consist of text or a hyperlink to an associated website or directory. Callouts are created and configured for individual objects using the Callout Properties dialog.
Canceled status	The job is canceled and cannot be resumed. A job can be canceled before it becomes active while it is in the Waiting On Dependencies or Waiting On Resources statuses. A job that is active cannot be canceled but must be aborted.
Canceled Normally status	The job was previously placed in a Canceled Pending status while the job dependencies were released. Once the job’s dependencies were satisfied, the job goes to a Canceled Normally status. This status is treated by other jobs as a Completed Normally status.
Canceled Pending status	The job is canceled but the job’s dependencies are released so the job stream can be maintained. In essence, the job goes into a Waiting on Dependencies state as the dependencies run. Once all of the job’s dependencies are satisfied, the job ends with a Canceled Normally status that is equivalent to a Completed Normally status. This status only occurs through a user-initiated job control action or a predefined job action.
child agent list	An agent list that belongs to a parent agent list. Child agent lists may also be parent agent lists if they contain other child agent lists. A child agent list must be the same type as its parent, i.e., rotational, workload balanced, ordered, etc.
child job	A job that is a member of a job group. By default, a child job inherits scheduling and run properties from its parent job group. When a parent job group is submitted, all of its qualified child jobs are submitted.
child job group	A job group that is a member of another job group. By default, child job groups inherit scheduling and run properties from their parent job groups. When a parent job group runs, all of its children (jobs and job groups) are run.
child queue	A queue that is a sub-queue of another, called the parent queue. The number of jobs that a child queue can run is constrained either by its own limit setting, or by the job limit setting of its parent, whichever is smaller. Child queues can only accept jobs that have passed through it parent’s queue filter.
command	The executable file that is run by a job. For Windows, commands can be. bat , .cmd , .exe or other executable files and DOS scripts. For Unix, commands can be shell scripts, programs and commands. Commands can include command parameters are passed to the executable file when it runs.
command parameters	The runtime parameters that are passed to a command before Scheduler runs the command.
Completed Abnormally status	The job completed with a non-zero exit code indicating that it did not run normally.
Completed Normally status	The job completed normally. If the status is determined within Scheduler, the exit code is 0. If the status is set by an external program, the exit code may be non-zero.
concurrency	Refers to the situation when more than one occurrence of the same job is running at the same time, regardless of which agent they are running on. For each job, you have the option to Skip , Defer until completion , or Run anyway when an occurrence of the job is already running. The default is Skip .
Connector	The Connector is a component that allows a Windows machine to translate the Unix master's job requests. If you are using a Unix master and you intend to run PeopleSoft, SAP or Oracle Applications jobs, then you must install the Connector. If you are using a Windows master with a Windows adapter than you do not need the Connector.
console alert	A notification to the Scheduler console that a job's pre-defined Job Event has occurred. An alert often indicates that the operator should view the alert message from the Alert Information dialog and take an appropriate action.
cqd	The communications queue daemon is responsible for network communication between the different modules of Scheduler and between multiple Scheduler masters and agents.
create schedule	Create Schedule compiles all the jobs that are scheduled to run and creates a production schedule. Schedule creations are incremental, that is, only jobs that were not previously added through a schedule creation, are added. Schedule creations can also delete jobs from the production schedule if they are deleted from the Scheduler database, and they haven't run yet.
Create Hyperlink	A feature in the graphical View that creates a hyperlink by displaying the Choose a View for Link dialog to create a hyperlink from the current view to another existing view. You click the link icon to display the linked view.

D
default working model	The default working model comprises a set of default Security Policy Templates of which you can designate one to each type of user of Scheduler. When all templates are assigned within a network of Scheduler users, each user operates and is responsible for a piece of the entire scheduling process. When taken as a whole, the entire scheduling process is complete.
Deferred status	Another occurrence of the job was running when a new occurrence tried to execute, and the concurrency option for the job was set to Defer until completion . The job occurrence will run after the running occurrence completes.
dependency	A dependency is a condition that must be met before a Job can run. Dependencies are specified in a job’s definition. Scheduler includes time dependencies, job dependencies, variable dependencies and file dependencies.
diagnostic message	A diagnostic message is a type of message used for internal debugging purposes and help-desk support.
dynamic rerouting	The ability of an ordered agent list to reroute a job from a primary unavailable agent to another available agent in the list.

 

E
environment file	A file that includes a set of constants that define the environment for a command or executable. The command or executable refers to the environment file for information such as local path names. Environment files allow a command or executable to be portable among different machines.
error message	A message indicating that an error occurred somewhere in Scheduler. All Scheduler error messages are defined in the System Configuration dialog. All error messages, audit and diagnostic messages can be displayed from the Logs pane.
Error Occurred status	An internal computer error or security breech occurred that prevented the job from running.
estimated duration	The part of a job’s definition where you enter an estimate of how long a job should run. If a job has run one or more times, this value is the historical average of actual run durations.
event trigger	Scheduler monitors every point in a job’s life cycle, and changes in a job’s status are event triggers. Other triggers include schedule irregularities such a job running shorter or longer than expected, and operator job control such as stopping, starting, and overriding jobs. (also see Job Event triggers)
execution slot	An execution slot is an opening for a job to run. The total number of available slots are determined either by the system queue limit, the sum of all the queue limits, or the sum of all the job limits that are on every licensed Scheduler agent in your network, whichever is less.
exit code	An exit code is the value returned at the end of every completed process. A Scheduler agent relays this value to the master to be used in deciding what status to assign the completed job. The job definition usually defines what job status is denoted by a specified exit code. Normally, an exit code is 0, but the OCSEXIT command can be used to specify a different exit code at the end of a script. The exit code can range from 0 to 30,000. If you are running a batch script, only the last process that completed is used by the operating system to set the exit code.
Externally Defined status	The job is waiting for the status to be set externally.

 

F
fault monitor	The component of Scheduler Fault Tolerance that monitors the primary master for system, network, or hardware faults. If a fault occurs, the fault monitor switches scheduling control over to the backup master.
fault tolerance	A fail safe mechanism that ensures uninterrupted scheduling. Fault Tolerance is software that is optionally supplied with Scheduler on a licensed basis. It uses a primary and backup master with replicated databases and uses a fault monitor system that monitors the primary master for a network or system failure. If failure occurs, scheduling control is switched over to the backup master until the primary master is fixed.
file dependency	A condition associated with a job where a file must exist, not exist, be less than a certain size, be greater than a certain size, or be stable for a certain amount of time before the dependency is resolved.
flag	A flag-shaped icon that is assigned to individual objects defined in a graphical View. Flags serve as markers to highlight designated objects. A text message can be attached to the flag that can be read by pausing the cursor over the flag.

 

G
Gant-style chart	A chart containing visual styles, wallpapers, application skins, etc.
Grant All Edit option	The Grant All Edit option grants the Edit Queue function but not the more advanced functions of Edit System Queue or Edit Nice Queue Value .
Group option	If the Group option is selected then the User/Group Name drop-down list only displays the groups that belong to the selected domain.

 

H
Held status	The job occurrence was temporarily put on hold by an operator. A job can be held only when it has the Waiting On Resources or Waiting On Dependency statuses.

 

I
intermaster dependency	You can create jobs with variable dependencies that are determined by jobs processed on another master. A job with an intermaster dependency resides on a local master subscribing to a remote master that publishes the value of a variable. The variable is defined on the remote master and made available to other masters.

 

 

J
job	A job is the basic scheduling unit in Scheduler. Also called a job definition, or a job, a job consists of a command script or executable, and a set of scheduling criteria and runtime instructions, including dependency information. Command executables can include any number of system activities. Scheduling criteria include when and how often to run the executable file.
Job Activity pane	The central point of control for monitoring and controlling jobs. The Job Activity pane lists each job occurrence in the production schedule. It also shows and lets you take action on operator alerts that are generated by jobs.
job alias	A unique 8-digit code that identifies a job or job group. Job aliases are particularly useful when using the command-line interface, since some operating systems still have an 8-character restriction, and because a job name can specify more than one job.
job class	Job classes are be used to organize when, where and/or how jobs are run, and are created from the Job Classes pane.
job control	Scheduler lets you manage jobs in the Job Activity window including aborting, stopping, holding, and releasing jobs, overriding job dependencies, rerunning jobs, and setting job completion statuses. Job control can be performed by an user or through a job control action.
job dependency	A job that prevents a job from running until an associated job reaches a particular status.
job event	A feature of Scheduler that provides a link between job event triggers and actions. Each job event responds to a single job event trigger, but can respond with multiple actions, which can be sending an email, an SNMP message (trap), an alert, adding a new job, controlling a job, changing a user-defined variable, or posting a log message. A job can also respond to system events.
job event trigger	A condition such as a job occurrence status change, schedule irregularity, or job control action which causes a job event to occur and subsequent actions to be issued. Scheduler continually monitors for event triggers.
job group	A set of jobs and other job groups which have properties and runtime instructions inherited from the job group to which they belong. Job groups allow for the hierarchical organization of jobs. You can define dependencies that refer to job groups as well as individual jobs.
job ID	The job ID is used interchangeably with the term job number. Both terms are often loosely used and refer to two distinctly different things depending upon the context the terms are used in. When used in association with job definitions, the term job ID (or job number) refers to the job ID, the unique identifier of the job definition. When job ID (or job number) is used in association with the Job Activity window, the term refers to the job instance ID, the unique identifier that distinguishes between different instances or occurrences of the same job. See the definition for job instance.
job instance	The basic unit of a production schedule used in the Job Activity pane to designate a specific occurrence of a job within the schedule. A job may run numerous times during the day so the job instance distinguishes between different instances or occurrences of the same job. Each job instance is given a job instance ID number to uniquely identify it.
job limit	A value assigned to a licensed Scheduler agent that limits the number of jobs it can run concurrently. Job limits are defined from the Connections window.
job number	See job ID definition .
job occurrence	The basic unit of a production schedule that represents a specific occurrence of a job within the schedule. The production schedule can have more than one occurrence of a job running at the same time. Also called the job instance.
job pane	The portion of the Job Activity pane which displays the status and other properties of each job occurrence in the schedule.
job priority	A job’s launch importance set in the job’s definition. This value is relative only to other jobs in the same queue.
job tree	The hierarchical structure Scheduler uses to display jobs and job groups in the Jobs pane.
JVM	Java Virtual Machine (JVM) is needed by the Scheduler components that run on the Unix platform so they can respond to Java commands. Verify that the correct version of JVM is used with Scheduler. Check the installation prerequisites for each component for the recommended version of JVM. The JVM can be downloaded for free from the Sun Microsystems website.

 

K
Key File	The key file must be generated by an SSH open system. To use a private key file, you must supply the password and directory location of the private key file.

 

L
Launched status	The job occurrence is in the process of being started on its agent. This status is between Waiting On Resource and Active .
life cycle	A job occurrence life cycle consists of all the phases that the job occurrence enters into and exits while it is in the production schedule. Each phase is determined by the job’s status. A job occurrence begins its life cycle when it is added to the production schedule, and ends when it completes its execution or exceeds its schedule time frame.
Locked status	The status of a defined resource that indicates the resource is being used to its defined limit. No other job may use the resource until the current jobs using the jobs complete and release a sufficient amount of the resource. If a resource is not in a Locked status, it is in either an Available status or a Waiting status.
log message action	A log message action is a type of Action that posts a message of your choice to the Scheduler Logs window when a job event occurs. You can also route the message to the Windows Event Viewer utility.
log viewer	see logs pane
logs pane	A Scheduler window that enables the user to view and to search through a record of all audit, error, and diagnostic messages created by Scheduler throughout the process of creating, scheduling and running jobs. In Scheduler releases prior to v2.2, logs were viewed through the Log Viewer.

 

M
mask	A string with wildcards used to search for job names from the Job Search dialog and in queue filters. Masks include the * and ? wildcard characters. The * wildcard is a mask for any number characters, while the ? wildcard is the mask for a single character. For example, AA* masks AA, AAB and AAB1, but not ABB. AA? masks AAB, but not AABB or ABB.
master	Any Windows system running the Scheduler scheduler with its own database and production schedule.
Master.Props File	The properties of the Unix master are managed in a file called Master.Props that resides in the config directory on the master machine. You change the configuration properties of the Unix master by manually adding a new property or modifying the value for an existing property. The Master.Props file stores information on the machine names, port numbers and drivers used by the Unix master.
maximum duration	The maximum length of time you will allow your job to run. Scheduler has an event trigger that monitors whether the job ran past its maximum duration. This event trigger can be used to trigger an action(s) of your choice.
minimum duration	The minimum length of time you expect the job to run. Scheduler has an event trigger that monitors whether the job’s run duration was less than its minimum duration. This event trigger can be used to trigger an action(s) of your choice.

 

N
new job	A type of action that inserts a job with optionally modified properties into the production schedule. A new job action can be used to run recovery jobs in case the primary job fails.
nice value	Relative CPU scheduling priority, assigned when Scheduler launches a job on a Unix agent, and determined from the job's assigned queue. See the Unix manual page under nice (1) for more information.

 

O
OCSEXIT	The command, OCSEXIT , is used to set a batch job’s completion status to Completed Abnormally by specifying a non-zero exit code when a job finishes. Any non-zero exit code means the job completed abnormally. If the OCSEXIT command is omitted, the exit code is assumed to be 0 and the job completed normally. The OCSEXIT command should be the last executed statement in the script.
operator	A Scheduler user with a security policy that enables access to the Job Activity pane, and Job Control actions. According to the Default Working Model, the Operator is responsible for compiling and running the production schedule, monitoring job occurrences, watching for and responding to operator alerts, and controlling jobs as necessary.
operator alert	see console alert
Orphaned status	The master lost track of the job’s status while the job was running and the job's final status is unknown. This status occurs when either the agent goes down or the connection between the agent and the master fails.
override	The job control which allows a job to run by ignoring all dependencies and making the job available for immediate launching.
owner	The user or workgroup that created the Scheduler object (job, calendar, event, etc.).

 

P
Pan and Zoom	See Bird’s Eye View .
parent agent list	An agent list containing other agent lists called child agent lists. A child agent list must be of the same type as a Parent Agent List.
parent job group	A job group that includes other jobs or job groups. A job or job group, by default, inherits its scheduling and run properties from its parent job group.
parent queue	Any queue that has subqueues, called child queues.
primary agent	In a primary alternate agent list, the primary agent is the agent of choice to run jobs. Alternate agents function as substitutes for the primary agent if it becomes unavailable.
primary master	The master from which normal scheduling operations are executed. When using Scheduler Fault Tolerance, the primary master accompanies a backup master which can take over scheduling operations should the primary master fail.
production schedule	The database of all jobs selected to run within a given production date range. Scheduler compiles a production schedule by using your job definitions to create job occurrences that will run within the production period. Dependency and progress information is included with the schedule and updated according to the master’s polling interval.
purge frequency	The frequency in days when Scheduler looks for job occurrences to purge from the production schedule. Purging takes place for job occurrences which are older than their respective job's Retention Period option setting.

 

Q
qualified job	A job that has the qualifications that allow it to be added to the production schedule when the schedule is created. Qualified jobs have their active flag set, and have an associated calendar such that the job's next run date falls within the days that are included for the schedule creation.
queue	Controls job execution priority and sequencing by allowing limited collections of jobs to run with different priorities. Queues are assigned job quantity limits and queue priorities in a hierarchy of queues. All jobs are assigned to a queue according to their job properties using queue filters.
queue filter	Queue filters contain definitions used to determine the jobs that will be assigned to the queue when all their dependencies are met. The queue manager assigns jobs to queues based on each job’s properties. Using queue filters, you can control and organize when and where to launch jobs.
queue limit	The maximum number of job occurrences a queue can run at any time.
queue manager	The part of Scheduler that controls job launch activity. The queue manager is responsible for assigning jobs to queues based on the match between each job’s properties and each queue’s queue filter criteria. If more than one queue can accept a job, the queue with the highest queue priority value is chosen.
queue priority	The priority rank of a queue relative to other queues at the same level in the queue hierarchy. Jobs in higher priority queues are generally run before jobs in lower priority queues.

 

R
remote shell agent	A Unix computer that has remote shell (rsh, remsh, or rcp) services. Scheduler can run Unix-only jobs on these types of agents, but cannot take advantage of some of the advanced features such as workload balancing, and fault tolerance that Scheduler agents offer.
resource	A system asset that is required by a job for its successful completion. This resource can be either hardware like a printer or simply access to a designated database. Though a job can still run if an asset is not defined as a resource in TES, by defining the asset as a resource, access to that resource can be managed. Limiting the simultaneous demand on a resource can streamline production and improve efficiency.
resource limit	A value designated during the definition of a resource that determines the quantity of a resource available for jobs, similar in principle to agent limit. A quantity of the resource is allocated to each job as required by a job’s definition until the resource limit is reached. No other jobs can use the resource until jobs currently running complete, freeing up enough of the resource for another job to run.
retention period	The number of days that job occurrence data is retained in the production schedule. Job occurrences that have occurred beyond the retention period are automatically purged according to the History Retention setting on the Options tab of a job definition.
runtime user	The user logon used for a job. The Runtime User option gives the job the user's environment when running a job. Runtime users are defined on your agents and in the User Definition dialog.

 

S
Scheduled status	The initial status all jobs and job groups enter when they have just been compiled into the production schedule, before their true status is determined.
scheduler	An Scheduler user who schedules jobs for another user. Scheduler users have access to the applications and environments of other users listed in their Runtime User list. Runtime Users are defined in the User Definition dialog.
script	In Unix terminology, a file containing Unix commands for the shell to execute as a job. A script can also be a file containing MS-DOS commands.
security policy	A list of system features that can be assigned to a Scheduler user. Scheduler has default security policy templates you can customize to fit the needs of Scheduler users in your organization.
security policy template	Security policy templates contain a predefined set of system features. Each default security policy can be used to help you create your own security policies. The default working model comprises all the default security policy templates.
Skipped status	Another occurrence of this job was running when the agent tried to launch the job, and the concurrency option for the job was set to Skip . This job occurrence never runs.
SNMP	SNMP (Simple Network Management Protocol) is a messaging protocol used for sending network management data. Actions can include messages (also called Traps) that are collected by SNMP agents, and sent to managers that make the information available to network administrators, and/or display the messages on an SNMP console.
Stopped status	The job has been stopped by a user or through a job control action. A job can be stopped only if it is Active .
super user	A user with a security policy containing all available application functions. Super User is an option in the User Definition dialog.
Scheduler database	The central repository for storing all Scheduler scheduling data. The database is stored on the master system and is shared between all users of the Scheduler system.
Scheduler desktop	The desktop on which all Scheduler windows appear as tab pages.
Scheduler toolbar	The toolbar is located above the Scheduler desktop. For more information about the Scheduler interface, see Getting Started .
system administrator	The user of Scheduler who has a System Administrator security policy. The System Administrator is usually responsible for configuring Scheduler for the needs of users. Can also mean the site’s System Administrator, the person in charge of computer security and other critical responsibilities.
system event	A feature of Scheduler that provides a link between system event triggers and actions. Each system event responds to a single system event trigger, but can respond with multiple actions, such as sending an email, an SNMP message (trap), an operator alert, adding a new job or controlling a job. A job can also respond to job events.
system event trigger	An event that originates from the system, as opposed to originating from a job, that can be used to issue an action associated with the job.
system queue	The queue at the top of the queue hierarchy. The number of jobs running on Scheduler at any given time can be limited to the queue limit value assigned to this queue. The system queue has the lowest queue priority, and is used as the default queue for jobs that cannot be accepted into other queues according to their queue filters.
system queue limit	The system queue value that determines the overall number of jobs Scheduler can run at any given time. This value must be less than the sum of all the agent’s Job Limit values and the sum of all the individual queue limit values for this control to work effectively, since the job scheduling capacity is limited to the system queue value, the sum of the Job Limit values, or the sum of all of the individual queue limit values, whichever is smaller.

 

T
time dependency	A condition where time controls whether a job is ready to run not. A time dependency is determined by a job's calendar and time window.
time window	A job property that specifies the period of time during the day (24 hour period) when the job can run. The Time Window setting is optional. The default is 24 hours.
Timed Out for Day status	The job's dependencies were not met by the end of its time window today. The job will be a candidate to run tomorrow during its time window if its dependencies are satisfied.
timed out status	The job's job or file dependency was not met by the end of its time window. The job will not run.
tracking method	The part of a job’s definition that instructs Scheduler how to determine whether a job completed successfully or not.

 

U
unscheduled job	A job that is not scheduled to run on a regular basis, and is added to the production schedule on an “as needed” basis. You can add unscheduled jobs to the production schedule any time while production is running. Unscheduled jobs include all job definition properties, except a calendar.
user	A registered user of Scheduler. Users can have ownership (along with workgroups) of jobs, job events, actions, variables, and calendars. Each user has access to a limited set of Scheduler features as defined by the user’s security policy.

 

V
variable	A data item that can be added to action message text, or as a command parameter. The variable’s value is based on the type of variable used. Variable types include system variables, job variables, job event variables, action variables, and user-defined private and public variables.
variable dependency	A dependency that prevents a job from running until a specified user-defined variable has a specified value. Variables can be updated manually, or by other jobs through a variable update action.
variable update action	A variable update action is a type of action that changes a user-defined variable when a job event occurs. The variable's value can be used as the criteria to meet a variable dependency.

 

W
Waiting on Dependencies status	The job occurrence has been scheduled and is waiting on dependencies to be satisfied before it will run.
Waiting on Group status	The status a job occurrence enters when it is waiting on its parent job group's dependencies.
Waiting on Operator status	All the job occurrence’s dependencies have been met, and it is waiting for a user to release it.
Waiting on Resource status	All the job occurrence’s dependencies have been met, and it is in a queue waiting to be launched.
Waiting status	The status of a defined resource needed by a job displayed on the Resources tab of a job's Job Details dialog. This status indicates a job is waiting to use the resource. Anytime that the amount needed of the resource exceeds the amount available of the resource it will show a Waiting status. If a resource is not in a Waiting status, it is in either an Locked status or an Available status.
workload balancing	The ability of Scheduler to distribute jobs among a group of agents in an agent list, thereby reducing the load on any single agent. There are three types of workload balancing: 1) Lightest Load, 2) Random, and 3) Rotation. Lightest load distributes a job on the machine in the list with the lightest load. Random distributes a job on a machine in the list randomly. Rotation distributes a job on the next machine in sequence on the list.
workgroup	A collection of users who can share jobs, job events, system events, actions, variables, and calendars. Any user can create a workgroup and invite other users into it. In order to belong to a workgroup, you must be invited in by its owner, the originator of the workgroup.

 

X
XML file	The Extensible Markup Language (XML) is a W3C-recommended general-purpose markup language that supports a wide variety of applications.

 

Y
Year option	Select this option to include the year in your custom date format.

 

Z
Zoom In/Zoom Out	This is a toggle option controlling the view perspective of the job flow