2005 Dec 21 5:46 AM
Is there any method to find out in "runtime" how much memory for internal tables is left ?
If there is, the programm could do a better reaction than runniung into a "dump"...
2005 Dec 21 5:50 AM
hi check this abstract from abap faqs:
<b>List of internal tables while debugging</b>
There can be times when you need a list of active internal tables while you are debugging ABAP code.
The first method, lets you see which table required a lot of memory
While on debug mode follow the menu path GOTO->Display condition->memory use
Select tabstrip: Memory use - ranked list
The second method provides a very detailed list
While in debug mode, choose GOTO->System Areas->internal information
A list appears on the debug screen
By default the area editbox contains a ?
Now enter DSEG in that field.
Press Return .
You will get a list of all the tables active in that program along with some other attributes.
The type and size of the records determine if they are internal tables and how many records there are.
You can play around and try the other area than DSEG, some are interesting.
Message was edited by: Hemendra Singh Manral
Is there any method to find out in "runtime" how much memory for internal tables is left ?
If there is, the programm could do a better reaction than runniung into a "dump"...
2005 Dec 21 5:50 AM
hi check this abstract from abap faqs:
<b>List of internal tables while debugging</b>
There can be times when you need a list of active internal tables while you are debugging ABAP code.
The first method, lets you see which table required a lot of memory
While on debug mode follow the menu path GOTO->Display condition->memory use
Select tabstrip: Memory use - ranked list
The second method provides a very detailed list
While in debug mode, choose GOTO->System Areas->internal information
A list appears on the debug screen
By default the area editbox contains a ?
Now enter DSEG in that field.
Press Return .
You will get a list of all the tables active in that program along with some other attributes.
The type and size of the records determine if they are internal tables and how many records there are.
You can play around and try the other area than DSEG, some are interesting.
Message was edited by: Hemendra Singh Manral
2005 Dec 21 5:54 AM
Hi !
Thnaks for that but what I need is to find that out in a running programm by itself. I'd like to react in the programm by interacting to the user or something like that...
Regards
Rainer
2005 Dec 21 6:18 AM
have you tried TX: SE30 for abap runtime analysis
here you can check the performance of your internal table
at runtime.
2005 Dec 21 6:24 AM
HI,
System Field: <u><b>SY-TOCCU</b></u>
After the statements DESCRIBE TABLE, LOOP AT, and READ TABLE, SY-TLENG contains the amount of memory allocated to the relevant internal table.
Hope this solves your problem
Regards
Sudheer
2005 Dec 21 6:32 AM
Hi !
Thanks for that...
What unit are there values .. bytes, lines... ??
Regards
Rainer
| User | Count |
|---|---|
| 3 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |