ControlM Performance Issues

geneglynn · Post by **geneglynn** » 17 Nov 2010 11:39

Hi

I am a newbie. We are using ControlM 6.4 in our organisation. Over the past week we have seen a decline in the performance. We have 2 locations that run the same controlM jobs. One site runs perfectly, while the other we have seen a decrease in performance. One job used take 30 mins, now it takes 5 hours. Nothing has changed. When we run the jobs manually, by this i mean from the command line, it takes 30 minutes again.

Has anyone ever experienced this or something similiar before?

thanks

philmalmaison · Post by **philmalmaison** » 19 Nov 2010 4:37

it looks like a A to S specific port number or protocol version number not taken and act by controlm server.

Regards,
Philmalmaison

geneglynn · Post by **geneglynn** » 19 Nov 2010 7:27

philmalmaison wrote:it looks like a A to S specific port number or protocol version number not taken and act by controlm server.

Regards,
Philmalmaison

Thanks and how would you go about resolving this?

philmalmaison · Post by **philmalmaison** » 23 Nov 2010 5:04

Hi,
Go on your controlm server and use the following command:
ctm_diag_comm <nodeid>

and from the agent part :
ag_diag_comm

on controlm server using the ctm_menu/parameter customisation/Default Parameters for Communicating with Agent Platforms

look at protocol version (08 for the 6.4)
look at Server to Agent port number that must be the same on the agent.

1) Polling Interval: 900
2) Communication Timeout: 120
3) Maximum Retries: 12
4) Retry Interval (Unavailable): 90
5) Server-to-Agent Port Number: 7006
6) Communication Protocol Version: 07
7) Check Interval (Available): 7200

Unavailability Shout Urgency: R
9) Persistent Connection: N
10) Maximum Concurrent Sessions: 256
11) Allow Agent Disconnection: Y
12) Session Idle Timeout: 900
13) Maximum Disconnect Time: 300

a) Modify all of the above
q) Quit

(All time parameters expressed in seconds)

Enter option or item number you wish to change: [q]:

and on the agent part do a more from ~/ctm/data/CONFIG.dat you must have same parameters on each.

CTMSHOST titi
CTMPERMHOSTS toto|titi
ALLOW_COMM_INIT Y
AGENT_DIR /var/ctmag/ctm
CM_APPL_TYPE OS
LOCALHOST titi
CODE_VERSION 610
PROTOCOL_VERSION 07
FD_NUMBER DRKAI.6.3.01
CHECKHOSTS NO
DBGLVL 0
COMM_TRACE 0
AG_LOG_ON Y
LOGICAL_AGENT_NAME sapteus2
LISTEN_INTERFACE *ANY
AUTOEDIT_INLINE Y
LOGKEEPDAYS 1
UTTIMEOUT 120
COMMRETCNT 12
COMMRETSLP 1
EVENT_TIMEOUT 60
PERSISTENT_CONNECTION N
ATCMNDATA 7005/120
AGCMNDATA 7006/120
TRACKER_EVENT_PORT 7007
AR_AG_COMM_PORT 7008/120
AR_AT_COMM_PORT 7009/120
AR_UT_COMM_PORT 7010/120
CMLIST OS | SAP | FILE_TRANS | DATABASE
AGENT_STATUS STARTED
WATCHDOG_ENABLED Y

Regards,
Philmalmaison