![\"\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2023\/02\/IMPORTFILE-OK-1024x560.png\")
<\/figure>\n\n\n\nImport the “problematic” xml file<\/h2>\n\n\n\n![\"\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2023\/02\/IMPORTFILE-NOTEPADLINE-1-1024x544.png\")
<\/figure>\n\n\n\nOUTPUT:<\/strong><\/p>\n\n\n\nThe error message in the popup window is clear: there is problem in the email message(character format?)<\/p>\n\n\n\n
The line and the columns is indicated in the windows it is the line 47 <\/strong>and column 140 <\/strong>we will check that by using a file text editor<\/p>\n\n\n\nCAUSE:<\/strong><\/p>\n\n\n\nUsually this error message corresponds to the case in which the DO MAIL action contains 0 character for the message part.
In our case the DO MAIL action contains the message body but is still not working<\/p>\n\n\n\n
Check the corresponding line on a file editor<\/h2>\n\n\n\n
Let’s open the xml <\/strong>file in a file editor and go to the line 47 as indicated by the popup window.<\/p>\n\n\n\nWe can clearly see that the message part is not empty, also we see some numbers at the beginning of the message ( number that are not part of the message I have input in the text field )<\/p>\n\n\n\n![\"\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2023\/02\/IMPORTFILE-NOTEPAD-1-1024x121.png\")
<\/figure>\n\n\n\nAfter some search on the excellent Support Center of BMC, I found out that this is this specific number referring to the character length of the message which is causing this import issue.<\/p>\n\n\n\n
It should correspond to the message length ( Here with have number 0002 which is not corresponding to the text length which I voluntarily added for this test purpose )<\/p>\n\n\n\n
The number of characters of our message ” Hi this is a test for the do mail notification ” is 47 chars including spaces.<\/p>\n\n\n\n
Update the xml file with corresponding values <\/h2>\n\n\n\n
So next step is to update the number to the corresponding length<\/p>\n\n\n\n
Note:<\/strong><\/p>\n\n\n\nDon’t forget to take in account the spaces in your message ,also bare in mind that you have to keep the 0 before the number otherwise it cannot work.<\/p>\n\n\n\n
Action to do in our example:<\/strong><\/p>\n\n\n\nSubstitute 0002 by 0047<\/p>\n\n\n\n![\"\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2023\/02\/47-1-1024x372.png\")
<\/figure>\n\n\n\nImport the updated xml file <\/h2>\n\n\n\n
Now we have imported the file with updated values we can try to import it an see if it is now working<\/p>\n\n\n\n![\"\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2023\/02\/IMPORNEWJOBOK-1024x401.png\")
<\/figure>\n\n\n\nAs you can see the folder\/job is now imported successfully <\/p>\n\n\n\n![\"\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2023\/02\/message-display-1-1024x401.png\")
<\/figure>\n\n\n\nCheck the do mail part in the job, this is working our message is displaying as expected<\/p>\n\n\n\n
If you have still the import message<\/h2>\n\n\n\n
Unfortunately if you still have the import issue even after updating the character number at the beginning of your message , you will have to delete the message body in the related job ( save it in a notepad for example )<\/p>\n\n\n\n![\"\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2023\/02\/empty-1024x152.png\")
<\/figure>\n\n\n\nNext step will be to import your xml <\/strong>file without the message in the do mail part,after that the import will be successful.<\/p>\n\n\n\nNote that the message field will be empty<\/p>\n\n\n\n![\"\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2023\/02\/message-paste-1024x204.png\")
<\/figure>\n\n\n\nYou will of course need to add the message manually in your jobs on Control-M planning<\/p>\n\n\n\n
Once done ,export your job definition from the planning domain to have a compliant xml <\/strong>file \ud83d\ude42<\/p>\n\n\n\n![\"\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2023\/02\/48-1024x414.png\")
<\/figure>\n\n\n\nResult:<\/strong><\/p>\n\n\n\nYour export will now work ,you can try to import it again in the planning domain to check if the importation error is fixed.<\/p>\n\n\n\n
Note:<\/strong><\/p>\n\n\n\nAs checked also with BMC <\/a><\/strong>we don’t exactly know what is the root cause of this bug , it can be corrupted at anytime ( during an export of the folder or even when you edit your xml <\/strong>export in the file editor) also it is not detected during migration as the migration toolkit doesn’t check this specific error,unfortunately that means that you can keep this issue even after an upgrade if you don’t keep out.<\/p>\n\n\n\nSo the only way to solve it is to update manually the xml <\/strong>file to get the correct character number in the message or to do the workaround with the empty field.<\/p>\n\n\n\nConclusion <\/h2>\n\n\n\n
Now you know how to fix this folder import issue , the popup windows gives precious info about where the error is located , you just have to open the xml <\/strong>file in your favorite text editor and make a quick investigation \ud83d\ude42<\/p>\n\n\n\nI hope it will be helpful and also don’t forget to follow my other blogs<\/a> and also those form my colleagues on dbi bloggers<\/a> to have more new tips and tricks on your favorites software \ud83d\ude09
<\/p>\n","protected":false},"excerpt":{"rendered":"Introduction Hello everybody,sometimes users can request us to import their job definition using xml specific file.It is quite an easy task to perform but in rare cases you can encounter some issues.When Control-m is checking the XML schema verification to import it in the planning domain you can have an windows error message explaining that […]<\/p>\n","protected":false},"author":40,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1256],"tags":[717],"type_dbi":[],"class_list":["post-23019","post","type-post","status-publish","format-standard","hentry","category-control-m","tag-control-m"],"acf":[],"yoast_head":"\n
Control-M\/EM : Import error conflict message "The format of do notify message is not valid" - dbi Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/control-m-em-import-error-conflict-message-the-format-of-do-notify-message-is-not-valid\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Control-M\/EM : Import error conflict message "The format of do notify message is not valid"\" \/>\n<meta property=\"og:description\" content=\"Introduction Hello everybody,sometimes users can request us to import their job definition using xml specific file.It is quite an easy task to perform but in rare cases you can encounter some issues.When Control-m is checking the XML schema verification to import it in the planning domain you can have an windows error message explaining that […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/control-m-em-import-error-conflict-message-the-format-of-do-notify-message-is-not-valid\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2023-02-28T17:24:12+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2023-02-28T17:24:14+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2023\/02\/IMPORTFILE-OK-1024x560.png\" \/>\n<meta name=\"author\" content=\"Middleware Team\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Middleware Team\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/control-m-em-import-error-conflict-message-the-format-of-do-notify-message-is-not-valid\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/control-m-em-import-error-conflict-message-the-format-of-do-notify-message-is-not-valid\\\/\"},\"author\":{\"name\":\"Middleware Team\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/8d8563acfc6e604cce6507f45bac0ea1\"},\"headline\":\"Control-M\\\/EM : Import error conflict message “The format of do notify message is not valid”\",\"datePublished\":\"2023-02-28T17:24:12+00:00\",\"dateModified\":\"2023-02-28T17:24:14+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/control-m-em-import-error-conflict-message-the-format-of-do-notify-message-is-not-valid\\\/\"},\"wordCount\":771,\"commentCount\":0,\"image\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/control-m-em-import-error-conflict-message-the-format-of-do-notify-message-is-not-valid\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/sites\\\/2\\\/2023\\\/02\\\/IMPORTFILE-OK-1024x560.png\",\"keywords\":[\"Control-M\"],\"articleSection\":[\"Control-M\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/control-m-em-import-error-conflict-message-the-format-of-do-notify-message-is-not-valid\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/control-m-em-import-error-conflict-message-the-format-of-do-notify-message-is-not-valid\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/control-m-em-import-error-conflict-message-the-format-of-do-notify-message-is-not-valid\\\/\",\"name\":\"Control-M\\\/EM : Import error conflict message \\\"The format of do notify message is not valid\\\" - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/control-m-em-import-error-conflict-message-the-format-of-do-notify-message-is-not-valid\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/control-m-em-import-error-conflict-message-the-format-of-do-notify-message-is-not-valid\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/sites\\\/2\\\/2023\\\/02\\\/IMPORTFILE-OK-1024x560.png\",\"datePublished\":\"2023-02-28T17:24:12+00:00\",\"dateModified\":\"2023-02-28T17:24:14+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/8d8563acfc6e604cce6507f45bac0ea1\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/control-m-em-import-error-conflict-message-the-format-of-do-notify-message-is-not-valid\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/control-m-em-import-error-conflict-message-the-format-of-do-notify-message-is-not-valid\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/control-m-em-import-error-conflict-message-the-format-of-do-notify-message-is-not-valid\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/sites\\\/2\\\/2023\\\/02\\\/IMPORTFILE-OK.png\",\"contentUrl\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/sites\\\/2\\\/2023\\\/02\\\/IMPORTFILE-OK.png\",\"width\":1312,\"height\":718},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/control-m-em-import-error-conflict-message-the-format-of-do-notify-message-is-not-valid\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Control-M\\\/EM : Import error conflict message “The format of do notify message is not valid”\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/8d8563acfc6e604cce6507f45bac0ea1\",\"name\":\"Middleware Team\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/ddcae7ba0f9d1a0e7ae707f0e689e4a9c95bb48ec49c8e6d9cc86d43f4121cb6?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/ddcae7ba0f9d1a0e7ae707f0e689e4a9c95bb48ec49c8e6d9cc86d43f4121cb6?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/ddcae7ba0f9d1a0e7ae707f0e689e4a9c95bb48ec49c8e6d9cc86d43f4121cb6?s=96&d=mm&r=g\",\"caption\":\"Middleware Team\"},\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/author\\\/middleware-team\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Control-M\/EM : Import error conflict message \"The format of do notify message is not valid\" - dbi Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/control-m-em-import-error-conflict-message-the-format-of-do-notify-message-is-not-valid\/","og_locale":"en_US","og_type":"article","og_title":"Control-M\/EM : Import error conflict message \"The format of do notify message is not valid\"","og_description":"Introduction Hello everybody,sometimes users can request us to import their job definition using xml specific file.It is quite an easy task to perform but in rare cases you can encounter some issues.When Control-m is checking the XML schema verification to import it in the planning domain you can have an windows error message explaining that […]","og_url":"https:\/\/www.dbi-services.com\/blog\/control-m-em-import-error-conflict-message-the-format-of-do-notify-message-is-not-valid\/","og_site_name":"dbi Blog","article_published_time":"2023-02-28T17:24:12+00:00","article_modified_time":"2023-02-28T17:24:14+00:00","og_image":[{"url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2023\/02\/IMPORTFILE-OK-1024x560.png","type":"","width":"","height":""}],"author":"Middleware Team","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Middleware Team","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/control-m-em-import-error-conflict-message-the-format-of-do-notify-message-is-not-valid\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/control-m-em-import-error-conflict-message-the-format-of-do-notify-message-is-not-valid\/"},"author":{"name":"Middleware Team","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d8563acfc6e604cce6507f45bac0ea1"},"headline":"Control-M\/EM : Import error conflict message “The format of do notify message is not valid”","datePublished":"2023-02-28T17:24:12+00:00","dateModified":"2023-02-28T17:24:14+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/control-m-em-import-error-conflict-message-the-format-of-do-notify-message-is-not-valid\/"},"wordCount":771,"commentCount":0,"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/control-m-em-import-error-conflict-message-the-format-of-do-notify-message-is-not-valid\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2023\/02\/IMPORTFILE-OK-1024x560.png","keywords":["Control-M"],"articleSection":["Control-M"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/control-m-em-import-error-conflict-message-the-format-of-do-notify-message-is-not-valid\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/control-m-em-import-error-conflict-message-the-format-of-do-notify-message-is-not-valid\/","url":"https:\/\/www.dbi-services.com\/blog\/control-m-em-import-error-conflict-message-the-format-of-do-notify-message-is-not-valid\/","name":"Control-M\/EM : Import error conflict message \"The format of do notify message is not valid\" - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/control-m-em-import-error-conflict-message-the-format-of-do-notify-message-is-not-valid\/#primaryimage"},"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/control-m-em-import-error-conflict-message-the-format-of-do-notify-message-is-not-valid\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2023\/02\/IMPORTFILE-OK-1024x560.png","datePublished":"2023-02-28T17:24:12+00:00","dateModified":"2023-02-28T17:24:14+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d8563acfc6e604cce6507f45bac0ea1"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/control-m-em-import-error-conflict-message-the-format-of-do-notify-message-is-not-valid\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/control-m-em-import-error-conflict-message-the-format-of-do-notify-message-is-not-valid\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbi-services.com\/blog\/control-m-em-import-error-conflict-message-the-format-of-do-notify-message-is-not-valid\/#primaryimage","url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2023\/02\/IMPORTFILE-OK.png","contentUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2023\/02\/IMPORTFILE-OK.png","width":1312,"height":718},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/control-m-em-import-error-conflict-message-the-format-of-do-notify-message-is-not-valid\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Control-M\/EM : Import error conflict message “The format of do notify message is not valid”"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d8563acfc6e604cce6507f45bac0ea1","name":"Middleware Team","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/ddcae7ba0f9d1a0e7ae707f0e689e4a9c95bb48ec49c8e6d9cc86d43f4121cb6?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/ddcae7ba0f9d1a0e7ae707f0e689e4a9c95bb48ec49c8e6d9cc86d43f4121cb6?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/ddcae7ba0f9d1a0e7ae707f0e689e4a9c95bb48ec49c8e6d9cc86d43f4121cb6?s=96&d=mm&r=g","caption":"Middleware Team"},"url":"https:\/\/www.dbi-services.com\/blog\/author\/middleware-team\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/23019","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/40"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=23019"}],"version-history":[{"count":31,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/23019\/revisions"}],"predecessor-version":[{"id":23072,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/23019\/revisions\/23072"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=23019"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=23019"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=23019"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=23019"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
<\/figure>\n\n\n\nOUTPUT:<\/strong><\/p>\n\n\n\n The error message in the popup window is clear: there is problem in the email message(character format?)<\/p>\n\n\n\n The line and the columns is indicated in the windows it is the line 47 <\/strong>and column 140 <\/strong>we will check that by using a file text editor<\/p>\n\n\n\n CAUSE:<\/strong><\/p>\n\n\n\n Usually this error message corresponds to the case in which the DO MAIL action contains 0 character for the message part. Let’s open the xml <\/strong>file in a file editor and go to the line 47 as indicated by the popup window.<\/p>\n\n\n\n We can clearly see that the message part is not empty, also we see some numbers at the beginning of the message ( number that are not part of the message I have input in the text field )<\/p>\n\n\n\n After some search on the excellent Support Center of BMC, I found out that this is this specific number referring to the character length of the message which is causing this import issue.<\/p>\n\n\n\n It should correspond to the message length ( Here with have number 0002 which is not corresponding to the text length which I voluntarily added for this test purpose )<\/p>\n\n\n\n The number of characters of our message ” Hi this is a test for the do mail notification ” is 47 chars including spaces.<\/p>\n\n\n\n So next step is to update the number to the corresponding length<\/p>\n\n\n\n Note:<\/strong><\/p>\n\n\n\n Don’t forget to take in account the spaces in your message ,also bare in mind that you have to keep the 0 before the number otherwise it cannot work.<\/p>\n\n\n\n Action to do in our example:<\/strong><\/p>\n\n\n\n Substitute 0002 by 0047<\/p>\n\n\n\n Now we have imported the file with updated values we can try to import it an see if it is now working<\/p>\n\n\n\n As you can see the folder\/job is now imported successfully <\/p>\n\n\n\n Check the do mail part in the job, this is working our message is displaying as expected<\/p>\n\n\n\n Unfortunately if you still have the import issue even after updating the character number at the beginning of your message , you will have to delete the message body in the related job ( save it in a notepad for example )<\/p>\n\n\n\n Next step will be to import your xml <\/strong>file without the message in the do mail part,after that the import will be successful.<\/p>\n\n\n\n Note that the message field will be empty<\/p>\n\n\n\n You will of course need to add the message manually in your jobs on Control-M planning<\/p>\n\n\n\n Once done ,export your job definition from the planning domain to have a compliant xml <\/strong>file \ud83d\ude42<\/p>\n\n\n\n Result:<\/strong><\/p>\n\n\n\n Your export will now work ,you can try to import it again in the planning domain to check if the importation error is fixed.<\/p>\n\n\n\n Note:<\/strong><\/p>\n\n\n\n As checked also with BMC <\/a><\/strong>we don’t exactly know what is the root cause of this bug , it can be corrupted at anytime ( during an export of the folder or even when you edit your xml <\/strong>export in the file editor) also it is not detected during migration as the migration toolkit doesn’t check this specific error,unfortunately that means that you can keep this issue even after an upgrade if you don’t keep out.<\/p>\n\n\n\n So the only way to solve it is to update manually the xml <\/strong>file to get the correct character number in the message or to do the workaround with the empty field.<\/p>\n\n\n\n Now you know how to fix this folder import issue , the popup windows gives precious info about where the error is located , you just have to open the xml <\/strong>file in your favorite text editor and make a quick investigation \ud83d\ude42<\/p>\n\n\n\n I hope it will be helpful and also don’t forget to follow my other blogs<\/a> and also those form my colleagues on dbi bloggers<\/a> to have more new tips and tricks on your favorites software \ud83d\ude09 Introduction Hello everybody,sometimes users can request us to import their job definition using xml specific file.It is quite an easy task to perform but in rare cases you can encounter some issues.When Control-m is checking the XML schema verification to import it in the planning domain you can have an windows error message explaining that […]<\/p>\n","protected":false},"author":40,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1256],"tags":[717],"type_dbi":[],"class_list":["post-23019","post","type-post","status-publish","format-standard","hentry","category-control-m","tag-control-m"],"acf":[],"yoast_head":"\n
In our case the DO MAIL action contains the message body but is still not working<\/p>\n\n\n\nCheck the corresponding line on a file editor<\/h2>\n\n\n\n
<\/figure>\n\n\n\nUpdate the xml file with corresponding values <\/h2>\n\n\n\n
<\/figure>\n\n\n\nImport the updated xml file <\/h2>\n\n\n\n
<\/figure>\n\n\n\n<\/figure>\n\n\n\nIf you have still the import message<\/h2>\n\n\n\n
<\/figure>\n\n\n\n<\/figure>\n\n\n\n<\/figure>\n\n\n\nConclusion <\/h2>\n\n\n\n
<\/p>\n","protected":false},"excerpt":{"rendered":"