<?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>topic Re: some important short dump example?? in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/some-important-short-dump-example/m-p/1874288#M367771</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Go to SM37 (especially in QA/PRD) and in the job name give *, user name also give *, tick the option cancel, keep the from date as blank and execute. Here you will get the list of short dumps, if basis team has not removed the old logs. You can choose each cancelled job and click on job log. Here if you double click on the job log, it will give in detail what is the name of dump, what is the reason for the dump, how to overcome the dump etc. This is a good way of understanding short dumps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One more easiest way is use ST22 transaction code. You can double click on each of the dump which will give a detailed analysis as I mentioned above.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward points if found useful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Vimal&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 26 Jan 2007 09:19:50 GMT</pubDate>
    <dc:creator>vimal_kumar4</dc:creator>
    <dc:date>2007-01-26T09:19:50Z</dc:date>
    <item>
      <title>some important short dump example??</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/some-important-short-dump-example/m-p/1874286#M367769</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi.this is arijit...plese give me some short dum example regarding Reoprting,&lt;/P&gt;&lt;P&gt;B.D.C,SCRIPT,SMARTFORMS,MODULE POOL....&lt;/P&gt;&lt;P&gt;bye&lt;/P&gt;&lt;P&gt;thanking you&lt;/P&gt;&lt;P&gt;arijit&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Jan 2007 19:49:41 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/some-important-short-dump-example/m-p/1874286#M367769</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-25T19:49:41Z</dc:date>
    </item>
    <item>
      <title>Re: some important short dump example??</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/some-important-short-dump-example/m-p/1874287#M367770</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;If the custom ABAP program (Z program) has a statement 'delete from itab', just before this statement if the internal table is empty, then it will give a dump.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the program if you have a statement X/Y and if Y happens to be zero, then it will give a dump.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the program if you keep adding amounts to a field and if the sum is greater than the size of the amount field then it will give a dump.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;These are some of the report dump that we can expect.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Vimal&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Jan 2007 07:19:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/some-important-short-dump-example/m-p/1874287#M367770</guid>
      <dc:creator>vimal_kumar4</dc:creator>
      <dc:date>2007-01-26T07:19:16Z</dc:date>
    </item>
    <item>
      <title>Re: some important short dump example??</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/some-important-short-dump-example/m-p/1874288#M367771</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Go to SM37 (especially in QA/PRD) and in the job name give *, user name also give *, tick the option cancel, keep the from date as blank and execute. Here you will get the list of short dumps, if basis team has not removed the old logs. You can choose each cancelled job and click on job log. Here if you double click on the job log, it will give in detail what is the name of dump, what is the reason for the dump, how to overcome the dump etc. This is a good way of understanding short dumps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One more easiest way is use ST22 transaction code. You can double click on each of the dump which will give a detailed analysis as I mentioned above.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward points if found useful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Vimal&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Jan 2007 09:19:50 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/some-important-short-dump-example/m-p/1874288#M367771</guid>
      <dc:creator>vimal_kumar4</dc:creator>
      <dc:date>2007-01-26T09:19:50Z</dc:date>
    </item>
  </channel>
</rss>

