Configuring CCI on UNIX or Linux

book

Article ID: 38194

calendar_today

Updated On:

Products

CA Unicenter NSM

Issue/Introduction

Introduction:

During post-installation, you must configure CAICCI on every UNIX or Linux machine where the Unicenter Universal Job Management Agent (UUJMA) is installed. 

 

Question:

How to configure CCI on Linux or Unix?

 

Environment:

Windows, Linux/Unix

 

Answer:

To configure CAICCI on Linux or UNIX

1. Attempt to ping the job manager node. If you cannot, modify the TCP/IP setup on the Linux or UNIX machine as well as on the job manager node. This may require a DNS entry or an entry in the /etc/hosts file of the Linux or UNIX machine for the job manager or mainframe ENF node name. (Note the MVS host name.)

2. Define a connection between job manager nodes and the UUJMA machine. To define it on the UUJMA machine, use LOCAL and REMOTE statements in the CAICCI configuration file, located at $CAIGLBL0000/cci/config/<local host>/ccirmtd.prf. 

LOCAL and REMOTE statement format.

The LOCAL statement applies to the local Linux or UNIX computer, while REMOTE statements apply to the remote nodes that exchange information with CAICCI. For an explanation of the syntax and parameters in the local and remote statements, see the section LOCAL and REMOTE Statements. The definitions apply to both LOCAL and REMOTE statements.

LOCAL statement example.

The following example tells CAICCI that the TCP/IP name of the local machine is UNXSYS3 and that any remote system that wants to communicate with this system should reference UNXSYS3 as the name. Any Job Management Agent within the network can send and receive messages to this system independent of hardware or protocols if it uses the name UNXSYS3.

LOCAL=UNXSYS3 UNXSYS3 32768 STARTUP

REMOTE statement examples.

The following REMOTE statement example tells CAICCI to attempt a connection to 172.22.111.123 and to internally register MF01 as the CCI name. Any Job Management Agent within the network can send and receive messages to this system, independent of hardware or protocols, if it uses the name MF01.

REMOTE=172.22.111.123 MF01 32768 STARTUP PORT=1721

The following REMOTE statement example tells CAICCI to attempt a connection to the computer whose TCP/IP name is NTSYS1 and whose CCI name is WINNTSYS1, but also to allow any Job Management Agent to send and receive messages using the alias NT1.

REMOTE=NTSYS1 WINNTSYS1 32768 STARTUP ALIAS=NT1 

3. Issue the following command to determine the status of the Remote Server:

unifstat

A series of messages appears indicating the status of servers. If the Remote Server is running, the following message is included:

CA-CCI Remote Server <nnn> running

where nnn is the process ID of the Remote Server process.

4. Start the Remote Server if necessary. If the Remote Server is not running, issue the following command to start all processes including CAICCI:

unistart all

If you modified the ccirmtd.prf file (Step 2), and the Remote Server is active, issue the following command:

unicycle all

This command stops and starts all Unicenter processes.

5. Issue the following command to verify that CAICCI has established communications:

$CAIGLBL0000/cci/bin/ccii

The ccii command displays the CAICCI applications that are available. If Unicenter services have not been started, no entries are displayed for the local machine.

Following is an example of the output of this command:

Oid(SCHLAP2,CAI_OPR_SAFD ) Did( , ) type(L)

Oid(SCHLAP2,CAU9SET SetUp Mgr ) Did( , ) type(L)

Oid(SCHLAP2,SUBMITC Server ) Did( , ) type(L)

Oid(A44SENF,W410_SPAWN_SERVER ) Did( , ) type(R)

Oid(A44SENF,MVS_START_SERVER ) Did( , ) type(R)

Oid(A44SENF,CA7XE44 Server ) Did( , ) type(R)

Oid(A44SENF,BARRYNT2.A44SENFUL2 ) Did( , ) type(R)

Oid(A44SENF,CA7XE44 Job track ) Did( , ) type(R)

In this example, the lines with the A44SENF entries indicate that the CAICCI connection has been made to a mainframe. SCHLAP2 is the UNIX machine where UJMA is installed. 

 

Additional Information:

https://support.ca.com/irj/portal/anonymous/phpsupcontent?contentID={0FA5D97E-E0E1-48B0-A3C9-1F2ACB6642C1}

 

Environment

Release: TNGEXO05500-11.2-Management-for Microsoft Exchange
Component: