In the work process overview (transaction SM50) you can perform the following tasks:
Stop an ABAP program that is running
Debug an ABAP program that is running
Cancel a process (with or without core)
End a session
Activate/deactivate the restart option after an error
Execute various functions for the process trace
You are already in the process overview (SM50) and have selected a work process using your cursor.
Note
If you want to manipulate an ABAP program, an ABAP program must be running in the selected process (you can find the report name in the Report column).
The table below describes the functions for controlling ABAP programs.
Function |
Menu path |
---|---|
Debugging You can debug a runnung ABAP program. Caution To debug a running ABAP program, you need “Debug and Replace” authorization, which is controlled by authorization object S_DEVELOP together with OBJTYPE = DEBUG and ACTVT = 02. End of the caution. More information: Debugger: |
|
Cancel program You can cancel the ABAP program; a short dump is processed. |
|
The table below describes the functions for manipulating work processes.
Function |
Menu path / pushbutton |
---|---|
Exit work process - with core Cancel work process and create a core file, this can be viewed in transaction ST11. The process is then exited at operating system level, the Dispatcher starts a new work process with a new PID (provided Restart is set to Yes). |
|
Exit work process - without core Cancel work process without creating a core file |
|
Set automatic restart Restarts work processes after cancelation: You can specify whether a process should be restarted automatically after an error has occured. The default is Yes. |
|
End Session You can end the session that is running. This does not actually end the process, it deletes the external session. |
|
The table below describes the functions for creating traces and evaluating work processes.
Function |
Menu path |
---|---|
Specify trace components You can specify which kernel components write trace information to the trace file and the trace level for logging. no trace, 1: Error trace, 2: Full trace, 3: Full trace with buffers). Only the task handler component is set as the active default, and the trace level is 1. |
|
Configure Trace Display There are 2 options under this option, Loading components and Display components. These options are useful for very large trace files where all or many of the components were active. Loading components lets you choose which components are loaded in the file; Display components lets you further limit the display. The display components are a subset of the loading components. By default, the loading components are displayed. |
|
Display trace file This displays the trace file for a selected work process. |
|
Download trace files With this function you can download one or more trace files to your local PC. More information: Saving Trace Files Locally |
|
Reset trace files You can empty the trace files here: You can choose whether to reset all files or only work process files. All Files mean all dev* files on this server. They include the traces from the gateway, dispatcher, ICM, RFC, and so on, as well as the work process traces. Caution After the trace files have been reset, the information contained in them is lost and cannot be retrieved. End of the caution. |
|
Setting Dispatcher Trace Level Here you can set the trace level for the trace file of the dispatcher dev_disp, view the file, or save it locally. |
|