Skip to main content

Respond to a failed connector job

In briefWhen a connector job fails or stalls, read its Output and the Termination text first, then find the symptom in the table for its kind of job. Problems with the job's settings go to the Builder; problems with connections, agents, drivers or the relay go to the Administrator.

Notes
  • On Run Command and Run Script, a matching exit criterion means failure, and with criteria set Fail on Error is ignored.
  • Every Universal Agent job has a fixed one-hour limit; a job stopped at the hour reports exit code 128.
  • Database work runs through the SQL LSAM job types; their failures are in the legacy LSAM table.
  • An IBM i job's Termination holds the message ID the agent reported; any failure text is in Agent Message.
  • A z/OS job's Termination holds the agent's text; the agent decides its outcome from the job's condition-code or return-code range, and a z/OS Console Command finishes once the command is issued. An MCP job's agent decides from its fail codes, and an OS 2200 Job's from its Completion Status rules; for both, Termination is the agent's text too.
Watch out
  • Many legacy features need a current relay. An older relay can refuse a dispatch, or send a File Arrival job the wrong schedule date. A job carrying IBM i lists, z/OS pre-runs, Step Control rows or restart options, an MCP prerun, or an OS 2200 prerun or file dependencies is refused with RELAY_LSAM_FEATURE_UNSUPPORTED rather than run without them.
  • Never include credentials when you escalate.