Hi Jorge,
They use the Plex r6.0 Build 47.030.
They do not think a negative surrogate as a big problem. Surrogate gap is the most serious problem for them.
Their model is large and many surrogate gap has occurred. Therefore the remaining number is less of the surrogate that can be used, the following warning message when they update the group model is output.
GRP59923 - ***Error, high surrogates detected, 'Num.Num'***.
The group model update is assigning surrogates within
3,000,000 of the known limit, this may indicate problems
within your group model, please contact CA, Inc. Product
Support ASAP. Object ID in Num.num = n; Total shift from
local model = n; Combination exceeds 13,777,215.
* 13,777,215 is different from the actual number.
They use renum.num to fill the surrogate gap, but surrogate gap even renum.num occurs.
We would like to know how that does not generate a surrogate gap.
If we do not know it, their model surrogate is full and they will not be able to update the group model.
A negative surrogate is created in Plex 7.2 build 22.000. They also said that negative surrogate is created in Plex r6.0.
We thought to update rogue triples to the model with negative surrogates that is a bug of Plex r5.1, but the problem does not seem to be solved now either.
Regards,
Hifumi