3 of 3 people found this helpful
The Automation API export service to JSON format will only work if all jobs types and all job parameters (attributes) in the folder are already supported in the JSON definition. Please check Code Reference - Documentation for Control-M Automation API 9.0.00.500 - BMC Documentation for full details about supported fields for your vesion.
Therefore, if you try to export to JSON a folder with jobs you created directly from the Control-M EM Client, it is very likely that it has parameters that are not support yet in JSON, and you will get that error message. (It will work in future AAPI versions when 100% of current job parameters and all job types are supported in JSON - in fact there have been new enhancements with AAPI 0.0.18 and 126.96.36.199). If you try to export it to XML format, it will work, as Control-M XML definitions already support all job types and parameters.
To check how you can import a folder and all its jobs in JSON, you can try to create a definition in JSON, use "ctm deploy" to deploy it to Conttol-M, and then do the export to JSON operation - you will see how it works that way (that way you make sure all your job parameters will be supported, as it was created in JSON since the beginning).
Finally, as far as I know the use of Deploy Descriptors works only on JSON job definitions.