Commit work while debugging

[Former Member]

Hi,

In the old debugger, there was only one session and commit work used to take place after every step of execution. In the new debugger, debugging takes place in two sessions. Will the commit work take place here too after every step of execution ?

Best Regards,

Raghu

[Former Member]

hi

You can find out what's going one without debugging (if you debug, it will COMMIT, and you don't want it to) using the transaction ST05 (SQL Trace). It will show you all COMMIT WORK's and also the update task execution.you can also write Commit work in your program / exit

so that data is saved.

try doing doing this.

hope this helps

regards

Aakash Banga

[Former Member]

Hi,

I just want to know whether commit work is executed after each step of execution in the new debugger as it does in the old bebugger.

Regards,

Raghu

[Former Member]

Yes It works,

Krishna.

[Former Member]

The new debugger does NOT commit while stepping like the old one.

The new debugger operates in an external session, and therefore it does NOT perform implicit commit when navigating.

Warning: I have experienced that sometimes (but only sometimes) committing is performed, when the debugger is aborted (closed down) while debugging.

So, if you want to make a proper rollback before aborting program execution, then first choose Edit->Database->Rollback and then close debugger session.

Read more:

http://www.sap4u.org/media/userfiles/articles/pdf/26.pdf

Regards,

Poul

[Former Member]

Thanks

[marcin_cholewczuk]

Hi,

Just to clear some things. For debuger to make it possible to hold its state, there has to be reserved work proces for this need (normally when gui is launched wp is lost - there is no need to occupay it since application server has no job to do - it's waiting for user input). That's why there is a specific amount (can be changed) of wp defined for this purpose. So yes it is possible that you'll get commit after every step under debugger when this pool of free debuger wp is empty (many people are debugging in the same time). Explanation for this "commit every step" is that without dedicated wp that would be waiting for you, everytime you get back to your debugger, dynpro is being shown to you and as a result you lose wp, LUV is ended and so is your connenction between aplication server wp and DB wp. System has to do something with your changes - rollback or commit. SAP decided that it will be commit. I hope this is of any help

Best regards

Marcin Cholewczuk