Yes, the solution is to modify the EM system parameter Action_OrderForce_AuthLevel. Default is "UPDATE_ACCESS" which means that only users with update access can order jobs. Change it to "BROWSE_ACCESS" and then users with browse access will be able to order jobs.

This can be closed admins. I have an answer. Cheers.

I've found in EM authorisations (in various versions up to v9) that I need to enable an em user/group to order jobs or folders, I need to provide give the user/group Update access to the relevant folder(s) in the 'Folders' tab in EM Authorisations . Yet this provides access to make changes to folder...

ctm_agstat -list "AGENTNAME". Just insert the name of the agent (as seen in Configuration Manager) instead of AGENTNAME (and keep the quotes).

Run the agent config utility ctmagcfg and change the primary and authorized Control-M/Server to the correct value.

I've seen three digit suffixes appended to condition names in version 8. It occurs when you use any of the methods to create a condition automatically (such as drag and drop) and where either of the jobs already has a dependency. It is to ensure that every dependency is unique. This is a new 'featur...

I would make sure that I use static conditions for all jobs and not use a dummy job. Then new day processing will not affect these jobs at all, and you don't need a dummy job to start it off every day. The only catch is that you need to trigger the first job on the very first instance (not daily but...

I often notice that after installing Control-M/Server and Agent that the local agent is listed twice in the Configuration Manager (and hence defined twice in the Control-M/Server), once with the short name and once with a fully qualified name. The one with the short name is the 'default' agent and c...

Thanks for the answer, but I did do some research earlier and got the following answer, for all those who are interested: What this field does is determine what nodes you can select from when creating a node group. If you select PS8, for instance, you can only add nodes that have the control module ...

I'm wondering what the "application type filter" field in the node/host group definition does. I've seen it before as a field in the node/host group definition, and BMC say that it is where you should specify the type of job you wish to run. The version 8.0.00 doco says, "In the Application Type Fil...

Maurizog's advice works for most versions, but I've found that the xml files for version 8 differ a lot more than any other version. I would think that it would be easier to install a separate test version of Control-M/EM 6.4.01 (on any server), then use the migration utility to migrate the data to ...

Does anybody know how to report rivenbark121 for the spam? Clearly his/her messages are not on topic. Or does anybody know how to contact admins to inform them of this?

Does anybody know how to report rivenbark121 for the spam?

Hi, I don't have any example of such a script - I'm no scripting expert and it does depend on the platform. But basically it is is an IF/ELSE statement, something like this: IF $RUNCOUNT = 1 THEN ctmshout -DEST CTMSUPPORT -MESSAGE "Job failed. It will be rerun" ELSE ctmshout -DEST CTMSUPPORT -MESSAG...

That is tough, as you want to send a different message depending on the circumstance, and both need to be sent on failure. As you, and many other Control-M users know, there are no nested IFs in the Steps panel. What I would do is take the alerting out of the job itself and instead shout to a script...