7 Replies Latest reply on Sep 16, 2019 2:22 PM by George Lau

    Does exportdefjob & defjob works between two different versions?

    Bhuvanesh CM
      Share This:

      Hi I have a requirement to copy selected jobs from v6.2 Control-M environment to another existing v9 Control-M environment.

       

      Can I use exportdef & defjob to export and import from V6.2 to V7 and then from v7 to v9 without using the migration tool kit?

       

      Or if I use migration toolkit can I migrate only selected jobs and without overwriting existing V9 environment jobs.

        • 1. Re: Does exportdefjob & defjob works between two different versions?
          Andrew Wong

          Hi, Bhuvanesh.

           

          There were Control-M database schema changes between v8 and v9, so pretty sure you have to use the export migration toolkit to go from v6.2 to v9.

           

          Have you opened a case to ask BMC support? They'll have the definitive answer for you.

           

          Andrew

          • 2. Re: Does exportdefjob & defjob works between two different versions?
            Keyur Patel

            Hi Bhavanesh,

             

            Migration tool kit is useful, if you want to migrate Control-M EM\Server Data from V6.4 to V9, if you want only selected job the I would suggest to use exportdefjob, you should be able to import xml from 6.4 to V 9.0, also you can create two xml file from each version and compare them to identify any deferenecs between two xml files

            Thanks

            1 of 1 people found this helpful
            • 3. Re: Does exportdefjob & defjob works between two different versions?
              MunKeong Lee

              Hi

              You will not be able to import XML files from different versions into V9. This can be easily tested by exporting workspace from earlier version e.g. V8 using the WLA GUI and then importing the exported XML file in V9. The format used by the GUI's export is exactly the same as exportdefjob. You will need to change a lot of stuff to get it to work in V9 especially if the exported XML is v7 and earlier.

              BMC don't recommend using any other way to migrate your data except to use the migration toolkit.

              Regards,

              MK

              • 4. Re: Does exportdefjob & defjob works between two different versions?
                Adriano Gomes

                Hi Bhuvanesh CM

                 

                If the set of jobs, they are ALL non Mainframe ones, and they are easily filtered from within their existing tables, you may want to consider exporting them by using "CTMEXDEF" control-m util with -ACTION "DEFINE". With this util, you will have as output a self generated script that can ben run/executed on the second v.9 env and have the exported jobs defined on the CTM server Database. As of the nature of the script execution, you can edit the generated script file in order to overcome schema data issues and errors.

                 

                Please be aware that:

                 

                if table/folder names from exported content matches exixting ones in the v9 ENV, the object will be overwritten.

                 

                ctmexdef usage: ctmexdef

                  -FOLDER             <name>

                [ -JOBNAME|-FILE_NAME <name> ]

                [  -ACTION          <DEFINE|CREATE> ]

                [  -FILE            <filename> ]

                [  -WORKING_DIR     <working directory> ]

                 

                My Best

                 

                A>Gomes

                1 of 1 people found this helpful
                • 5. Re: Does exportdefjob & defjob works between two different versions?
                  Graeme Byrnes

                  Hi there,

                  Theshort answer that no this cannot be trusted. You cannot ensure that the jobs will work (essentially because of Job parameter difference between the versions being stored differently in the Database).

                  How many jobs do you have a need to do this for? Do you have a plan to migrate to a supported version soon?

                  Cheers, Graeme.

                  1 of 1 people found this helpful
                  • 6. Re: Does exportdefjob & defjob works between two different versions?
                    Mark Francome

                    I am not entirely sure why BMC don't recommend the "manual/XML" method. When you import the jobs get validated and will fail if there's something fundamentally wrong. Obviously you need to do some checking for yourself but I have always found the XML approach to very useful when migrating tables.

                    • 7. Re: Does exportdefjob & defjob works between two different versions?
                      George Lau

                      Agree with Mark.

                       

                      Prior version XML should be compatible for import into EM of later version. Old field names remain in DTD and supported. Newly added fields not in XML will be provided with default values. It is a safe operation to import older version XML into blank workspace. If EM refuses the XML file, it may list out invalid job fields/values. Since V8, XML contains version number (e.g. VERSION="900") at folder. Simply delete all occurrences from the file, otherwise EM will refuse to import if EM does not have CTM of same version as specified in XML.

                      4 of 4 people found this helpful