After AWA r12 upgrade, CCI won't recognize the Remote entries in ccirmtd.prf.

Products

• Autosys Workload Automation

Issue/Introduction

# uname -a
Linux xxxxabcd 3.10.0-1160.49.1.el7.x86_64 #1 SMP Tue Nov 9 16:09:48 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

# univer
CA Common Services 11.2

# rpm -qa | grep ^ca-
ca-cs-dia-dna-11.2.11350-1254.i586
ca-cs-utils-11.2.16336-0000.i386
ca-cs-cci-11.2.11350.0-0000.i386
ca-lic-01.90.04-00.x86_64
ca-cs-csl-11.2.11350-0000.i386
ca-cs-unicenter-utils-langpack-11.2.09253-0000.i386
ca-cs-jre-1.5.0-11.i386
ca-cs-unicenter-utils-11.2.11350.0-0000.i386
ca-certificates-2021.2.50-72.el7_9.noarch
ca-cs-cci-utils-11.2.08100-0000.i386
ca-cs-etpki-3.2.4-1.i386

# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.9 (Maipo)

# autoflags -a
0051 LINUX ORA 12.0 01.02 xxxxx8a8 xxxxxx xxxxx.xxxxl.xxx

Problem description

After upgrading AWA to r12 SP1, CCI is no longer connecting to remote nodes specified in the ccirmtd.prf file. 

 

# ccinet status
There is no information on remote CCIs

# rmtcntrl status
There is no information on remote CCIs

# cat /opt/CA/SharedComponents/ccs/cci/config/xxxxabcd/ccirmtd.prf
LOCAL = xxxxabcd xxxxabcd 32768 startup
REMOTE = TESTXXX1 TEST 32768 startup retry=60 port=7000

We expect the TEST to be listed in the "rmtcntrl status" or "ccinet status" output and it does not seem like any connection attempt is made to the REMOTE node. 

 

Environment

Release : 12.0

Component :

Resolution

The CCI in 11.3.6 and r12 are not much different from any functionality. So there is no upgrade of CCI on the 11.3.6 machine.

In this case the Mainframe CCI remote nodename was not resolvable from the Scheduler/CCI host.

After adding /etc/hosts file entry for the Mainframe node, CCI was able to pick-up and connect to remote node.