How to find the root cause for Control-M PGSQL database went down.
Where can I find alert log of pgsql database?

Control-M Server/EM 6.4.01 on Windows 2003.
Can any one please help on providing steps for moving Control-M Server/EM 6.4.01 to Windows 2008 Server.

We are not upgrading Control-M version but only moving the Control-M from Windows 2003 to Windows 2008R2 32 bit.
I need the implementation steps for this activity.

Hi,
Did you find any solution for this?
I too have this same problem now

some of the maybe conditions(#-condition) are not loading into prerequisite condition menu so the job are waiting. I had to add manually into the prerequisite condition menu daily
any suggestion?

Can any one please share operating system compatibility list for Control-M 6.4.01

How to create different types of shout Msg or email alert according to days with the single job For example: 1. If the day is Tuesday, I want to set alert or shout if the job not submitted or completed till the time 01:30 hrs. 2. If the day is Friday, I want to set alert of shout if he job not submi...

The issue is because there was an unfortunate server reboot so the stored conditions were deleted from prerequisite condition list, so the jobs were waiting for condition. When I added the maybe (#-Condition) into the Prerequisite condition list the job started running.

Since yesterday there are some jobs waiting for condition which is hash(#) prefixed on the InCondition, but when I checked in archived jobs those same jobs were not waiting for the hash(#) prefixed on the InCondition. Would there be any chance of change in ControlM setting that makes a job to wait f...

Hi,
Any one can guide me with Steps or document for migrating Control-M 6.4.01 from Windows 2003 to Windows 2008 R2.

A job executes a procedure on SQL Server, in which controlm sysout log is successful, but the command execution of the job creates an external logfile which has actually failed.
In this situation the job should be alerted as failure.
Any ideas or help?

Hi Jstarkw,
Thanks for your reply.
Our SysAdmin team also have suggested the same that to run the control-m agent service to be 'logon as' the account not as local system.So changed the account to some other account name and the job going successful.

I need to run a windows batch file from control-m. when the batch file is executed directly from the server it works fine. But when the batch file is called from control-m some proxy issue is occuring. Is there any script that can be called from control-m in-turn it will call the batch file? or any ...