ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
z/OS: Connection from Event Monitor to Agent not possible: U02000100 Non-encrypted message of 'n.n.n.n:m' will not be processed.
Article ID: 87703
Updated On:
Products
CA Automic Workload Automation - Automation Engine
Issue/Introduction
Error Message :
U02000100 Non-encrypted message of 'n.n.n.n:m' will not be processed.
The Agent doesn’t recognize the Event Monitor as a trusted communication partner. Even though the connection is established for a local / own IP address.
A solution for this issue is to add the IP address to the “Trustable IP-Addresses” file in the Agent object. However, this causes the Agent to crash with S0C4 errors:
U02000100 Non-encrypted message of 'n.n.n.n:m' will not be processed.
When using z/OS the connection from the Event Monitor to the Agent fails and the above error message is displayed.
Investigation
When an Event Monitor is started it connects to the Agent, but the Agent rejects the connection and errors similar to these appear:
20160818/121329.608 - U02002039 Successfully established connection with '10.0.0.152:49431' (socket handle = '1').20160818/121329.609 - U02000100 Non-encrypted message of '10.0.0.152:49431' will not be processed.20160818/121339.609 - U02002040 Disconnected from '10.0.0.152:49431' (socket handle = '1(ID=6)').
The Agent doesn’t recognize the Event Monitor as a trusted communication partner. Even though the connection is established for a local / own IP address.
A solution for this issue is to add the IP address to the “Trustable IP-Addresses” file in the Agent object. However, this causes the Agent to crash with S0C4 errors:
14.23.11 S0022722 BPXP011I THREAD 122C300000000002, IN PROCESS 83952182, WAS 826826 TERMINATED DUE TO A PTHREAD QUIESCE OF TYPE 2.14.23.42 S0022722 IEA995I SYMPTOM DUMP OUTPUT 827827 SYSTEM COMPLETION CODE=0C4 REASON CODE=00000004827 TIME=14.23.10 SEQ=00521 CPU=0000 ASID=0021827 PSW AT TIME OF ERROR 078D2400 8538B796 ILC 6 INTC 04827 NO ACTIVE MODULE FOUND827 NAME=UNKNOWN827 DATA AT PSW 0538B790 - D2FFE000 F00041E0 E10041F0827 GR 0: 120CA950 1: 0008F389827 2: 00187618 3: 0538B682827 4: 11D701F0 5: 08FFFFFF827 6: 120CA950 7: 0008E120827 8: 120DBD61 9: 00000008827 A: 00186F6C B: 00000000827 C: 00185BD8 D: 00187798827 E: 12191F50 F: 121A399D827 END OF SYMPTOM DUMP14.23.42 S0022722 BPXP018I THREAD 122C1F0000000001, IN PROCESS 83952182, ENDED 828828 WITHOUT BEING UNDUBBED WITH COMPLETION CODE 840C4000828 , AND REASON CODE 00000004.
Cause
Processing exstartq trusted IP list causes agent crash. Eventmonitor visitcard socket is not accepted as trusted socket. That causes repeated unsuccesful EM connection in case IP address discovery doesn't provide IPs of other LPARs.
Environment
OS: MVS
Resolution
Fix Status: Released
Fix Version(s):
Component(s): Agent MVS
Automation Engine 11.2.3 - Available
Automation Engine 11.1.5 - Available
For Higher Versions of Automation Engine and the Agent (12.X):
Add the IP address of the host that is specified in the error in the Attributes Section of the agent in the User Interface:
Go to Client 0 -> Go to Administration Perspective -> go to Agents & Groups -> Agents -> Right-click on the agent, select "Open" -> Under the "Agent" tab -> Specify the "Trusted IPs" in the "Attributes" section.
Fix Version(s):
Component(s): Agent MVS
Automation Engine 11.2.3 - Available
Automation Engine 11.1.5 - Available
For Higher Versions of Automation Engine and the Agent (12.X):
Add the IP address of the host that is specified in the error in the Attributes Section of the agent in the User Interface:
Go to Client 0 -> Go to Administration Perspective -> go to Agents & Groups -> Agents -> Right-click on the agent, select "Open" -> Under the "Agent" tab -> Specify the "Trusted IPs" in the "Attributes" section.
Feedback
Yes
No
Powered by
