Skip to main content

Legacy LSAM connectors (UNIX/Linux, Windows, IBM i, SQL, SAP R/3, SAP BW, z/OS, MCP and OS 2200)

In briefThe legacy LSAM connectors let an OpCon Continuum workflow run work on the UNIX, Windows, IBM i, SQL, SAP R/3 and CRM, SAP BW, z/OS, Unisys MCP and Unisys OS 2200 LSAM machines you already have, through a relay. Each platform offers several job types; the relay builds what the agent needs from the job's fields, and the agent reports the outcome back.

WhereIn the workflow editor: Workflows, open the workflow, add or open a job, then the Job Definition tab › Job Type list. Every legacy LSAM job type is there — UNIX, Windows, IBM i, SQL, SAP R/3, SAP BW, z/OS, MCP and OS 2200. Its fields appear under Job Parameters, the machine under Agent Assignment, and the account under Connection. The result of a run is on the job's Summary tab, in the Termination and Agent Message rows, and what the agent reports while the job runs is in its Agent Feedback section — an SAP R/3 job's children in a Child Processes table above it.

When

  • A workflow has to drive work that already runs on an existing UNIX, Windows, IBM i or SQL LSAM machine — a command, a file transfer, a file wait, a T-SQL, Oracle or MySQL script, an SSIS package, SQL through an ODBC driver or OLE DB provider, an IBM i batch job, an existing SAP R/3 or CRM background job, an SAP BW process chain, a z/OS JCL member submitted through JES — held until its datasets, a console message, a job or task, tape units or a REXX check are ready, if you need — a z/OS started task, REXX exec or operator command, a Unisys MCP program, WFL job, EAE/AB Suite report or file copy, rename or removal, or a Unisys OS 2200 ECL runstream.
  • A z/OS job is submitted on the mainframe outside OpCon, or held there by the agent, and you want it on its schedule — a z/OS Tracked Job or z/OS Queued Job the agent's report lands on.
  • An MCP or OS 2200 job must wait for something on its own system first — a Prerun, or on OS 2200 File Dependencies, that the agent checks before it starts the job.
  • A legacy job was refused at dispatch, failed where you expected it to finish, or reported an exit code you need to interpret.
  • You are writing exit criteria, or an Exit Description or LSAM Feedback event, against what a legacy job reports.
  • A UNIX Command, SAP R/3 Job or SAP BW Process Chain failed part-way and you want to restart it at the failed step — or a z/OS Batch Job or z/OS Started Task, from a start step to an end step.
  • You want to read or fix the JCL member a z/OS Batch Job submits, or a z/OS REXX Exec's exec, without leaving Continuum — View / edit JCL.
  • Some child jobs of an SAP R/3 Job failed and you want to restart only those, from its Child Processes table.
  • You want to pick an SAP job, an application server or a process chain from the SAP system rather than type it — Search… beside SAP Job Name, Exec. Target or Process Chain Name.
  • SAP R/3 Jobs may hold SAP job numbers SAP no longer has, and you want to find and correct them before they fail with 70006 — Check SAP Job Numbers in Workflows.

Use something else when the work runs on a Universal Agent — the Run Command, Run Script and Wait for File job types — or when it moves a file between two legacy machines, which is SMAFT File Transfer.

How

  1. Make sure the relay is current and the LSAM machine is registered with it.
  2. Add a job to the workflow and choose its job type in the Job Type list.
  3. Set the machine and the job's parameters, and pick the Connection the job runs as, where the job type takes one.
  4. Add exit criteria where the job type offers them.
  5. Save, run, and read the Termination row; a dispatch refusal names the field.

The full steps are in Run commands on legacy LSAM machines.

Notes
  • Most field values are checked by the relay when the job runs, not when you save it. A refused job fails before anything reaches the machine, and the message names the field but never its value. An OS 2200 Job is checked when you save it too: the editor refuses one the agent could not be sent.
  • A blank Connection means something different on each platform; on a UNIX job, on every MCP job, and on MS SQL Job, Oracle and MySQL, it is not allowed.
  • The six SQL job types are listed under SQL - in the Job Type list, and their forms show only the fields your choices use — Script Source, Connection Option and Package Location each hide, and clear, the fields that do not apply.
  • An Oracle, MySQL or Other DB job needs SQL*Plus, the mysql client, or the ODBC driver or OLE DB provider, installed on the agent machine.
  • Fifteen job types take an exit-criteria table, and on the six SQL types, UNIX - Episys: Run JobFile, UNIX - Episys: Find Report from RSJ Output, Windows - WS_FTP Pro and Windows - File Arrival Continuum always applies it itself. IBM i jobs report a message ID instead, which becomes the job's termination description, and an SAP R/3 Job or SAP BW Process Chain reports the agent's result text, whose leading code is its exit code; when it fails, its Agent Message says what that code means. A z/OS job is judged by its agent — against the job's condition-code or return-code range and its Step Control rows, or, for a console command, finished once the command is issued — an MCP job by its agent against the fail codes you set, and an OS 2200 Job by its agent against its Completion Status rules; in each, the agent's text becomes the termination description.
Watch out
  • Newer job types and fields need a current relay. An older one refuses the job at dispatch rather than run it without them — IBM i lists, MCP preruns, z/OS Step Control, pre-runs and Restart options, and OS 2200 preruns and file dependencies included.
  • Never put a password in an Other DB connection string, where only common key names are refused, or in a MySQL user variable, which the agent's log shows. The login belongs in the batch user.
  • An IBM i File Arrival job checks for the file once unless a $@RECHKFREQ dynamic variable sets a re-check interval.
  • The machine must be an agent of the job type's own platform. A UNIX job pointed at a Windows agent is refused at dispatch with LSAM_AGENT_TYPE_MISMATCH.
  • Kill on an SAP R/3 Job is refused until the agent's Allow Kill is turned on, and on an SAP BW Process Chain it is always refused.
  • An SAP BW Process Chain's name is checked against its 25-character limit only when the job runs.
  • An MCP job or an OS 2200 Job restarts from the beginning only; a restart that names a step is refused. So does a z/OS REXX Exec or z/OS Console Command.
  • Saving JCL needs z/OS JCL Edit and a z/OS user ID assigned to you; viewing it needs Agents Execute under All workspaces and an agent with a JORS Port.
  • A z/OS job's pre-runs — dataset, message, job/task, tape and REXX — need a current relay. An older one refuses the job at dispatch, so it goes to Initialization Error instead of waiting.
  • An MCP job must name a Connection, and an MCP agent's name must end with a period.
  • Kill on an OS 2200 Job is always refused.
  • A z/OS or OS 2200 job's output can be listed only when its agent reports where it is, and only once the agent's JORS Port is set. An MCP job's can be listed while it runs, too.
  • Search… on an SAP field is there only with a Specific Agent assignment and a Primary Agent chosen, and it and Start Check on Check SAP Job Numbers need Agents Execute granted under All workspaces.