I would guess it has something to do with / in unix is a function, not a "letter" try to use // instead

You can create a condition via PRECMD by

%%PRECMD ctmcontb -ADD condition-ok ODAT

ofc you need an agent on the target system

/Hagar

You can use ctmaftacc (or ctmaftacc.bat) to manage accounts

You should be able to do that in the report facility under Active jobs.
make one report for ended OK and one for ended notok

/Hagar

I suppose you are trying to install it on a 64-bit platform.
6.4 is not supported for that.

Hi!

you need to stop the config agent else it will restart ctm for you.

shut_ca is the command for you

Hi!

Is the job waiting for the condition with a wildcard date?
In that case it might have existed in the database from a n old predecessor.
You can use ctmcontb -LIST "condition name" "*" to see if it exists with an old date. (or even with todays date)

/Hagar

Thats the way, The jobID is used to keep track of jobs in the definition part of the database and gets updated every time you uploads the job to the control-M/Server, even if that job is not changed. The OrderID is used to keep track of jobs in the Active Jobs File. Every time you order a job it get...

There were some problems if you are trying to order/force a scheduling group with hold that already exists in the EM.

And yes you can order/force a whole table from the desktop by having control-m/sched tab view and then right click the table.

Only thing I've seen in it is messages if the GUI-server has been down and the connection has been resumed.

it should also be noted that is RHEL is 64-bit you need PosgreSQL as database server.
But the upgrade to 6.4 is not much different if you go for posgreSQL referred to other databases,

The problem is that you define %%DAY as 0 every time the job runs. First I would not use a system variable for this. use %%day instead. If you want to reset the value each day you make an extra job that runs once a day before your cyclic job that sets a global variable to 0 %%\result = 0 then in you...