The use of Trusted IPs on z/OS agents | ENDED_VANISHED
search cancel

The use of Trusted IPs on z/OS agents | ENDED_VANISHED

book

Article ID: 129839

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

After installation of a z/OS agent, jobs duration take several minutes more in One Automation than on the z/OS system.

1.) Executed Jobs return systematically the status ENDED_VANISHED.

2.) In Agents logs following messages are present:

U02000100 Non-encrypted message of '192.0.2.1:2006' will not be processed. 

The IPs that are listed here are addresses of another LPAR of the SYSPLEX. 

The communication between Members of the SYSPLEX may affect the global performance unless these Members are parted of the trusted hosts. . 

Environment

Release:
Component: AAUTEN

Resolution

Solution to avoid these two problems.

In the settings of the Z/OS Agents: Administrative Prospective ==> Agent ==> Trusted IPs

Add there the IPs of all LPAR members of the SYSPLEX, separated by semi-colon as such:   IP1;IP2;IP3