Hi olivier2c, Here is the solution for this. Set maximum rerun under execution tab to 1 In step tab of job On stmt=* CODE= COMPSTAT>0 Do = rerun On stmt=* CODE=RERUNNO=1 Do Condition = JOB-OK ODAT + Also you need to out condition under condition tab , so if job completed ok it will add the condition...

Hi Nero1981, you need to update the General parameters in Control-M/EM parameters through CCM SnmpSendActive =1 SnmpHost = hostname SendSnmp =1 you need to get in touch with your system admin for snmp host configuration to send alert to destination Alternatively there is a way of sending alert to pa...

Hi olivier2c, what I understand your requirement , you want to re-run a job once it is completed OK and want to add condition . You need to schedule a job with Maximum Rerun value =1 under Execution tab ( to restrict rerun only only once ) Under Step tab On Stmt=* Code =OK Do Rerun Do Condition Name...

Hi jstarkw, You can use a LATE SUBMIT shout to Thursday Job, to notify Operation team , if Thursday job does not get started on time . and moreover you can ask Application/development team to notify monitoring team to update on status of failed job so that they can either rerun or force completed it...

yes for windows agent you need to stop and start the services from service panel in windows Sometime on CCM it takes time to reflect the status of agent status however it does not affect anything , as its showing in your output of commands ag_diag_comm and ctm_diag_comm --- Recycling agent form CCM ...

This error indicate that load balancing is set to XAL in BMC control-M for SAP configuration --- You need to change the load balancing algorithm from XAL to SAP default using CCM Go CCM right click on CM (SAP) for the problematic agent/host and select configuration management to change the load bala...

Hi anirudhp, Create a Dummy Job - D which is running when you need to run the sequence of A--> B --> C For Job D - IN() OUT (C+) -- C is dummy job which is time dependent and adding condition C+ to start the Job A Now setup would be as follow :- Then condition should be as below For job A - IN(C+) O...

Hi, If you want to run Job in sequence A--> B --> C Then condition should be as below For job A - IN() OUT(A+) -- cyclic job set for every 5 mins For job B - IN(A+) OUT(B+,A-) -- cyclic job set for every 0 mins For job C - IN(B+) OUT(B-) -- cyclic job set for every 0 mins Now A is independent and wi...

you can Change below parameter using CCM Go to Tools --> Control-M/EM System Parameters then Parameter type --> gtw Name --> MaxOldDay --> ( number of days) name --> MaxOldTotal --> ( Number of days) I prefer to have 7 days data .. because it will be save in DB and can cause DB used warning if you w...

Hi, It depends on how the parameters are set for CTM server see in system parameters on Control-M server 7) Maximum Days to Retain Sysout Files : 4 Sysout will be kept for above mentioned days , however if you want to keep the sysout of jobs for long time than you can schedule job with post -proc pr...

Hi ,

You can update the CONFG.dat file for agent in below path

~<controlm>/ctm/data/CONFIG.dat

LOCALHOST <New>
LOGICAL_AGENT_NAME <New>

Then u can verify it by ctmagcfg

after this restart the agent services to know gateway know the new name

Thanks,
Mani

you can run the following command on Control-M Server DB to get all Nodes associated to it and used in Jobs


select distinct NODEID from CMS_JOBDEF ;

Hi, If you are using same ports ( Server-to-agent & Agent-to-server ) in new version 8, then you need to update 2 parameter in agent configuration Update the config.dat file under <agent>/ctm/data First 2 parameters are CTMSHOST and CTMPERMHOSTS, here you need to replace/add the new control_M server...

HI

if you are using Control-M V7
Then u can check the DB space first , as per WD log it shows that it low in space

Go to CTM_MENU --> Option 2 --> Option 3 (Reports) --> Option 3 (Database Storage Report)

This will show the used percentage of DB, if required u can extend the sizie of your DB

its seems that SL process or TR process hung for sometime or the status directory was not updated for job id, thats the reason job hung . as soon as you held the job it initiated the CS process again and which result in status directory to change the status of job and it refreshed the SL and TR proc...