Also you will always need to schedule some kind of housekeeping taks on the CM Server anyway (ctmjsa, etc).

FW should see the arrival of a new file, you need to keep it re-checking. Here's an example -

ctmfw /pkgs/hpux/home/app/tmp/your_file_arrived.txt CREATE 0 60 10 5 1435

... this FW will loop for nearly 24 hours and stop once it sees the file.

It is not really necessary to back anything up if it is just the Agent upgrade. The more recent versions recognise that you have an older version of the agent installed and it should give you the option to upgrade instead of doing a full re-install, so there should be minimal impact.

We use 2 methods - 1. File Watcher is great at seeing file creation/deletion (as mentioned above) and that can then trigger Control-M jobs. 2. If you have a SNMP framework tool (Tivoli or ITO/OpenView etc) then they can send conditions through (I think the CM utility is ctm_contb) which, in turn, tr...

I have just uploaded "Control-M File Watcher Utility.doc" - a quick guide to FW. Note that it was written at the time of 6.0.1 and there are some new options with more recent releases. However the guide will get you started and will be enough for what you describe.

You have to start Configuration Agent on the CONTROL-M/Server and start the CONTROL-M Configuration Server via the emuser root_menu.

Once started all the agents should suddenly appear in the CCM gui.

Absolutely agree with Walty; unless you have a very strange environment you should go with the 'jobs/tasks' licence model. It will work out better in the long run as you will not need to maintain anything (unless BMC want to audit the number of jobs that you run, which is only a matter of a few emai...

Not sure about 6.3 but 6.4.1 definitely does if you use the dedicated PostGres DB -

SUSE Linux Enterprise Server AS, 10 - x86_64 with PostgreSQL, 8.2.4 (English Version)

64.

This is best done with a 'fine tuning' of your grep statements.

Or (if you know which job you are interested in) simply hold the job over the New Day period.

Are we talking mainframe or distributed?

The are various uses but not all fields support autoedit variables. The best way to get to know them is to setup a test job with CMD as tasktype. On the commandline type something like echo %%NODEID run the job and the output should tell you where the job was running. I use this in my shout messages...

Sorry, you'll have to more specific. I use Autoedits all the time and they are very useful. Unless you have issues on your server then there should be no limit on usage.

The SNMP stuff is easy to configure, there are only 3 system parameters to set on the Control-M side and this should allow you to send stuff across easily. With 6.3.1. the format of messages is set and they'll be a basic mirror of what appears in the EM Alerts screen. If you want something else then...