EVO156 Invalid Connection Attempt from Different Servers - ironstream_for_servicenow_discovery_1 - 7.5

Ironstream for ServiceNow® Discovery for IBM Z® Administration

Product type
Software
Portfolio
Integrate
Product family
Ironstream
Product
Ironstream > Ironstream for ServiceNow® Discovery
Version
7.5
Language
English
Product name
Ironstream for ServiceNow® Discovery for IBM Z®
Title
Ironstream for ServiceNow® Discovery for IBM Z® Administration
First publish date
2007
Last updated
2024-11-18
Published on
2024-11-18T05:02:12.928000

Message Variables

None.

Message Description

Two Ironstream proxy server components attempted to connect to the agent's TCP/IP ports, with one server taking the Message port and the other taking the Command port. The Ironstream design requires that both ports communicate with server processes on the same Ironstream proxy server.

System Action

The TCP subtask terminates both TCP connections and resets. If the server conflict continues for more than the number of restarts allowed for the TCP subtask, then the TCP subtask will stop completely, requiring a manual restart using the INIT console command, or restarting the mainframe job.

User Action

The mainframe task's SYSPRINT will give a detailed message identifying the source of the two server connection attempts. Terminate the Ironstream processes on one of the servers. If multiple Ironstream clients are desired to connect to the same mainframe agent, then add another TCP subtask card to the SYSIN deck with different port numbers, and refer to that new set of port numbers in the EVOMF_HCI_AGENT_PORT and EVOMF_CMDS_AGENT_PORT fields in the mainframe node configuration file on the Ironstream proxy server.