Communication Parameters (COMM)
Configure the TCP/IP port, TLS settings, hostname alias, and accepted IP addresses on the SMACOMM screen to enable LSAM-to-OpCon communication.
Configure the TCP/IP port, TLS settings, hostname alias, and accepted IP addresses on the SMACOMM screen to enable LSAM-to-OpCon communication.
Configure the network and security settings the MCP Agent uses to exchange scheduling messages with the OpCon server.
An overview of the MCP Agent configuration section, covering the configuration file, all parameter groups, and procedures for common configuration tasks.
Access the SMA/MANAGER program and navigate its configuration screens to modify MCP LSAM settings.
Reference the core MCP LSAM programs installed by *SMA/INSTALL and the permanent and temporary files each program uses or creates.
Create, edit, and save records in the displays definition file that the MCP Agent uses for automated response to job display messages.
Select which displays definitions file to create or edit for automated response monitoring of job and system display messages.
Reference list of all error and informational messages generated by SMA Manager screens, with descriptions and required actions.
Create and edit file monitoring definitions that instruct the Resource Monitor to watch for file events and trigger actions or OpCon events in response.
Configure the WFL startup parameters, usercode credentials, family assignments, and OpCon authentication values on the SMAGEN screen.
Configure the WFL startup parameters for the MCP Agent and Resource Monitor, including usercodes, disk families, and OpCon external event credentials.
View the current number of display messages queued for processing by the Display Handler to identify potential response delays.
Reference pre-18.00.00 MCP LSAM procedures for configuration, startup, shutdown, and feature management that have been superseded by SMA/MANAGER.
Enable and disable debug mode for the MCP Agent to capture diagnostic information for troubleshooting with SMA Technologies Support.
Start or stop the MCP Agent and optionally the Resource Monitor using the INITLSAM and STOPLSAM screens.
Look up MCP LSAM status messages forwarded to the SAM and supporting services to diagnose job and LSAM behavior in Enterprise Manager Operation.
Review documented MCP LSAM known issues and their workarounds, including FTAgent compatibility, startup errors caused by concurrent jobs changes, and JORS limitations.
Review and update the MCP LSAM configuration file to set communication options and activate optional features before starting the agent.
Start, monitor, and stop the MCP LSAM and its optional processes using the SMA/MANAGER INITLSAM, STATUS, and STOPLSAM screens.
Enable and configure Automated Response, Job Adoption, File Monitor, JORS, SMA File Transfer, and MSGIN settings on the SMAOPT screen.
Enable and configure optional MCP Agent features including Automated Response, Job Adoption, File Monitor, Resource Monitor, JORS, SMA File Transfer, and MSGIN.
Reference the optional MCP LSAM programs and their associated files that support features such as File Monitor, JORS, File Transfer, Automated Response, and MSGIN.
Gather and submit MCP LSAM debug information to SMA Technologies support for timely issue resolution.
Set concurrency limits, job failure determination logic, task-completion messaging, checkpoint behavior, and temporary file location on the SMAVAR screen.
Configure job concurrency limits, failure detection rules, task completion reporting, checkpoint frequency, and temporary file placement for the MCP Agent.
Instruct the running MCP Agent and its monitors to reload configuration, display, file, or performance definitions without a full restart.
Start or stop the MCP Resource Monitor independently of the MCP Agent when it is configured to run in its own separate WFL.
Create and edit resource monitoring definitions that instruct the Resource Monitor to watch system performance metrics and trigger actions or OpCon events in response.
Select and restore a recent backup of MCP Agent configuration or definitions files when a production file needs to be rolled back.
Understand and configure how the MCP LSAM determines job success or failure using the JOB TO BE FAILED flag, Fail Codes, Fail Resets, and task-level checking.
An overview of the SMA/MANAGER program, the MCP-based interface used to configure the LSAM and perform operational tasks.
View the current operational status of all MCP Agent modules for this instance, including mix numbers, process status, priority, release ID, and process name.
Reference the Transaction Server (COMS) Utility entries created during MCP Agent installation, which must not be modified or deleted without SMA Technologies guidance.
Remove LSAM checkpoint and tracking files and restart the agent after changing the maximum concurrent jobs configuration value.