I have resolved the issue. I am posting the steps I had to take to get the shouts to the powershell script to work: 1. Set the value of shout destination in the shout table as follows: [tab=30]powershell C:\<location of script>\<script name>.ps1 2. Account for the sending of the "HostID" and "Urgenc...

Does anyone have experience with defining a shout destination as a powershell script? We are currently upgrading to version 8 and migrating the server from Solaris to Windows. I have custom KORN shell scripts on my server that execute when a job sends a shout to the corresponding entry defined in th...

Hello All, To provide me with a daily list of the Control-M tasks I created a BMC job that runs right before new day and executes the following command on the Control-M/Server: ctmdbcount | grep "CMR_AJF table" | mailx -s "The count of production BMC tasks" <email_address> The body of the email I re...

I had a similar problem. The problem occurred when I wanted to move a current job to a new application->group using drag and drop in contolm desktop with the scheduling table locked. Instead of moving the job to the new application->group controlm would make a copy of the job, keeping the original j...

At one point we looked at Alarmpoint (which is now xmatters). They are a BMC partner. Their web site is:

http://www.xmatters.com/products/it-management/

To schedule a job to run on the 1st monday of every month configure the "Scheduling" tab as follows. 1. Select the 1st 7 days in the "Month Days" section (1,2,3,4,5,6,7) 2. Select "Mon" in the "Week Days" section. 3. Select "And" 3. Select all months in the "Months" section. To verify the job's sche...

sjnbilko,

To get the order id of Job B you could use this command:

ctmpsm -listall allfields |grep <job_name> | awk '{print $1}'

Hope this helps.

Ignore my earlier post, I was assuming that Job B was already executing. My solution was for two filewatches looking for the same file to be created on different servers.

I currently do this very task with a shout to a script I created called "killjob.sh": When job A finishes, it sends a shout to destination "Kill_job". The message of the shout contains the name of job B. In the steps panel of job B I added the following lines: On Statement Stmt=* Code= COMPSTAT=143 ...

The job I mentioned is also cyclical and executes every 5 minutes.

abishek,

I created a job that runs right after newday to save the previous nights ctmlog:

ctmlog list %%$PREV 0600 %%$DATE 0600 /opt/bmc/controlm/backup/ctmlog%%$PREV..txt

I had this same issue with 6.04.01.300. The job had 'ON' statements that evaluated the sysout for a word pattern. When I removed the 'ON' statement and corresponding 'DO' steps, the job status updates returned to normal.

I've created two jobs that run the CTMPSM utility. One runs the utility with the "-UPDATETABLE" parameter to hold all jobs in a scheduling table. The other one runs the utility with the "-UPDATEGROUP" parameter to hold jobs in a specific group or application. Hope this helps you.

Hi, We are also migrating from 6.1.03 (Solaris) to 6.4.01 (Solaris). The one caveat that I can tell you is to make sure you clean up any old files in the AGSTAT directory. For instance, I had my UNIX admin remove all files that did not have the current date. If you don't do this you may get an agent...