copydefcal

The copydefcal utility creates a new calendar definition in the Control-M/EM database identical to an existing calendar definition. Calendars can be copied and saved under different names in the same data center. Calendars in one data center can be copied to a different data center and saved under the same or different names. To copy existing calendar definitions using the copydefcal utility, see Copying an existing calendar using the copydefcal utility.

Multiple calendars can be selected and copied using the * wildcard character. For an explanation of how wildcards function in XML-based utilities, see Terminology.

When copydefcal is invoked, a file of arguments that you created is processed. This arguments file contains statements that specify an existing calendar or group of calendars. The specified calendars are exported to an output file. copydefcal reads arguments directly from a plain text arguments file (in XML format) instead of reading them from the command line. For more information, see copydefcal arguments file rules.

The copydefcal 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.