The Master Configuration Server (or MCS) process – initiates two TCP connections to the agent using the Command port and Message port parameters in the Node configuration. It receives message data and commands or API requests from the agent. Message data can be system messages, performance data, resource status change messages, command responses, or responses to API requests.
There should be one ev390mcs process for each active IBM Z system. When there is no activity on the TCP connections, the ev390mcs process expects to receive a periodic heartbeat message from the agent (by default every 30 seconds, but this can be changed with the "HB" option on the TCP card in the mainframe agent's SYSIN parameter cards). If the heartbeat is not received, the connection is closed, and the connection process is re-initiated.
Different levels of program tracing is available by modifying the "HCI" value in the