Skip to main content

Job type catalog

The complete list of job types available today, grouped by category.

Every job in a workflow runs exactly one job type — the thing that decides what the job actually does. Job types are not built into the product one by one: each comes from a plugin (a connector), and each plugin declares a category. Enable a plugin and its job types become available to Builders; disable it and they disappear from new jobs.

Where you choose a job type​

In the job editor, on the Job Definition tab, pick a type from the Job Type list in the Job Type section (Choose a job type...). The list holds every job type your organization's enabled plugins provide.

Once a type is chosen, the Job Parameters section renders the fields that type declares. Changing the type later clears both the old parameters and the agent assignment, because neither carries over. Agent Assignment appears only for types that run on an agent — Null Job and Workflow Container run in the platform, so it is hidden for them.

The workflow editor sidebar also offers a quick-add shortcut that creates a job with its type already set.

The categories below are each plugin's own category. They are how the Marketplace administration page groups and filters plugins; they are not headings in the picker.

The catalog​

76 job types across 18 plugins. The newest are z/OS Tracked Job and z/OS Queued Job, which bring the z/OS LSAM plugin to six types and put a job the z/OS LSAM agent reports — one submitted outside OpCon, or one the agent is holding — on its schedule. Before them came MCP Copy, MCP Change and MCP Remove, which bring the MCP LSAM plugin to six types and copy, rename or remove a file or a whole directory on a Unisys MCP LSAM agent, and z/OS Started Task, z/OS REXX Exec and z/OS Console Command, which start a procedure as a started task, run a REXX exec or issue an operator command on a z/OS LSAM agent. Before them came OS 2200 Job, the one job type of the OS 2200 LSAM plugin, which starts an ECL runstream on a Unisys OS 2200 LSAM agent, and MCP EAE/AB Suite, a third MCP LSAM type, which runs an EAE/AB Suite report, and before them MCP Run and MCP Start, the first two job types of the MCP LSAM plugin, which run a program or start a WFL job on a Unisys MCP LSAM agent, and before them z/OS Batch Job, the first job type of the z/OS LSAM plugin, which submits a JCL member to JES on a z/OS LSAM agent, and before that SAP BW Process Chain, the one job type of the SAP BW LSAM plugin, which starts an SAP BW process chain by its technical name, and before that SAP R/3 Job, the one job type of the SAP R/3 and CRM LSAM plugin, which starts an existing SAP R/3 or CRM background job by name and number, and before that SQL - MySQL, a sixth SQL LSAM type, which runs a MySQL script file with the mysql client, and before that SQL - Oracle, which runs a SQL*Plus script, and SQL - Other DB, which runs SQL through an ODBC driver or OLE DB provider, both on the SQL LSAM plugin, and IBM i - File Arrival, which waits for a file on an IBM i LSAM machine. Before them came three more IBM i LSAM types — IBM i - Operator Replay, IBM i - Restricted Mode and IBM i - FTP — SQL - MS SQL DTExec and SQL - MS SQL Job on the SQL LSAM plugin, and the twenty in the EASE (Episys As A Service) plugin, which runs jobs on Jack Henry's hosted EASE OpCon — three of those twenty are in the catalog but not supported yet. The five IBM i types are recent.

Built In​

Script​

Job typePluginWhat it doesConnectionRuns on
Run CommandRun CommandRuns a command line on the agent — either through a shell (the default) or as a direct processNoneUniversal Agent — Windows, Linux, macOS
Run ScriptRun ScriptRuns an embedded script you type into the job, using the matching interpreter: PowerShell, Bash, Python, or ShellNoneUniversal Agent — Windows, Linux, macOS

Both are built in to the Universal Agent, so there is nothing to install or enable. See Run Command job and Run Script job.

Utility​

Job typePluginWhat it doesConnectionRuns on
Wait for FileWait for FileHolds the workflow until a file appears and meets optional size, age, and stability criteria; can delete the file once detectedNoneUniversal Agent — Windows, Linux, macOS

Also built in. See Wait for File job.

Database work​

Database work runs on an existing SQL LSAM machine, through the six SQL LSAM job types — SQL - MS SQL Script, SQL - MS SQL Job, SQL - MS SQL DTExec, SQL - Oracle, SQL - Other DB and SQL - MySQL. They are listed under Integration — legacy LSAM, on the Legacy LSAM tab. No job type runs database work on a Universal Agent.

Internal​

These run inside the platform. No agent is involved, so they have no agent assignment and no OS requirement.

Job typePluginWhat it doesConnectionRuns on
Null JobNull JobCompletes immediately. Used to aggregate dependencies, hang events off a single point, and build a workflow on hold. Takes no parametersNoneThe platform — no agent
Workflow ContainerWorkflow ContainerEmbeds another workflow as a single step; the referenced workflow is built and run as part of this oneNoneThe platform — no agent

See Null Job and Workflow Container job.

Good to know
  • A job type is fixed once a job has been processed. In a running or completed instance the Job Type picker is read-only; you choose it while designing the job, not while it runs.
  • Changing the job type clears its parameters and its agent. Compatible agents are job-type-specific, so neither can safely carry over. Re-set both after a change.
  • "The job type I need isn't in the list": check Marketplace first. Every shipped plugin is enabled by default, with all its job types on, so a missing type usually means an administrator has turned it, or its plugin, off for your organization — see Turn job types on or off.
  • A job keeps its job type when an administrator turns that type off. It opens with the type still selected, saves and runs as before; the type is simply not offered for new jobs.
  • Saving a job checks that its required parameters are filled in (Required parameter '…' is missing.) and that its exit-criteria rows are complete, but most parameter values are not checked until the job runs: a bad value saves cleanly and fails when it runs — on the agent for the Universal Agent types, and at the relay at dispatch for the legacy LSAM types. The exceptions are a few save-time rules: the embedded-script types' script and runner, a set of cross-field rules enforced when you save a SMAFT transfer or an OpCon MFT transfer, and every field of an OS 2200 Job, which is refused at save when a value the agent could not be sent is in it.
  • Null Job is not a no-op to skip past. It's a workflow-design workhorse — the standard way to fan many dependencies into one point.
  • A job may itself be a whole workflow. When troubleshooting, remember a Workflow Container step expands into a child workflow.
  • The legacy LSAM types take a saved connection for the account they run as — all but SAP R/3 Job and SAP BW Process Chain, which use the logon configured on the agent, z/OS Batch Job and OS 2200 Job, which name their user in a User ID field, and the other five z/OS types, which have no user field. Beyond those, an OpCon MFT Transfer may take one for its optional compression password. The built-in command, script, file-wait, and internal types need none — they take their credentials from the agent.
  • A legacy LSAM type with no working relay can't be placed at all. That surfaces as no compatible agent to choose rather than as a relay error, which is worth knowing before you go looking for one.

Related topics