45 docs tagged with "Jobs"

OpCon bases all date and time automation on the OpCon server's date and time, providing a consistent reference for all graphical interfaces and agent machines.

Reference for the fields used to define a BIS job in OpCon.

This section explains the core building blocks of OpCon automation — the objects, rules, and behaviors that define how work is scheduled, run, and tracked.

OpCon Container jobs are used to run a subschedule.

Job documentation is user-defined information (e.g., command history, operator instructions for failure).

Master job definitions can include all possible Job Automation Components.

Embedded Scripts in OpCon lets users centrally manage scripts for distribution to Agents.

Events are OpCon events the SAM processes based on triggers: job status, agent feedback string match, Exit Description evaluation, or Evaluation Expression.

Each OpCon job can depend on the result of an expression defined using the Property Expressions API.

The information in this section applies to defining a File Transfer job.

The SMA File Transfer (SMAFT) system transfers files across multiple platforms via an OpCon job.

Frequencies are calendar rules that determine which days a job or schedule qualifies to build and run.

The information in this section applies to defining an IBM i job.

The instance definition for a job is a place to define properties for one or more instances of the job.

OpCon supports running the same schedule multiple times simultaneously using named instances or multi-instance definitions.

Field reference for configuring a Java job in OpCon, covering the Class, Command, and JAR operations.

Frequencies specify the recurring days on which a schedule or a job should run.

Every job and schedule in the daily queue has a status reflecting its current state, and understanding those statuses helps you monitor and control automation workflows.

Job automation components control how OpCon jobs behave, including frequencies, dependencies, events, and threshold updates.

Each OpCon job can depend on one or more OpCon jobs.

The Frequency specifies the weeks, days, and calendar information for when a job is scheduled to run.

The Instance Definition tab in Job Master lets you predefine property sets for one or more instances of a job.

OpCon was designed to use two major sets of tables.

Job Tracking lets OpCon monitor external jobs (user-submitted or program-submitted) that were started outside an OpCon schedule or event.

OpCon supports jobs across a wide range of platforms.

MCP job details define the parameters for running a job on a Burroughs MCP agent, including user code, access code, file title, and task attributes.

Named Schedule Instances reduce the maintenance burden on repeatable workflows by allowing a single definition rule to be designated for unlimited use or job runs.

The Null job generates OpCon events and/or sets thresholds without running a job.

The Null job generates OpCon events and/or sets thresholds without running a job.

Reference for the fields used to define an OS 2200 job in OpCon, including Start Command, Run Card Control, dependencies, completion status, and tokens.

The Property Expressions API gives you advanced control over job dependencies and events by evaluating expressions that read and write OpCon property values at runtime.

Field reference for defining an SAP BW job in OpCon, including machine selection, process chain name, and the Process Chain List search dialog.

Field reference for defining an SAP R/3 and CRM job in OpCon, including login settings, general data, job step types, and print specifications.

Schedule and job status change commands are used with events and graphical interfaces to control processing of schedules and jobs in OpCon.

The information in this section applies to defining a SQL Job.

Tags are labels you can create to group jobs based on business needs.

Threshold and resource dependencies allow a job to wait until a threshold reaches a specified numeric value or a resource pool has enough available units before it is eligible to start. These dependencies are defined at the job level or at a specific frequency level.

Threshold and resource updates cause OpCon to change a threshold value or resource count when a job enters a specific status — such as Finished OK or Failed. These updates are defined at the job level or at a specific frequency level.

Field reference for configuring a Tuxedo ART job in OpCon, including the Variables, Step Control, and Failure Criteria tabs.

The information in this section applies to defining a UNIX job.

There are several scenarios for automation that benefit from using Machine Groups in OpCon.

Secondary windows in the Operations view provide read-only and interactive details about schedules, jobs, subschedules, history, and machines without leaving the current view.

The information in this section applies to defining a Windows Job.

Reference table of Microsoft Windows System Error Codes (0–499) for interpreting Windows job exit codes in OpCon.

The information in this section applies to defining the z/OS Job Type information.