Skip to main content

Processing Variables (Legacy)

FieldDefaultValid ValuesDescription
Max number concurrent jobs101 – 500This field specifies the maximum number of jobs the LSAM is allowed to process concurrently.

- When changing the value of this field, the configuration program displays the following message at the bottom of the screen: MAX JOBS changed - Remove *SMA/CP/MCS/= files

Transmit "M" after receiving the warning message to confirm the change Refer to Update the "Max Number Concurrent Jobs" Field for additional procedures required to change this parameter.
Task level checkingN- N
- I
- T
This field enables/disables the checking of a job's subordinate tasks to determine and to display the job's status in Enterprise Manager Operation.

Note: Regardless of this setting, a task is always tested for a FailCode/Reset match.

- If N, the LSAM does not perform Task-Level Checking.
- If I, the LSAM fails the job immediately upon failure of a subordinate task.
- If T, the LSAM sets the JOB TO BE FAILED internal flag upon failure of a subordinate task. A Fail Reset match resets the JOB TO BE FAILED flag to "N".
Fail immediately on FailCodeN- Y
- N
This field determines the LSAM's behavior upon a Fail Code match for either a task or a job.

- If Y, the LSAM immediately fails the jobs upon a Fail Code match.
- If N, the LSAM sets the JOB TO BE FAILED internal flag to "Y" upon a Fail Code match. A Fail Reset match resets the JOB TO BE FAILED flag to "N".
Task completion messageF- F
- A
- N
This field determines if and when an LSAM sends a task completion message.

Note: Task-level resource utilization statistics will be returned only if and when a task completion message is sent. For more information on resource utilization statistics, refer to Resource Utilization Statistics.

- If F, the LSAM sends task completion messages for failed tasks only.
- If A, the LSAM sends task completion messages for all tasks.
- If N, the LSAM does not send task completion messages.
---- If the value is "A" or "F", the process name of the failed process and as much information as possible indicating the reason for the failure are stored within the database. The HISTORY task attribute is used to provide the failure information; values returned will be integers that correspond to the HISTORYTYPE, HISTORYCAUSE, and HISTORYREASON task attributes. Because of the excessive number of possible values and combinations for the history task attributes and the overhead required in translating them, the numeric values will not be translated to mnemonics by the LSAM. The associated meanings of these values may be found in the Unisys document, "Task Attributes Programming Reference Manual". The process name and failure information are returned in separate entries immediately following the job status description entry. This information will be visible in Enterprise Manager Operation > Job Information > Configuration > Operations Related Information.
Send Fail/Reset messageA- A
- F
- R
- N
This field enables/disables messaging during job processing to indicate Fail Code/Fail Reset matches.

- The LSAM sends messages to Enterprise Manager Operation.
- If A, the LSAM sends messages upon a Fail Code/Fail Reset match.
- If F, the LSAM sends messages upon a Fail Code match.
- If R, the LSAM sends messages upon a Fail Reset match.
- If N, the LSAM does not send messages upon a Fail Code or a Fail Reset match.
Enable StatisticsN- Y
- N
This field determines whether to return job statistics appended to job status messages.

- If Enable Statistics is N, then statistics are not returned.
- If Enable Statistics is Y, statistics are returned.
Temp file family<None>Any valid family nameThis field determines where the temporary files created by the MCP LSAM will be placed.

- If no family name is entered, the temporary files created by the MCP LSAM will be placed on the same family upon which the LSAM resides.
- If a family name is entered, temporary files created by the MCP LSAM will be placed on the specified family.
FreqN- N
- M
- U
This field determines the units of a Checkpoint Interval. Refer to User-defined Restart/Recovery Checkpoints for more information on checkpoints.

- At regular checkpoints, the LSAM saves tracking file and job array information for recovery and restart purposes.
- The automatic recovery/restart process falls back on the data from the last checkpoint.
- If N, the LSAM does not create user-defined checkpoints.
- If M, the interval unit is by minute.
- If U, the interval unit is by update to the job array.
Interval01000 – 9999This field sets the number of minutes/updates between checkpoints.
- If the Checkpoint Frequency is M, then the interval is the number of minutes between checkpoints.
- If the Checkpoint Frequency is U, then the interval is the number of job array updates between checkpoints.