Job Output Retrieval System

Theme: Overview
Who Is It For? System Administrator

What is it?

MSJORS.exe is a Windows service used to retrieve the output (stdout/stderr along with additional information) generated by each job running through the agent. This output is helpful in identifying runtime errors that occur while jobs are running.

• Capture stdout, stderr, exit code, timing, command line, and environment variables for each job
• Archive job output logs automatically with configurable retention via ArchiveDaysToKeep

When to use

• When diagnosing why a job failed and you need to see the exact stdout, stderr, or exit code from the process.
• When you need to review the command line, arguments, or environment variables that were active when a specific job ran.

Benefits

• Job output is accessible through OpCon without requiring direct access to the agent machine's file system.
• All execution details — command line, environment, timing, exit code — are captured in a single structured log file per job.

Configuration options

The following MSLSAM.ini settings control JORS behavior. For complete setting descriptions, refer to MSLSAM.ini configuration file.

Setting	What It Does	Default	Notes
CaptureJobOutput	Enables or disables output file creation for each job. View Job Output requires this to be TRUE.	TRUE	Dynamic — no service restart needed.
JORSSocket	Port on which the JORS service listens. Must match the JORS Port Number in OpCon Advanced Machine Settings.	3110	Requires service restart.
MaxJorsFileSize	Maximum output file size in bytes that JORS retrieves for viewing. Files that exceed this limit are truncated.	65536 (64 KB)	Requires service restart.
ArchiveDaysToKeep	Number of days of job output archives to retain before automatic cleanup at midnight.	10	Dynamic — no service restart needed.

Exception handling

View Job Output returns no output or reports that output is unavailable — The JORS service is not running, or CaptureJobOutput is set to FALSE in MSLSAM.ini. Confirm that the SMA OpCon JORS for Microsoft service is running and that CaptureJobOutput is set to TRUE, then retry.

View Job Output shows truncated output for large jobs — The job output file exceeds the MaxJorsFileSize limit. Increase MaxJorsFileSize in MSLSAM.ini (maximum 52,428,800 bytes / 50 MB) and restart the JORS service. The LogComposition setting controls which portion of the file is shown when truncation occurs: START, END, or MIX (default — half from each end).

View Job Output fails for jobs on a specific machine — The JORSSocket value in MSLSAM.ini does not match the JORS Port Number in Advanced Machine Settings in OpCon. Verify both values are identical and restart the JORS service for the change to take effect.

FAQs

Do jobs still run if the JORS service is not running?
Yes. The JORS service handles only output capture and retrieval — it is independent of job execution. However, View Job Output in OpCon will not work unless JORS is running and CaptureJobOutput is set to TRUE.

Does JORS capture output for failed jobs?
Yes. When CaptureJobOutput is TRUE, JORS captures stdout, stderr, and the exit code regardless of whether the job succeeded or failed.

Glossary

JORSSocket — The port number configured in MSLSAM.ini on which the JORS service listens. This value must match the JORS Port Number in Advanced Machine Configuration — Communication Settings.

ArchiveDaysToKeep — A Debug Options setting in MSLSAM.ini that controls how many days of job output logs are retained before automatic cleanup at midnight.

note

CaptureJobOutput must be set to TRUE for the View Job Output feature to work.

The MSJORS service communicates on a specific port number configured in the MSLSAM.ini JORSSocket setting under the JORS Settings section. This value must match the JORS Port Number configured in Advanced Machine Configuration — Communication Settings.

When CaptureJobOutput is set to TRUE, JORS captures the following information for each job:

• Internal job name
• Job command line
• Job arguments
• Environment variable list
• STDOUT generated
• STDERR generated
• Job start and end time
• Job process name and PID
• Job exit code

The agent creates one log file for each job with all of the above information. The job log file is created under the JobOutput folder while the job is running and is saved under the <Output Directory>\MSLSAM\JobOutput\Archives\<Job Schedule Date> folder when the job completes.

note

The Output Directory was configured during the installation. For more information, refer to File Locations in the Concepts online help.

Archived JobOutput folders are also cleaned up based on the ArchiveDaysToKeep setting configured under Debug Options. Any output logs older than ArchiveDaysToKeep days are cleaned up at midnight.