A quick way I've used is to disable and re-enable the agent from the CCM\CTM Server.

AFT is a command module (CM) that is installed on the Control-M agent, not server. The AFT CM does not have it's own ftp\sftp server but uses the host transfer protocol that it is installed on and it's being treated by the agent as just another job. I'm transferring thousands of files via already bu...

In 6.4 the start time of the jobs (running or completed) is in cmr_ajf.startrun. The from time (job def) is in cms_jobdef.fromtime

The node\node group you selected does not have AFT on it. If you installed AFT on the node be sure to do a ctmgetcm from the CTM Server to "discover" the AFT CM.

Check the log of the job, there might be some information. Might be permissions as well.

AFT has it's own ssh key you need to generate and add to authorized_hosts on the destination. The public key putty uses is the "native" OS one.

Keep Linux and use Postgres instead of Oracle. We run a huge CTM shop and have not had a single failure on Postgres. It's free light, robust and manages itself.

It might be umask related. Check the umask for the account you use to manage the agent.

I've hosted EM's on Solaris, HP-UX and Linux and it's all good - anything but Windows. Have been running on HP-UX since ecs600. For our next upgrade I'm moving the EM to Linux, the latest fixpacks for CTM 7 sorted out issues on the platform.

Thanks Derick. Looking forward to it. Hope we get to see you in action.