Parameter
rdisp/softcancel_sequence
Short text
Sequence of delays for the signals sent at a softcancel
Parameter Description
This parameter specifies which actions can cancel a running session when a softcancel has been triggered (for example, using ‘Cancel Transaction’ in SAPUI). These actions are also called softcancel sequence.
The possible steps of the softcancel sequence are predefined:
• Step 1: Canceling the ABAP without a signal (effective during execution of an ABAP program). This happens by setting an ABAP control
• Step 2: Sending a softcancel signal (SIGUSR2, for example to interrupt DB queries)
• Step 3: Sending a SOFTKILL signal (SIGINT, for example to save the session and then end the work process)
• Step 4: Sending a HARDKILL signal (SIGKILL to end the work process)
The parameter specifies the time delays (separated by commas) in seconds between the different steps. The following values have a special meaning.
• The value 0 means that the next step is executed immediately
• The value -1 means that the next step (and those following) are not executed.
• Value n < 0 means that the step is repeated after a time delay of abs(n) seconds.
Example
Default setting rdisp/softcancel_sequence = 0,5,-5 means:
• Step 1 is executed
• Step 2 is then executed immediately.
• The session is not interrupted after 5 seconds, the dispatcher sends the signal SIGUSR2 every 5 seconds.
Caution
Since a HARDKILL can lead to inconsistencies, the softcancel sequence must not be changed.
Application Area
Dispatcher
Default Value
0,5,-5
Who is permitted to make changes?
Only with SAP support
Operating System Restrictions
None
Database System Restrictions
None
Values allowed
See the parameter description.
