SAP Basis Tech Supports

Symptom
The trace file dev_disp displays the following string (the numeric values may be different):
1.) invalid water mark -10 at level 1, see note 1148690
or:
2.)
Tue Mar 11 01:12:19 PM 2008
DIA water mark reached (30)
Tue Mar 11 01:14:31 PM 2008
DIA water mark underrun (30)
Other terms
invalid, water mark, reached, underrun, DpSetQueueWaterMarks, rdisp/softcancel_sequence, rdisp/queue_size_check_value
Reason and Prerequisites
1.) The instance profile parameter rdisp/queue_size_check_value has an incorrect syntax.
2.) There are new traces to display bottlenecks during the search for free work processes in the dispatcher.
Solution
This function is activated as of Kernel Release 700 patch level 153.
In relation to 1)
The parameter MUST have the following syntax:
rdisp/queue_size_check_value = [on,off],val0,val1,val2,val3,val4,val5,val6
Here, valX must be an integral value that is larger than 10 and smaller than 10,000.
Example:
rdisp/queue_size_check_value = on,50,30,40,500,50,500,80
or
rdisp/queue_size_check_value = off (check is deactivated)
The numeric values are threshold values for the different work process type queues (see transaction SM51 under “Goto -> Server Name -> Information -> Queue Information”).
val0: NOWP Queue
val1: DIA ”
val2: UP1 ”
val3: ENQ ”
val4: BTC ”
val5: SPO ”
val6: UP2 ”
The parameter rdisp/queue_size_check_value is set to off by default. Currently, you cannot dynamically change the parameter. The relevant ABAP enhancement for RZ11 is currently prepared and is delivered in a Support Package.
In relation to 2)
Tue Mar 11 01:12:19 PM 2008
DIA water mark reached (30)
Tue Mar 11 01:14:31 PM 2008
DIA water mark underrun (30)
The traces occur in pairs. The first entry exceeds the defined threshold of 30 waiting requests for the dispatcher dialog queue, the second entry falls again below this threshold. The difference of the time stamps indicates how long the bottleneck that is defined in such a way existed. Therefore, information about this period is also available AFTER the bottleneck occurred (if dev_disp is not overwritten). This is important, for example, for the analysis of performance problems.
The traces are also written for all other work process types if their threshold values (see parameter rdisp/queue_size_check_value above) are exceeded or not reached.

Caution:
This functional enhancement is activated in Kernel Release 700 with patch level 152. If the parameter is set in the instance parameter here, there is a core in the dispatcher in the function DpSetQueueWaterMarks. The last entry in the dispatcher trace file dev_disp is as follows:
rdisp/softcancel_sequence : -> 0,5,-1
Solution:
Remove the profile parameter rdisp/queue_size_check_val from ALL profiles or apply at leastpatch level 153.