4 Replies Latest reply on May 18, 2014 5:47 PM by Mark Francome

    Ctmcontb giving "invalid option" when trying to add condition

    Mark Francome
      Share:|


      Hi, I have a user who uses a script to add a condition to the Control-M Server via the ctmcontb agent utility. We had some problems with the Agent but now it's ok but we wanted to test that ctmcontb was working ok. The strange thing is, certain condition names are rejected as a bad command, e.g. -

       

      j:\>ctmcontb -ADD dummy_tst ODAT
      Output:
      Invalid option -ADD.

      usage:
      ctmcontb -LIST <Condition Name> <Condition Date> [-OUTPUT <Output file name>][-FULLDETAILS]
      ctmcontb -LISTNOWILD <Condition Name> <Condition Date> [-OUTPUT <Output file name>][-FULLDETAILS]
      ctmcontb -XML <Condition Name> <Condition Date>
      ctmcontb -ADD <Condition Name> <Condition Date>
      ctmcontb -DELETE <Condition Name> <Condition Date>
      ctmcontb -DELETENOWILD <Condition Name> <Condition Date>
      ctmcontb -DELETEFROM <Condition Name> <From Date> <To Date>

      Result: Failure.

       

      whereas other names work fine -

       

      j:\>ctmcontb -ADD eric_dum_test_msg ODAT
      Output:
      CONDITION:eric_dum_test_msg DATE:0515 added

      Result: Success.

       

      I checked the ctmlog and the initial (failing) command does not reach the server. I have security switched but there are no limitations on the conditions that a user can add and the manual says that the only limitation on condition names is that they cannot be longer than 255 characters.