Values assigned to $ZSTRPLLIM are always at least the minimum value
Final Release Note
An attempt to assign a value to $ZSTRPLLIM that is smaller than the minimum (currently 150,000 bytes) assigns the minimum value. Previously, an initial assignment to $ZSTRPLLIM was not checked against the minimum, and a subsequent assignment added the minimum value to the requested value. Also, previously, the minimum was 100,000 bytes. [#886 (closed)]
Description
There are two issues here:
- If $ZSTRPLLIM is being set for the first time or is being increased, then the minimum size check is bypassed. This allows values less than the minimum to be set which should not happen.
- The release note for GTM-9238 for V63012 [see it at YDBTest#420 (closed)] states that if the value being assigned to $ZSTRPLLIM is less than the minimum number (defined to be 100K) then the number specified is increase by the minimum.
When considering a fix for this, we decided that this functionality that adds the minimum to the setting can cause some odd results - set the limit to 100,000 and that works but reduce it to 50K and get 150K instead. So we've made a further change to set values that are below the minimum to the minimum to avoid value changes contrary to what the user was trying to accomplish.
Draft Release Note
The new value for $ZSTRPLLIM is ALWAYS checked for being a minimum value. Also, if the new value is below the minimum, then the value is set to the minimum, which was increased from 100,000 to 150,000 to be more usable. Previously, if the value was being set for the first time or was being increased, this check was bypassed. Also, in the same situation, the minimum was ADDED to the requested value potentially causing unexpected values. Example, set $ZSTRPLLIM to 100,000 (the old minimum) and that works fine but reduce it to 50,000 and instead it went up to 150,000. With this update, setting $ZSTRPLLIM to any value less than 150,000 sets it to 150,000.