Skip to main content

Run commands on legacy LSAM machines

In briefThe legacy LSAM job types let a Continuum workflow run work on the UNIX, Windows, IBM i, SQL, SAP R/3 and CRM, SAP BW, z/OS, MCP and OS 2200 LSAM machines you already have, through a relay. You pick a job type, the machine and the batch user it runs as, where it takes one, and fill in the fields that type asks for; the relay builds what the agent needs, and the agent reports the outcome.

Use them when existing automation on an LSAM machine has to take part in a workflow.

Notes
  • Fifteen job types take exit criteria; write them against the code the agent actually reports. On the six SQL types, on UNIX - Episys: Run JobFile and Find Report from RSJ Output, on Windows - WS_FTP Pro and on Windows - File Arrival, Continuum always evaluates the table itself. IBM i types have none: read the message ID in Termination, and use a message monitor to act on what a job raises. An SAP R/3 Job or SAP BW Process Chain has none either: its Termination is the agent's result text, and a failed one's Agent Message explains the code. A z/OS job is judged by its agent against its condition-code or return-code range and Step Control rows, or finishes once its 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, Termination is the agent's text.
  • Most values are checked when the job runs, not when you save it. A refused job fails before it reaches the machine, and the message names the field.
  • A blank batch user means the agent's service account on Windows, MS SQL Script, MS SQL DTExec and Other DB, and the job description's default user on IBM i. UNIX, MS SQL Job, Oracle, MySQL and MCP jobs need one.
  • Oracle, MySQL and Other DB need SQL*Plus, the mysql client, or the ODBC driver or OLE DB provider, on the SQL LSAM machine.
Watch out
  • Several features need a current relay — the IBM i lists, the MCP and OS 2200 preruns, the z/OS pre-runs, step control and restart options, the newer IBM i and SQL job types, and the advanced exit-criteria forms. A relay that cannot send what the job carries is refused it, and the job goes to Initialization Error.
  • Never put a password in an Other DB connection string or a MySQL user variable; keep the login in the batch user.
  • 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 name over 25 characters saves, and is refused when the job runs.
  • A z/OS REXX Exec or Console Command restarts from the beginning only; a z/OS Batch Job or Started Task can restart on a range of steps. z/OS names are checked only when the job runs.
  • Saving JCL needs z/OS JCL Edit and a z/OS user ID assigned to you.
  • An MCP job restarts from the beginning only, and its values are checked only when it runs.
  • An OS 2200 Job restarts from the beginning only and cannot be killed. Its values are checked when you save it, and again, once any property token is resolved, when it runs.
  • An IBM i File Arrival job checks once unless a $@RECHKFREQ dynamic variable tells it to keep watching.