> >> Without running set command first the string matching
> >> fails on get command beacuse DPCLS prio value is different
> >> for different default builds like with --enable-autovalidator
> >> build auto-validator prio is set to 255 and if the build
> >> is a scalar than generic value is default
On 7/1/22 11:16, Stokes, Ian wrote:
>> Without running set command first the string matching
>> fails on get command beacuse DPCLS prio value is different
>> for different default builds like with --enable-autovalidator
>> build auto-validator prio is set to 255 and if the build
>> is a scalar than
> Without running set command first the string matching
> fails on get command beacuse DPCLS prio value is different
> for different default builds like with --enable-autovalidator
> build auto-validator prio is set to 255 and if the build
> is a scalar than generic value is default 255.
>
> The s
Without running set command first the string matching
fails on get command beacuse DPCLS prio value is different
for different default builds like with --enable-autovalidator
build auto-validator prio is set to 255 and if the build
is a scalar than generic value is default 255.
The same problem is
