Thanks a lot markf.

Thanks a lot for your answer chookgate. Do you know a document that might describe the new features for Control-M 7?

Hi there,

Does anyone know what are the differences between Control-M 6.3.01 and 7? Are there major differences? Can an admin for 6.3.01 handle release 7 as well? Will there be a lot of changes...Will training be required to understand 7?

thanks,
Alex

I've tried the autoedit variables. When it resolves them at the runtime, the job will still fail with command line longer than 512 chars.
I'm running 6.3.01. It does not have embedded scripts.

Is there a way to define a Control-M job with a very long command line (over 999 chars) without creating a script and running the script from the job?

Thank you

Thank you Walty.

Sandu

That sounds great to me Walty. I have some questions though for my education.
How do you enforce so the users don't fill in garbage when they fill in the details for the job? How do you limit the access to the tool that produces the xml? Do you have an authentication mechanism?

Thanks,
Sandu

The way I see it you need to take the info from email and put it in an xml format that can be used by deftable utility that will write to EM database. Or info from email put it in a file for ctmdefine and then run the file from any agent. Anyway you'll need to script around how to get the info from ...

Can't you use ctmcreate to submit the job to AJF? Example...Run from an agent: ctmcreate \ -TASKTYPE COMMAND \ -SCHEDTAB ABC \ -JOBNAME TEST_JOB_NAME \ -GROUP ABC \ -APPLICATION TEST \ -NODEGRP server_name \ -MEMNAME ADD9ENVQA@456A02 \ -OWNER unix_id\ -MAXRERUN 0 \ -PRIORITY AA \ -CMDLINE "ll -rt" \...

This will not work. PRECMD is not part of the job. It does not get included in the runtime of the job. Look at statistics for the job to see the elapsed time. ls command might be to quick to have the chance to kill the job before it completes. Sometimes there is a delay depending on how many you run...

If you did the whole setup correctly it should work. I would go again over the shout definition, script permissions and job definitions to see if they are correct.

Try and see if EXECTIME > 001 works instead of >1.

What does it say in the log of the job?

In the PostProc tab: When: Late Time Param: 0800 To: killjob Urgency:Urgent Message: %%ORDERID where killjob shoud be defined as a kill script in ctm_menu/Shout Destination table. e.g 11 P S killjob <abdolute_path>/killjob.sh killjob.sh script looks like: #/usr/bin/sh ctmkilljob -ORDERID $2

Thank you!