DEBUG in background task
2016-09-21 14:13
204 查看
Steps to
[b]debug Background task
[/b]
For debugging back-ground
task, there are few changes required to above program and FM which I have already created (Pre-requisite Points for back-ground
task)
Running a module in back-ground
task means assigning the module to separate LUW.
It can be run parallel and is an asynchronous process.
Changes required are mentioned below.
To
debug our
background task we need to switch on Do not process in debugging mode as shown below
Once we execute our program in SE38, FM will get execute in
background task and it will be assigned to a separate LUW.We can see this LUW registered in t-code SM58 and execute,
debug and delete manually.
If we do not check above check box, then LUW gets execute automatically and immediately based on attribute settings at FM level. It does not wait for user to manually execute
the same.
Before executing, let’s check in SM58.
No records so far.
Now let’s execute the program and check the same step by step.
/H to switch on system
debug and so that we can mark
Do Not Process check box
Let’s go to SM58 and refresh.
Put the cursor on below record and follow the path shown below to
debug.
After above execution process, corresponding record from SM58 will be deleted.
SM58 can be explored more to gain knowledge about different other remote debugging options.
Steps to
[b]debug Background task
[/b]
For debugging back-ground
task, there are few changes required to above program and FM which I have already created (Pre-requisite Points for back-ground
task)
Running a module in back-ground
task means assigning the module to separate LUW.
It can be run parallel and is an asynchronous process.
Changes required are mentioned below.
To
debug our
background task we need to switch on Do not process in debugging mode as shown below
Once we execute our program in SE38, FM will get execute in
background task and it will be assigned to a separate LUW.We can see this LUW registered in t-code SM58 and execute,
debug and delete manually.
If we do not check above check box, then LUW gets execute automatically and immediately based on attribute settings at FM level. It does not wait for user to manually execute
the same.
Before executing, let’s check in SM58.
No records so far.
Now let’s execute the program and check the same step by step.
/H to switch on system
debug and so that we can mark
Do Not Process check box
Let’s go to SM58 and refresh.
Put the cursor on below record and follow the path shown below to
debug.
After above execution process, corresponding record from SM58 will be deleted.
SM58 can be explored more to gain knowledge about different other remote debugging options.
相关文章推荐
- 【Multitasking】Executing a Finite-Length Task in the Background
- Error:Execution failed for task ':app:packageDebug'. > Duplicate files copied in APK META-INF/LICENS
- Executing a Finite-Length Task in the Background
- 关于adnroidStudio一直提示Task 'generateDebugSources' not found in project ':app'
- Completing a Long-Running Task in the Background(在后台完成长时间运行的任务)
- c# task run in background
- Task 'XXX' not found in root project 'BuildDemo'. Some candidates are: 'dexProductDebug'解决方案.
- _ITERATOR_DEBUG_LEVEL': value '2' doesn't match value '0' in xxx.obj
- Error:Execution failed for task ':app:processDebugResources'.
- How to debug a Private Module Assembly in DotNetNuke?
- Execution failed for task ':app:installDebug'. > com.android.builder.testing.api.DeviceException:
- Android 开发过程中遇到的问题Error:Execution failed for task ':app:processDebugManifest'
- PHP学习笔记 - 在Eclipse中使用XDebug调试代码 | Using XDebug debug code in eclipse
- How to use an ActiveX script task to create a loop in DTS
- iOS开发之后台运行调用beginBackgroundTaskWithExpirationHandler
- Working in the Background
- IOS 后台之长时间任务 beginBackgroundTaskWithExpirationHandler 申请后台十分钟 600秒
- How to Debug Enterprise Portal Code in Dynamics AX 2009
- android使用百度地图报:Error:Execution failed for task ':BaiduMap:transformNative_libsWithStripDebugSymbolFo
- Error:Execution failed for task ':app:processDebugManifest'. > Manifest merger failed with multiple