exportdeffolder

The exportdeffolder utility exports folders from the Control-M/EM database to a text file. To export folders using the exportdeffolder utility, see Exporting folders using the exportdeffolder utility.

When the exportdeffolder utility is invoked, a file of arguments that you have created is processed. This arguments file contains statements that specify an existing folder, SMART Folders and Sub Folders. The specified folders are exported to an output file. For more information, see exportdeffolder arguments file.

The exportdeffolder utility validates the XML rule file according to the following validation versions, which can affect the validation process:

• Validation version 1: Enables you to validate the XML rules folder according to the basic validation process in Control-M/EM version 9.0.18 fix pack 2 and below. If you are using scripts that were created in Control-M/EM version 9.0.18 fix pack 2 and below, and parsed the output to search for specific messages, you can add the -vv1 switch for using validation as if it was running in Control-M/EM version 9.0.18 fix pack 2 and below. It is recommended to use this flag for a short time until you update your script to use the new messages format.
• Validation version 2: Enables you to validate the XML rules folder according to the validation process in Control-M/EM version 9.0.19 and above. By adding the switch -vv 2, the utility validates the jobs/folders, which is similar to job/folder validations in Control-M client/Control-M Web. It also validates site standards (includes warnings based on strictness levels), improved error messages descriptions, and updated field names.

NOTE: By default, the utility validates the XML file in accordance with the EmdefValidationVersion system parameter in the CCM (Validation version 2). You can change the value in the CCM without the need to add the switch to the command, which may be preferable if you have many scripts that use a particular validation version.

For an example of the two validation processes see emdef validation service error message example.

Output files created with the exportdeffolder utility can be used as import files with the deffolder utility.

For example, you can export job processing definitions to an output file using exportdeffolder, make modifications to the definitions and save the file, and use the same file as the input file when running deffolder to import the modified folder definitions into Control-M/EM database.