<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Question Re: How to debug IDM script ? in Technology Q&amp;A</title>
    <link>https://community.sap.com/t5/technology-q-a/how-to-debug-idm-script/qaa-p/12742270#M4782582</link>
    <description>&lt;P&gt;Hi Welly,&lt;/P&gt;&lt;P&gt;debugging scripts is IMHO a big pain in the back as is debugging anything within IDM in general...&lt;/P&gt;&lt;P&gt;I would recommend to set the log of the according job / action tasks to a high level and remove the override.&lt;/P&gt;&lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/attachments/2167305-bildschirmfoto-vom-2023-05-26-19-09-02.png" /&gt;&lt;/P&gt;&lt;P&gt;Please note that this should be used only for a limited timeframe in order to debug something. You will find the settings in the properties of the job / action task in the tab "Logging". I unchecked "Reset log File" and increased "Max no of Error to Log in XML log:" to 25000 (default is 25).&lt;/P&gt;&lt;P&gt;Additionally you should set the Log Level to Debug on the Policy tab of your dispatcher.&lt;/P&gt;&lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/attachments/2167307-bildschirmfoto-vom-2023-05-26-19-13-52.png" /&gt;&lt;/P&gt;&lt;P&gt;Default is Info.&lt;/P&gt;&lt;P&gt;Next and most important IMHO is the "debugging" inside your script. You should use functions like uWarning to log values, parameters and return values of function calls in a way that it makes sense to you. E.g. you call internal function uProvision inside your script, so you could put it inside a uWarning like:&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;uWarning("myScriptName:: Par: " + Par + " uProvision: " + uProvision(...));&lt;BR /&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;I hope you get the picture. Please keep in mind that you should undo your debugging once you are done in order to reduce performance issues, increasing log files and the like as well as being able to transport artifacts to production.&lt;/P&gt;&lt;P&gt;As a last recommendation you could think about an own warning function that logs differently depending e.g. on a constant like LOGLEVEL. That way you can leave the debug warning in your development system and do not show them in your production. This would help for permanent debug infos that you want to have in your development system but don't want to show up in production.&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Alex&lt;/P&gt;</description>
    <pubDate>Fri, 26 May 2023 17:26:43 GMT</pubDate>
    <dc:creator>alexanderbrietz</dc:creator>
    <dc:date>2023-05-26T17:26:43Z</dc:date>
    <item>
      <title>How to debug IDM script ?</title>
      <link>https://community.sap.com/t5/technology-q-a/how-to-debug-idm-script/qaq-p/12742269</link>
      <description>&lt;P&gt;Beginner's question, how to debug IDM script ?&lt;BR /&gt;I have added the following test message, and set the different dispatchers Log level to trace , but nothing shown on DSE.log&lt;BR /&gt; uInfo("Test");&lt;/P&gt;
  &lt;P&gt; uErrMsg(0, "No problem");&lt;/P&gt;
  &lt;P&gt; uWarning("Test");&lt;/P&gt;
  &lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/attachments/2167289-2023-05-26-20-26-21-mremoteng-confconsxml-jumpbox4.jpg" /&gt;&lt;/P&gt;
  &lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/attachments/2167287-2023-05-26-20-24-24-mremoteng-confconsxml-jumpbox4.jpg" /&gt;&lt;/P&gt;
  &lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/attachments/2167288-2023-05-26-20-24-36-mremoteng-confconsxml-jumpbox4.jpg" /&gt;&lt;/P&gt;
  &lt;P&gt;Thank you and Regards&lt;/P&gt;
  &lt;P&gt;Welly&lt;/P&gt;</description>
      <pubDate>Fri, 26 May 2023 10:29:06 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/how-to-debug-idm-script/qaq-p/12742269</guid>
      <dc:creator>wsunarko</dc:creator>
      <dc:date>2023-05-26T10:29:06Z</dc:date>
    </item>
    <item>
      <title>Re: How to debug IDM script ?</title>
      <link>https://community.sap.com/t5/technology-q-a/how-to-debug-idm-script/qaa-p/12742270#M4782582</link>
      <description>&lt;P&gt;Hi Welly,&lt;/P&gt;&lt;P&gt;debugging scripts is IMHO a big pain in the back as is debugging anything within IDM in general...&lt;/P&gt;&lt;P&gt;I would recommend to set the log of the according job / action tasks to a high level and remove the override.&lt;/P&gt;&lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/attachments/2167305-bildschirmfoto-vom-2023-05-26-19-09-02.png" /&gt;&lt;/P&gt;&lt;P&gt;Please note that this should be used only for a limited timeframe in order to debug something. You will find the settings in the properties of the job / action task in the tab "Logging". I unchecked "Reset log File" and increased "Max no of Error to Log in XML log:" to 25000 (default is 25).&lt;/P&gt;&lt;P&gt;Additionally you should set the Log Level to Debug on the Policy tab of your dispatcher.&lt;/P&gt;&lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/attachments/2167307-bildschirmfoto-vom-2023-05-26-19-13-52.png" /&gt;&lt;/P&gt;&lt;P&gt;Default is Info.&lt;/P&gt;&lt;P&gt;Next and most important IMHO is the "debugging" inside your script. You should use functions like uWarning to log values, parameters and return values of function calls in a way that it makes sense to you. E.g. you call internal function uProvision inside your script, so you could put it inside a uWarning like:&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;uWarning("myScriptName:: Par: " + Par + " uProvision: " + uProvision(...));&lt;BR /&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;I hope you get the picture. Please keep in mind that you should undo your debugging once you are done in order to reduce performance issues, increasing log files and the like as well as being able to transport artifacts to production.&lt;/P&gt;&lt;P&gt;As a last recommendation you could think about an own warning function that logs differently depending e.g. on a constant like LOGLEVEL. That way you can leave the debug warning in your development system and do not show them in your production. This would help for permanent debug infos that you want to have in your development system but don't want to show up in production.&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Alex&lt;/P&gt;</description>
      <pubDate>Fri, 26 May 2023 17:26:43 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/how-to-debug-idm-script/qaa-p/12742270#M4782582</guid>
      <dc:creator>alexanderbrietz</dc:creator>
      <dc:date>2023-05-26T17:26:43Z</dc:date>
    </item>
  </channel>
</rss>

