1 of 1 people found this helpful
Just a wild guess, Do you have Condition with that name already existing?
Can you try ctmcontb -DELETE dummy_tst ODAT and tell what happens?
No, I can see via the -LIST option that it does not previously exist. If you try to create one that is already there then you usually get a specific message to indicate that. I will check this out later, it's not an issue because the naming convention for the production conditions are not affected.
Have you retried the command whenever it fails i.e. with the same condition name - just to evaluate whether it might be a network issue or if ControlM is having problems.
Yes, I did check that. I'm wondering if I added something to the process to stop the users adding any old condition. It is a security concern that maybe a user (external to Control-M) would add the wrong condition and cause problems to the system.
I will check further and give feedback.