A small production server indeed

@DocGoo: just wondering how long does your query takes to complete and how many jobs you got in def_ver_jobs ?

@mauriziog: by NDP time, I was meaning how long did your NDP took to complete :p

The 'funky CAPS' behavior is most likely due to your SQL Server database being created with a case sensitive collation (ain't that great?).

As for your avg runtime, you could get it from avg_run_info table.

Cheers

By 'your SLA' I meant your client/company SLA

Anyways thanks for feeding my curiosity. Care to share your NDP time for the 60k Control-M/Server (and the quantity of ordrered jobs ordered by SYSTEM) ?

Cheers

@mauriziog: just out of curiosity:

- what's your SLA ?
- how many times per year do you reboot your server ?
- how many times per month do you restart your Control-M/Server ?

Cheers

Hosting critical software (Control-M) on a Windows server ... does that sound to you like a good idea to you honestly ? Good luck with that !

Use the 'ctmudchk' utility: 1. check if there are jobs that haven't been ordered: ctmudchk -DAILY SYSTEM -ACTION LIST 2. if the command returns some jobs, do the following: ctmudchk -DAILY SYSTEM -ACTION ORDER Note: You can use this command for any user daily and specify an ODATE if necessary. Cheers

FYI you can return a negative code on Unix aswell with a little magic and a Unix Control-M/Agent can also return negative exit codes.

Cheers

This error message is tricky and the reasons very different. If you want to identify the "real reasons", give us some further details:

- Control-M/Agent version
- Operating System
- Exit code
- The full log of your job

Control-M Enterprise Manager and Control-M/Server are always packaged on different CDs in every 6.x versions (aka 6.1.01 up to 6.4.01). Version 7.00 is the first version to propose a full package with every single element of the infrastructure on the same CD (DROST.7.0.00_%ARCH%.iso) aside from the ...

Ok donc les changements vis à vis de l'ancienne infrastructure sont le changement d'OS (2003 -> 2008) et la version de Control-M (6.4.01 -> 7.0.00). Le fait que certaines actions fonctionnent et d'autres non est d'autant plus étrange que toutes ces actions transitent de la même façon entre les clien...

Even if you are not fan of such solution, it's the easiest. You can set this up quite quickly with the mass update utility or by modifying exporting-> modifying -> importing the XML .

Short answer is: you don't. At least the product does not inform you natively. If you want to detect this kind of events, you'll have to check this out yourself.

Quelques questions: 1. Sur quelle architecture était hébergée la version 6.3.01 (os/ram/database) 2. Quel est le fixpack appliqué sur ton serveur Control-M (CTMSV/CTMEM/CTMAG) 3. Les usagers ont-ils tous la même version de fixpack sur le Control-M/EM GUI (OS/FIXPACK) ? Si ce n'est pas le cas, est-ce...