Communication Parameters (Legacy)
Field | Default | Valid Values | Description |
---|---|---|---|
OpCon port | 03100 | 0 – 65535 | This field specifies the TCP/IP port number that will be used for communication between the LSAM and SMANetCom. |
Secure? | N | N | This field specifies whether communications with the SAM-SS are to be secured using TLS. |
Key | SMALSAM | Any valid sockets key | This configuration variable must correspond to a Sockets Key defined in the Trusted Keys store of MCP Cryptographic Services. A valid certificate is also required. - Use MCP Cryptographic Services to create a Sockets Key, associate it with the usercode under which you will run the MCP LSAM, and generate a certificate request. Once a signed certificate has been received, install it for this key. - The same key may be used for multiple instances of the MCP LSAM. |
Allow self-signed certificates? | N | - Y - N | This field specifies whether to allow the use of self-signed certificates in the scheduling and View Job Output (JORS) TLS protocols. |
Idle timer | 030 | 1 – 300 | This field defines the number of seconds the LSAM processes wait before checking for incoming messages from SMANetCom or other LSAM processes. - A low idle timer value results in faster response(s) by LSAM processes and more prompt delivery of job status messages and external events to SAM-SS. - A high idle time value results in lower CPU utilization since less processing is necessary. Note: When messages accumulate, *SMA/DISPLAY/HANDLER retrieves display messages more frequently (than the configured time); however, when the number of messages lessens, the idle timer resets to the configured value. |
Hostname alias | <None> | Any valid hostname | This field allows you to specify an alias for the LSAM. - If no alias is entered, the BNA hostname must be entered for the Machine in the Enterprise Manager. - If multiple LSAMs are in use, additional LSAMs require an alias. - If an alias is entered, the same alias must be entered for the Machine in the Enterprise Manager and in the Hosts file on the OpCon application server. - The alias (or BNA hostname) must be followed with a period (.) when defining a Machine in Administration of the Enterprise Manager. - The alias (or BNA hostname) must also be followed with a period (.) when defining a Machine in the Hosts file of the OpCon application server. The alias must not be followed by a period when defined in the *SMA/CONFIG/xxx program. |
Accept messages from IP addresses | ALL | - ALL - Any valid dotted decimal IP address | This field allows you to specify up to five different TCP/IP addresses as machines from which the LSAM accepts messages. |