DEBUGGING?

[Former Member]

HI all,

what are the following debugging modes in settings of debugging..

Update debugging

system debugging

memory monitoring

...etc

gavas.

[former_member189629]

Gavas,

System Debugging

If you set this option, the Debugger is also activated for system programs

(programs with status S in their program attributes). When you save breakpoints, the System Debugging setting is also saved.

Update Debugging

Update function modules do not run in the same user session as the program that is currently running in the ABAP Debugger.

These function modules are therefore not included in debugging.

Only if you select the Update Debugging option can you display and debug them after the COMMIT WORK.

System debugging

http://help.sap.com/saphelp_nw04/helpdata/en/ef/5f0640555ae369e10000000a155106/content.htm

UPDATE debugging is nothing but the system opens a new session the function which is being called in a UPDATE TASK mode and gets into a debug mode.

chk this

http://help.sap.com/saphelp_nw04/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm

Reward if helpful,

Karthik

[Former Member]

Hi,

System Debugging

If you set this option, the Debugger is also activated for system programs (programs with status S in their program attributes). When you save breakpoints, the System Debugging setting is also saved.

Update Debugging

Update function modules do not run in the same user session as the program that is currently running in the ABAP Debugger. These function modules are therefore not included in debugging. Only if you select the Update Debugging option can you display and debug them after the COMMIT WORK.

Normal Debugging

Normal debugging is the one we do it by the normal dynamic break points or by /H or by using stattic break points.

http://help.sap.com/saphelp_47x200/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/frameset.htm

For debugging tutorial:

http://help.sap.com/saphelp_erp2005vp/helpdata/en/5a/4ed93f130f9215e10000000a155106/frameset.htm

http://www.sapdevelopment.co.uk/tips/debug/debughome.htm

http://www.sap-basis-abap.com/sapab002.htm

Regards,

Priyanka.

[Former Member]

Hi,

System Debugging

If you set this option, the Debugger is also activated for system programs
(programs with status S in their program attributes). When you save breakpoints, the System Debugging setting is also saved.

Update Debugging

Update function modules do not run in the same user session as the program that is currently running in the ABAP Debugger.
These function modules are therefore not included in debugging.
Only if you select the Update Debugging option can you display and debug them after the COMMIT WORK.

Monitoring the Memory Management System

Use
You should monitor the SAP system during operation to check that Memory Management has the necessary resources, and that frequent paging at operating system level does not slow down the system or cause any bottlenecks.

Flow
The following tools are suitable for monitoring:

· Tune Summary (transaction st02): The current status and the memory resource usage for a specific SAP application server are displayed here. The procedure is described in Checking Roll /Paging Area and Extended Memory using Transaction ST02.

· Transaction st06 for monitoring the available swap space in the host system. See also Monitoring Memory Resources Using Transaction st06.

· CCMS Alert Monitor (transaction rz20): For more information, see the Tutorial in the CCMS Documentation.

· Overview of Users (transaction sm04): Use transaction sm04 or choose Tools ®Administration ® Monitor ® System monitoring ® User overview, and then choose Goto ® Memory to display the amount and type of memory reserved by the user contexts of all users for a specific SAP application server. See Displaying and Administrating User Modes.

· Overview of Work Processes (transaction sm50): Select the Detail button to display the memory resources that have been reserved for a certain work process. See Displaying and Controlling Work Processes.

By monitoring work processes in the SAP system (transaction sm50) or from outside the system (dpmon program at operating system level), you can determine the status of the work processes in relation to the PRIV mode. If work processes are often switched to the PRIV mode, you must increase the extended memory and/or adjust the limit for the extended memory (see Functions of the SAP Memory Management System). In this case, you must consult with SAP.

· You can evaluate this information for all the work processes by using transaction sm66.

· You can determine the Swap Space Requirements at SAP and operating system level.

Many monitoring tools are operating-system dependent. The procedures for monitoring systems on various platforms are described in the following sections:

Debugging Documents

http://www.cba.nau.edu/haney-j/CIS497/Assignments/Debugging.doc

http://help.sap.com/saphelp_nw04/helpdata/en/5a/4ed93f130f9215e10000000a155106/frameset.htm

http://help.sap.com/saphelp_47x200/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm

http://www.cba.nau.edu/haney-j/CIS497/Assignments/Debugging.doc

http://help.sap.com/saphelp_erp2005/helpdata/en/b3/d322540c3beb4ba53795784eebb680/frameset.htm

http://help.sap.com/saphelp_nw04/helpdata/en/84/1f624f4505144199e3d570cf7a9225/frameset.htm

http://help.sap.com/saphelp_bw30b/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm

http://help.sap.com/saphelp_erp2005/helpdata/en/b3/d322540c3beb4ba53795784eebb680/frameset.htm

Regards,

Padmam.

[Former Member]

Hi,

check these...

ABAP DEBUGGING

http://help.sap.com/saphelp_webas620/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9cbb7716-0a01-0010-58b1-a2d...

Debug Program scheduled Background

3 types update,normal and system debugging

check this for update debugging

If you set "Update Debbugging" you can debug the codes which works in update tusk.

SAP std often runs the routine (function or form) to update the database in update tusk mode, these routine start as soon as a commit work is done.

The commit is called at the end of the program, so you can't debug them by "normal debbugging" because it ends as soon as the program ends

or----

---

All the database updates are performed by the update work processes by calling the functions/subroutines in update tasks.

These tasks are executed after a commit work is reached in the application. By default you cannot debug these functions.

TO debug these u need to explicitly activate update debugging.

for system debugging check the below link

http://help.sap.com/saphelp_nw2004s/helpdata/en/ef/5f0640555ae369e10000000a155106/content.htm

http://help.sap.com/saphelp_47x200/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/frameset.htm

For debugging tutorial:

http://help.sap.com/saphelp_erp2005vp/helpdata/en/5a/4ed93f130f9215e10000000a155106/frameset.htm

http://www.sapdevelopment.co.uk/tips/debug/debughome.htm

http://www.sap-basis-abap.com/sapab002.htm

System Debugging

If you set this option, the Debugger is also activated for system programs (programs with status S in their program attributes). When you save breakpoints, the System Debugging setting is also saved.

Update Debugging

Update function modules do not run in the same user session as the program that is currently running in the ABAP Debugger. These function modules are therefore not included in debugging. Only if you select the Update Debugging option can you display and debug them after the COMMIT WORK.

Normal Debugging

Normal debugging is the one we do it by the normal dynamic break points or by /H or by using stattic break points.

You can switch to diffferent debuggin modes while processing.

BREAKPOINT

In the source code we set the Break-point there by clicking the stop button, the system will stop there when you execute the program.

Watchpoint

For watchpoints, we need to give some condition and when this condition is satisfied, program will stop

example : if you want to debug only

for matnr value 100 than set watch point

matnr = 100. when value reaches 100 than

program stops at that point.

more at

http://help.sap.com/saphelp_nw04/helpdata/en/c6/617cdce68c11d2b2ab080009b43351/content.htm

check these documents as well

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/abap/abap-runtime-...

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/media/uuid/f720ea47-0801-0010-f7a3-bd37d...

Thanks,

Reward If Helpful.

[Former Member]

Hi

<b>System Debugging</b>

If you set this option, the Debugger is also activated for system programs (programs with status S in their program attributes). When you save breakpoints, the System debugging setting is also saved.

<b>Update Debugging</b>

Update function modules are not processed in the same task as the program that is currently running in the Debugger. Instead, they run in an update work process. These function modules are therefore not included in debugging. Only if you select the Update debugging option can you display and debug them after the COMMIT WORK.

<b>Memory Monitoring</b>

After each ABAP statement, the system examines the roll area of the current session. This allows you to check whether neighboring memory areas have been overwritten.

You can also display the memory usage for objects, tables, references and single fields by choosing Settings &#61614; Memory Display On/Off. A distinction is made here between allocated and referenced memory. The memory actually used for each data object is also indicated.

You can display a hit list of the 25 data objects with the highest memory consumption by choosing Goto &#61614; System &#61614; System areas. You can enter the following values in the Area field:

<u>Area</u> <u>Hit list</u>

ITAB-TOP25 Displays max. 25 internal tables

OBJ-TOP25 Displays max. 25 objects

REF-TOP25 Displays max. 25 references

ALL-TOP25 Displays the 25 data objects with the highest memory consumption

<b>Reward if usefull</b>

[Former Member]

Hi

<b>Memory Monitoring with Watchpoints</b>

You can use watchpoints to display changes to the references of strings, data and object references, and internal tables. By placing an ampersand (&) in front of the object name, you can display the reference in question in hexadecimal format. With internal tables, you can also display the table header by placing an asterisk (*) at the beginning of the name.

&objectname Displays the references of strings, internal tables as well as data and object references

*itab Displays the table header of the internal table itab

<b>Transferring Breakpoints to HTTP and Update Sessions</b>

If an HTTP or update session is called from a Logical Unit of Work (LUW), new work processes are started for these new sessions. Breakpoints that were defined beforehand in the calling LUW are copied to these sessions where they can be displayed under breakpoints.

If, for example, the update module func is called via CALL FUNCTION func IN UPDATE TASK, the new work process is displayed in a second window if Update debugging was selected under Settings in the debugging mode. All the breakpoints that were set in the calling LUW can then be processed here.

<b>Reward if usedfull</b>