36 docs tagged with "Reference"

The OpCon server consists of the Schedule Activity Monitor (SAM) and supporting services (SAM-SS).

The basic OpCon Server configuration includes a single machine, a single database, and a StandAlone SMAServMan.

SMAChkStat.exe compares schedule and job statuses in OpCon against a logical expression, then returns a pass or fail exit code.

The Daily Job Definition is the runtime instance of a master job.

The Continuous SQL scripts for mirroring the OpCon database use scripting variables defined in SMA_SetDBMirroringScriptingVariables.cmd.

The Continuous SQL scripts for replicating the OpCon database use scripting variables defined in SMA_SetDBReplicationScriptingVariables.cmd.

This section contains the syntax, definition, and parameter descriptions for all supported OpCon events.

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

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

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 to be run.

Job Task Details contain the platform-specific settings that control how a job runs on its target agent — the command, script, parameters, user credentials, and platform-specific options.

OpCon supports jobs across a wide range of platforms.

A _job_ in OpCon is a task or activity, such as running a program on a remote machine, transferring files between machines, or running another schedule.

Enterprise Manager supports keyboard shortcuts that speed up navigation and common tasks. Shortcuts are available at the application level (such as F1 for help) and within individual views and editors.

The Machine Information dialog provides details about the selected machine.

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.

Each notification trigger can send alerts through one or more delivery channels.

OpCon notifications fire when jobs or schedules reach specific status conditions.

Configure global behavior settings for the OpCon SAM and supporting services, including time settings, logging, SMTP configuration, password requirements, and Vision settings.

In addition to displaying the completion percentage and the interim transfer operations (e.g., compressing, decompressing, etc.), the EM displays specific file transfer codes from the agent's.

Each agent returns different status messages while a job is running and when a job completes.

Optional components in OpCon extend the core server with additional capabilities such as LDAP synchronization, notification handling, and data input processing.

This section applies to defining an OS 2200 job.

Skills are the specific actions Otto can perform in OpCon on your behalf.

Properties are attributes of OpCon objects.

Reference material for OpCon events, notification configuration, reports, command-line and graphical utilities, error message codes, property expression syntax, best practices, and licensing.

Schedules and jobs in Schedule Operations have a status that indicates state and determines allowed status changes.

The SMA Request Router reads the OpCon database to process requests from the SAM and the Enterprise Manager.

SMADirectory (SMADirectory.exe) manages OpCon directories, keeping log and report directories from consuming excessive disk space.

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

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

Each master job has multiple configuration panels covering its core task details, frequencies, dependency rules, events, tags, and more.

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

Error numbers and descriptions for Microsoft Windows Error Codes (0-499).

The Operation views display all schedules to which the current user account has access in the Daily tables.