Skip to main content

Prepare agents for connectors

In briefMost connectors run on an agent, and some need software, settings or access in place on that machine before their jobs can run. A Universal Agent needs its allowed file paths and the script interpreters your Builders use; legacy job types need a running relay, reachable LSAM machines, the right batch user, and — for the newer job types and fields — a current relay.

Notes
  • Wait for File watches only the agent's allowed directories. OPCON_ALLOWED_FILE_PATHS replaces the default list rather than adding to it, and the agent must be restarted.
  • Run Script uses the interpreter on the agent; PowerShell on Linux or macOS needs pwsh.
  • Database work runs through the SQL LSAM job types, so the client software belongs on the SQL LSAM machine, not on a Universal Agent.
  • The SAP lookups need the agent's Query Listener Port and SAP system details; z/OS JCL access needs its JORS Port. Running a lookup, or viewing JCL, needs Agents Execute under All workspaces; saving JCL also needs z/OS JCL Edit and a z/OS user ID.
Watch out
  • A relay that has not reported it can send a job's newer settings refuses the job, which goes to Initialization Error with RELAY_LSAM_FEATURE_UNSUPPORTED. Upgrade the relay first.
  • A UNIX job, every MCP job, and an MS SQL Job, Oracle or MySQL job must name a batch user.
  • A job aimed at an agent of another type is refused with LSAM_AGENT_TYPE_MISMATCH.