The problem is that - sometimes - you do want to use the same cond name. I have a job that relies on an input condition; if the first job doesn't run by 2 a.m. then I run a dummy job to add the condition regardless. The best way is to use the standard conditions that are generated by the Desktop - w...

If you check out this page - http://www.bmc.com/products/product-listing/control-m-self-service.html then you'll see a 6 minute video about the Self-Service option. At the bottom of that page are links to 2 PDFs with more details. Self-Service has to be paid for as an add-on (not hugely expensive bu...

Do you mean in the Job Defs? The interactive SQL shows this, for example -

SQL> select DISTINCT OWNER from CMS_JOBDEF where NODEID = 'hpitop';

OWNER
------------------------------
telalert

SQL>

Easily done but it depends on the version of Control-M that you are using ...

If the jobs get released at exactly the same time and needs to use the same QRs then the execution order will be random ... unless you use the "Priority" field on the Execution tab (a value of 99 being the highest).

Sounds like this is a case for 2 separate jobs: FW on the trigger file and then another job does the actual transfer. You probably have to do housekeeping on the trigger anyway (i.e. delete it) so it makes sense to have the trigger file perform a 'do force' on the actual FTP.

They are simply logical representations of resources. For example, I have 10 tape drives available - on the Control-M Server I create 10 Quantitative Resources called 'tape_drive'. I have 150 backup jobs and I create all with one Quantitative Resources called 'tape_drive' ... release all 150 jobs an...

In addition to that post, I use this command line method to the job in Windows - ctmfw "%%Cds_InF*_tracking_error.csv" CREATE 0 60 10 5 1440 -Agent %%CTM_NODE && FOR /F "usebackq" %%#i in (`dir /B /O:-N %%Cds_InF*_tracking_error.csv ^| findstr /i /E /M ".csv\>"`) do ctmvar -action set -var "%%%#%\CD...

Within the command line you can use a feature called conditional processing (sometimes called conditional execution). This can be used to link commands together and make them dependent on each other. A common one is this - command 1 && command 2 - the above commands will run in sequence and command ...

I'm not sure that will work ... but if you are running the job as a 'command' then adding this to the end of the line will give you a sleep if the compstat code is not equal to zero -

|| sleep 600

or

|| _sleep 600
on a Windows Agent.

You need the CD-rom with the appropriate Control-M Agent for your Unix system (and the same Control-M version as your Control-M server). The name of the Control-M Server and the port numbers to use (if not the default values) is the only thing that you will need to specify.

Depends on the server used but you should also bear in mind that "not all jobs are created equal" ... if your job uses priorities, lots of in/out conditions, calendars, resources and sets lots of variables then you'll find it loads the system a lot more than running a simple command line. Most peopl...

These tasks are all done via the Control-M Configuration Manager. For Unix it is very simple. Either convert an existing Agent to "Remote Host" or add a new Remote Host. You just need to select a convenient host from which to launch the connection to the new Remote Host (connections are made via SSH...

I believe that it is a legacy of the old VMS (DEC) systems which needed this particular execution method. I haven't heard of anyone using it other environments, although the manual says it can be used for certain types of scripts.

Windows or Unix?