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
- Legacy LSAM
- OpCon RPA
- EASE
- File Transfer
- Categories and Availability
Built In
Script
| Job type | Plugin | What it does | Connection | Runs on |
|---|---|---|---|---|
| Run Command | Run Command | Runs a command line on the agent — either through a shell (the default) or as a direct process | None | Universal Agent — Windows, Linux, macOS |
| Run Script | Run Script | Runs an embedded script you type into the job, using the matching interpreter: PowerShell, Bash, Python, or Shell | None | Universal 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 type | Plugin | What it does | Connection | Runs on |
|---|---|---|---|---|
| Wait for File | Wait for File | Holds the workflow until a file appears and meets optional size, age, and stability criteria; can delete the file once detected | None | Universal 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 type | Plugin | What it does | Connection | Runs on |
|---|---|---|---|---|
| Null Job | Null Job | Completes immediately. Used to aggregate dependencies, hang events off a single point, and build a workflow on hold. Takes no parameters | None | The platform — no agent |
| Workflow Container | Workflow Container | Embeds another workflow as a single step; the referenced workflow is built and run as part of this one | None | The platform — no agent |
See Null Job and Workflow Container job.
Legacy LSAM
Integration — legacy LSAM
These drive your existing OpCon LSAM machines through a relay, so you can bring current automation into OpCon Continuum without rebuilding it. They dispatch only to legacy agents of the matching type, never to a Universal Agent, and they need a configured relay to work at all.
UNIX/Linux LSAM
Plugin UNIX/Linux LSAM; every job type here runs on a UNIX LSAM agent.
| Job type | What it does |
|---|---|
| UNIX Command | Runs a command or script on a UNIX/Linux LSAM machine |
| UNIX - File Arrival | Waits for a file to arrive during a time window and succeeds once it has stopped growing; the LSAM agent does the watching, so there is no connector to install and no command line |
| UNIX - Embedded Script | Runs a script from the script library — you choose the script, the version to track or pin, a runner, and optional arguments |
| UNIX - Episys: Run JobFile | Runs an Episys batch job file through RSJ, optionally from a restart point, with an edit file or without the SYM lock |
| UNIX - Episys: Answer Prompts | Fills in the prompts in an Episys batch control file, one prompt-and-response row per prompt |
| UNIX - Episys: Compare ACH Totals | Compares a FED ACH file's totals against an Episys batch output |
| UNIX - Episys: Find Batch Output Sequence Number | Finds an Episys job's batch output sequence number and writes it to a property you name |
| UNIX - Episys: Find Report from RSJ Output | Finds a report by title in an Episys job's RSJ output and writes its sequence number to a property you name |
| UNIX - Episys: Find Report from Episys Reports | Finds a report by title in the Episys report directory and writes its sequence number to a property you name |
| UNIX - Episys: FTP all Reports in List | Sends every report listed in a file to an FTP destination |
Windows LSAM
Plugin Windows LSAM; every job type here runs on a Windows LSAM agent.
| Job type | What it does |
|---|---|
| Windows Command | Runs a command on a Windows LSAM machine |
| Windows - WS_FTP Pro | Runs a WS_FTP Pro file transfer using site profiles configured on the machine |
| Windows - Command: File Copy | Copies one or more files (wildcards allowed) |
| Windows - Command: File Move | Moves one or more files, overwriting the destination without prompting |
| Windows - Command: File Rename | Renames a single file (cannot overwrite an existing name) |
| Windows - Command: File Delete | Deletes one or more files or directories (wildcards allowed) |
| Windows - Corelation | Submits and monitors a Corelation batch job through the SMA Corelation connector on the machine |
| Windows - Fiserv DNA | Runs a Fiserv DNA SQT job through the SMA DNA connector on the machine |
| Windows - Fiserv DNA (File Loader) | Runs a Fiserv DNA file-load job through the SMA DNA connector on the machine |
| Windows - File Arrival | Waits for a file to arrive during a time window and succeeds once it has stopped changing; uses the LSAM's own file watcher, so there is no connector to install |
| Windows - Embedded Script | Runs a script from the script library — you choose the script, the version to track or pin, and a runner |
| Windows - Web Services | Runs a sequence of HTTP/REST calls through the SMA Web Services connector on the machine, passing values extracted from one response into later requests |
IBM i LSAM
Plugin IBM i LSAM; every job type here runs on a IBM i LSAM agent.
| Job type | What it does |
|---|---|
| IBM i Command | Submits a batch job on an IBM i (AS/400) LSAM machine. No exit-criteria setting |
| IBM i - Operator Replay | Runs an Operator Replay script on an IBM i LSAM machine. No exit-criteria setting |
| IBM i - Restricted Mode | Runs a Restricted Mode script on an IBM i LSAM machine. No exit-criteria setting |
| IBM i - FTP | Sends, receives or deletes files over FTP from an IBM i LSAM machine — one file or several. No exit-criteria setting |
| IBM i - File Arrival | Waits for a DB2 file or an IFS file to arrive on an IBM i LSAM machine, optionally inside a creation window and once its size is stable; the LSAM does the watching, so there is no Call. No exit-criteria setting |
SQL LSAM
Plugin SQL LSAM; every job type here runs on a SQL LSAM agent.
| Job type | What it does |
|---|---|
| SQL - MS SQL Script | Runs a T-SQL script on a SQL LSAM machine — inline statements you type into the job, or a .sql file already on the machine |
| SQL - MS SQL Job | Starts an existing SQL Server Agent job on a SQL LSAM machine and reports its outcome, or monitors a run already in progress. The agent drives it directly rather than through sqlcmd |
| SQL - MS SQL DTExec | Runs a SQL Server Integration Services (SSIS) package with DTExec on a SQL LSAM machine — from msdb, the file system or the SSIS catalog |
| SQL - Oracle | Runs an Oracle SQL*Plus script file on a SQL LSAM machine, signing on with the batch user's Oracle login. SQL*Plus must be installed there |
| SQL - Other DB | Runs SQL — typed into the job or from a .sql file — through an ODBC driver or OLE DB provider on a SQL LSAM machine, by connection string or ODBC data source. The driver or provider must be installed there |
| SQL - MySQL | Runs a MySQL script file with the mysql command-line client on a SQL LSAM machine, signing on with the batch user's MySQL login, with optional MySQL user variables. The mysql client must be installed there |
The SQL - prefix keeps the six together in the Job Type list. Elsewhere on this page they go by their short names — MS SQL Script, MS SQL Job, MS SQL DTExec, Oracle, Other DB and MySQL.
SAP R/3 and CRM LSAM
Plugin SAP R/3 and CRM LSAM; every job type here runs on a SAP R/3 and CRM agent.
| Job type | What it does |
|---|---|
| SAP R/3 Job | Starts an existing SAP R/3 or CRM background job, by its job name and job number, on an SAP R/3 and CRM agent. The agent decides the outcome. No exit-criteria setting and no batch user |
SAP BW LSAM
Plugin SAP BW LSAM; every job type here runs on a SAP BW agent.
| Job type | What it does |
|---|---|
| SAP BW Process Chain | Starts an SAP BW process chain, by its technical name, on an SAP BW agent. The agent decides the outcome. No exit-criteria setting and no batch user. See SAP BW Process Chain |
z/OS LSAM
Plugin z/OS LSAM; every job type here runs on a z/OS agent.
| Job type | What it does |
|---|---|
| z/OS Batch Job | Submits a JCL member to JES on a z/OS LSAM agent, with JCL substitutions, a condition-code range and optional Step Control and Dataset Pre-run rows. The agent decides the outcome. No exit-criteria setting and no batch user: a User ID field names the z/OS user. See z/OS Batch Job |
| z/OS Started Task | Starts a procedure, such as a CICS or IMS region, as a started task on a z/OS LSAM agent; the job stays running until the task ends. The agent decides the outcome from its condition codes, with optional Step Control and Dataset Pre-run rows. No exit-criteria setting and no batch user. See z/OS |
| z/OS REXX Exec | Runs a REXX exec in its own address space on a z/OS LSAM agent. The agent checks the exec's return code against the minimum to maximum range; optional Dataset Pre-run rows hold the run until the datasets are ready. No exit-criteria setting and no batch user. See z/OS |
| z/OS Console Command | Issues a z/OS operator command, as entered, on a z/OS LSAM agent. It has no completion code: the job finishes as soon as the agent issues the command. Optional Dataset Pre-run rows hold the command until the datasets are ready. No exit-criteria setting and no batch user. See z/OS |
| z/OS Tracked Job | A job submitted on the mainframe outside OpCon. When the z/OS LSAM agent reports that it started, the job is added to its workflow instance already started, without waiting for its dependencies, and finishes with the condition code the agent reports. It has no JCL here, and runs only from the agent's report. See z/OS Tracked Job and z/OS Queued Job |
| z/OS Queued Job | A job the z/OS LSAM agent intercepts and holds. When the agent reports it, the job is added to its workflow instance and released to the agent once its dependencies are met, then finishes with the condition code the agent reports. It has no JCL here, and runs only from the agent's report. See z/OS Tracked Job and z/OS Queued Job |
MCP LSAM
Plugin MCP LSAM; every job type here runs on an MCP agent, and each can have a prerun — a second MCP job the agent runs first.
| Job type | What it does |
|---|---|
| MCP Run | Runs a program, named by its MCP file title, on an MCP LSAM agent under an MCP usercode, with optional arguments, task and file attributes. The agent decides the outcome from the fail codes you set. No exit-criteria setting. See MCP Run and MCP Start |
| MCP Start | Starts a WFL job, named by its MCP file title, on an MCP LSAM agent under an MCP usercode, optionally keeping a job summary. The agent decides the outcome from the fail codes you set. No exit-criteria setting. See MCP Run and MCP Start |
| MCP EAE/AB Suite | Runs an EAE/AB Suite report on an MCP LSAM agent under an MCP usercode, with its Report Name, Accept File and Parameters, and optional task and file attributes. The agent decides the outcome from the fail codes you set. No exit-criteria setting. See MCP EAE/AB Suite |
| MCP Copy | Copies a file or a whole directory between disk packs and tapes on an MCP LSAM agent under an MCP usercode, optionally to another MCP host over BNA and with a compare after the copy. The agent decides the outcome from the fail codes you set. No exit-criteria setting. See MCP Copy, MCP Change and MCP Remove |
| MCP Change | Renames a file or a whole directory on an MCP LSAM agent under an MCP usercode. The agent decides the outcome from the fail codes you set. No exit-criteria setting. See MCP Copy, MCP Change and MCP Remove |
| MCP Remove | Removes a file or a whole directory on an MCP LSAM agent under an MCP usercode; by default the agent fails the job when there is nothing to remove. The agent decides the outcome from the fail codes you set. No exit-criteria setting. See MCP Copy, MCP Change and MCP Remove |
OS 2200 LSAM
Plugin OS 2200 LSAM; every job type here runs on an OS 2200 agent.
| Job type | What it does |
|---|---|
| OS 2200 Job | Starts an ECL runstream — a file, or an element in it — on an OS 2200 LSAM agent, with run card values, runstream tokens and up to four Completion Status rules, and optionally a prerun or up to eight file dependencies the agent checks first. The agent decides the outcome. No exit-criteria setting and no batch user: a User ID field names the user. See OS 2200 Job |
What the legacy LSAM types share
Every one of them but SAP R/3 Job, SAP BW Process Chain, the six z/OS types and OS 2200 Job takes a batch user connection — the account it runs as. The two SAP types sign on to SAP with the logon configured on the agent itself, a z/OS Batch Job and an OS 2200 Job name the user in their own User ID field, and the other five z/OS types have no user field at all. On Windows, IBM i and SQL that field may be left blank (the agent's service account, the job description's default user, and the agent's service account, respectively); on UNIX it is required, and so it is on MS SQL Job, Oracle and MySQL, and on all six MCP types, whose batch user is an MCP usercode. An MS SQL DTExec job running a package from the file system takes no batch user — it always runs as the agent's service account, so the job editor hides Connection for it — and neither does an Other DB job using an OLE DB connection string without Windows Authentication. An IBM i - File Arrival job uses its batch user only to check authority to the file. See Batch User.
Four Episys types take a second connection on top of the batch user, for the credential the Episys utility itself needs: the three Find types take an Episys External Event Credential, and FTP all Reports in List takes an Episys FTP Credential. See Episys credentials.
The four file-operation types, WS_FTP Pro, Corelation, Web Services and all seven Episys types build their command line for you from form fields, so they have no command-line field of their own. So does IBM i - FTP, which takes the transfer as fields rather than a Call, and Oracle and MySQL, whose SQL*Plus and mysql command lines the agent builds from their fields. IBM i - File Arrival, Other DB, the six z/OS types, the six MCP types and OS 2200 Job have no command line at all: the IBM i LSAM watches for the file itself, the SQL agent runs Other DB's SQL through the driver directly, the z/OS LSAM submits the named JCL member, starts the named started task, runs the named REXX exec, issues the operator command you enter or reports a job it tracks or queues, the MCP LSAM runs or starts what the file title names, runs the named report, or copies, renames or removes the named file, and the OS 2200 LSAM starts the named runstream.
Three IBM i types also take lists — a message monitor, spool-file actions and dynamic variables: IBM i Command, IBM i - Operator Replay and IBM i - FTP. IBM i - File Arrival takes a message monitor and dynamic variables, and IBM i - Restricted Mode dynamic variables only. See IBM i LSAM.
See Legacy LSAM connectors and Relays.
OpCon RPA
Integration — OpCon RPA
| Job type | Plugin | What it does | Agent type |
|---|---|---|---|
| OpCon RPA Task | OpCon RPA | Starts one RPA task — a Robot, a Web Macro or a Scan Document — on an OpCon RPA agent, waits for it to finish, and shows the agent's own logs as the job output | OpCon RPA |
It takes no connection of any kind — no batch user — and it has no exit-criteria setting: the process status the agent reports is the job's verdict. Like an OpCon MFT agent, an OpCon RPA agent is reached through a relay but is not an LSAM, so it has no JORS port and no file-transfer endpoint. Its Task and Version lists are read live from the agent, and an empty Version means run the highest version that exists when the job starts. See OpCon RPA Task job.
EASE
Integration — EASE
Twenty job types from one plugin, EASE (Episys As A Service). Each adds the matching pre-built job to today's instance of your schedule on Jack Henry's EASE OpCon, waits for it to finish, and brings the remote job's output back. Like OpCon MFT and OpCon RPA, an EASE agent is reached through a relay but is not an LSAM — no JORS port, no file-transfer endpoint. None of the twenty takes a connection, and none has an exit-criteria setting. In the Job Type list each name is followed by its short description — for example EASE - RSJ : Run Symitar Job (single-threaded).
| Job type | What it does | Agent type |
|---|---|---|
| EASE - RSJ | Runs a Symitar job, single-threaded | EASE |
| EASE - RSJMULTI | Runs a Symitar job, multi-threaded | EASE |
| EASE - RSJEDIT | Runs a Symitar job with an edit file | EASE |
| EASE - MONITOR | Watches for an incoming file | EASE |
| EASE - PROMPT | Answers a single prompt | EASE |
| EASE - PROMPTSEQ | Answers a single prompt with a SEQ | EASE |
| EASE - TRANSLATE2COMMAS | Answers a single prompt whose response contains commas | EASE |
| EASE - RESET | Resets a single prompt | EASE |
| EASE - SEQ | Collects a report's sequence number and writes it to the global property SEQ-<identifier> | EASE |
| EASE - SEQ-SEND | Copies a specified SEQ to the reports directory for FTP | EASE |
| EASE - COPY-RPT-OUT | Copies a report to the letter files directory for FTP | EASE |
| EASE - COPY-DATA-TO-LTRFILE | Copies an outgoing data file to the letter files directory | EASE |
| EASE - COPY-RENAME-LTRFILE-OUT | Copies or renames a letter file for FTP, chosen by Action | EASE |
| EASE - MOVE-LTRFILE-TO-DATA | Moves an incoming letter file to the data files directory | EASE |
| EASE - RENAME-LTRFILE-IN | Renames a letter file, removing its prefix | EASE |
| EASE - FILEPERMS | Sets a letter file's privileges to 774 | EASE |
| EASE - RUN-FTP-OUT | FTPs a letter file off Symitar | EASE |
| EASE - BUNDLE-RSJEDIT | Not supported yet — fails at start. In Classic, MONITOR then RSJEDIT | EASE |
| EASE - BUNDLE-SEQ-FTP | Not supported yet — fails at start. In Classic, SEQ, COPY-RPT-OUT then RUN-FTP-OUT | EASE |
| EASE - BUNDLE-SEQ-PROMPT | Not supported yet — fails at start. In Classic, SEQ then PROMPT | EASE |
The three BUNDLE types ship so that a migrated job keeps its field values; a job of one of those types fails as soon as it starts, with a message telling you to model the bundled steps as separate EASE jobs. See EASE jobs.
File Transfer
File transfer — legacy
| Job type | Plugin | What it does | Agent type |
|---|---|---|---|
| SMAFT File Transfer | SMAFT File Transfer | Moves a file between any two file-transfer-capable legacy machines, in either direction. You name a source and a destination machine, and Start Transfer On decides which of the two runs the job | Windows, UNIX or z/OS LSAM |
| OpCon MFT Transfer | OpCon MFT | Downloads files from one endpoint on an OpCon MFT agent, optionally compresses, decompresses, encrypts, decrypts or renames them, and uploads them to another endpoint on the same agent | OpCon MFT |
SMAFT File Transfer is the only job type that names two machines, and the only one whose machine is derived from its own parameters rather than picked in Agent Assignment. It takes up to two batch users, one per end (a z/OS end takes none), and both machines need a file-transfer endpoint before a transfer can be built. See SMAFT File Transfer job.
OpCon MFT Transfer names one machine, picked in Agent Assignment as usual, and moves files between two endpoints configured on that agent. Its optional Compression Password is a connection rather than a typed value, and its endpoint and PGP key lists are read live from the agent. An OpCon MFT agent is reached through a relay but is not an LSAM — it has no JORS port and no file-transfer endpoint, so it can be neither end of a SMAFT transfer. See OpCon MFT Transfer job.
Categories and Availability
The category list
Nine categories are defined. Five are in use today; no shipped plugin uses the other four.
| Category | In use today |
|---|---|
| Script | Run Command, Run Script |
| Integration | UNIX/Linux LSAM, Windows LSAM, IBM i LSAM, SQL LSAM, SAP R/3 and CRM LSAM, SAP BW LSAM, z/OS LSAM, MCP LSAM, OS 2200 LSAM, OpCon RPA, EASE |
| Utility | Wait for File |
| Internal | Null Job, Workflow Container |
| File Transfer | SMAFT File Transfer, OpCon MFT |
| File | — none yet |
| Container | — none yet |
| Database | — none yet. The SQL LSAM plugin is in Integration |
| Custom | — none yet |
Note that Workflow Container is in the Internal category, not Container, and Windows - WS_FTP Pro is in Integration, not File Transfer — a job type's category follows the plugin that provides it, not the kind of work it does. The SMAFT plugin was the first to declare File Transfer; the OpCon MFT plugin is the second.
What's available to you
A job type appears in the picker only if its plugin is enabled for your organization.
| Plugin | Enabled by default? |
|---|---|
| Run Command, Run Script, Wait for File | Yes |
| Null Job, Workflow Container | Yes |
| Legacy LSAM (UNIX/Linux, Windows, IBM i, SQL, SAP R/3 and CRM, SAP BW, z/OS, MCP, OS 2200, SMAFT File Transfer) | Yes — but a job still needs a working relay and a registered LSAM agent. A transfer additionally needs a file-transfer endpoint on both machines |
| OpCon MFT | Yes — but a job still needs a working relay and a registered OpCon MFT agent, and the endpoints it names must already exist on that agent |
| OpCon RPA | Yes — but a job still needs a working relay and a registered OpCon RPA agent with its API token stored, and the task it names must already exist on that agent |
| EASE | Yes — but a job still needs a relay that reports EASE support and a registered EASE agent with its Customer Id, EASE Schedule Name and login stored |
A plugin can have several versions installed; new jobs pick up its default version. See Plugins.
Where a job can run
Each job type declares what it needs from an agent — an agent type (Universal, UNIX LSAM, Windows LSAM, IBM i LSAM, SQL LSAM, SAP R/3 and CRM, SAP BW, z/OS, MCP, OS 2200, OpCon MFT, OpCon RPA, or EASE) and sometimes a specific operating system. The platform only dispatches a job to an agent that matches, so a job type never lands somewhere it can't run. If no matching agent is available, the job can't be assigned. See Agents and pools.
- 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
- How connectors work — the connector model behind this list
- Job configuration — everything else on a job besides its type
- Plugins — enabling and versioning the plugins that supply job types
- OpCon RPA Task job — running an RPA robot, web macro or document scan from a workflow
- EASE jobs — running a job on Jack Henry's hosted EASE OpCon
- Add jobs to a workflow — using a job type in practice