I installed CTM in a site earlier this year. It took hours for installation process to build the schema. It turned out that the problem was configuration of SQL server. When just hostname was specified, it took hours to build schema. When hostname and instance was specified, installation completed i...

Do you have FP1 installed to the agent? There is a fix that seems to address the situation you are having.

I google the error ag_create_script_nm and it shows release notes of V7 FP1. (UNIX only) Control-M/Agent might fail to submit a job, and errors similar to the following appear in the debug log for the job: AS:OS_FILE_check_existence: file '/apps/saversplus/ purge/p.ksh' doesn't exist AS:ag_create_sc...

Changing the path at active job to something else just to make sure it is what it is. The path does not need to be an existing one (like /abc/def). Turn on debug at agent then rerun the job. If there is error in log saying /abc/def/myscript.sh does not exist, then something is wrong with your origin...

It does not make sense to have this problem.

Do you see this path in "File Path" of active job or of Desktop? (Maybe you have not uploaded the change ) What does log say if you change the path to something else in active job and rerun? Can you turn on debug when rerun to see what is going on?

MSSQL is not a supported DB on Linux. Installation will not offer this choice. Even if you hack it to finish installation, you are running the risk of not receiving support from BMC on any issues later. I have heard of asking Oracle for CTM/EM on Windows. I have never heard of asking MSSQL for CTM/E...

Yes, use Web Services within Business Process Integration Suite (BPIS).

I believe this is what IIS imposes as a protection mechanism. When IIS serves a folder through FTP, it does not expose the physical path and does not allow navigate outside this folder.

For admin facility, you need database client.

Yes. Since there are multiple jobs, each job will independently handle its completion status from the script.

Better to one is worse to the other. The choice is the one you are most comfortable with.

Although AS400 agent is different from UNIX/Windows agent, the idea/mechanism remains the same. If you can use a command to display the content of a file within AS400, you can do that using Control-M job to capture the output in SYSOUT.

Define a sample AS400 job in Desktop and upload into Server. Then run "ctmexdef" to extract job definition to a file suitable for "ctmcreate". This file can be the template for your other similar jobs.

Within Control-M, you can copy sysout upon NOTOK. There needs to be a running script looking for new file and act on it. A background FW process at each agent can do the looking.

set cyclic interval to 10 minute from end, and there will be wait time between two successive runs