Reaching dataset limit prevents system to operate without any user feedback that the limit has been reached

This feature is to address and issue where customer has reached maximum number of datasets allowed (currently it is around 25 I believe - increased from 10 to satisfy some short term requirements).

This feature is added to address comment from PMFR request:

Finally, whatever a reasonable limit on the number of datasets should be, there should be a better way of discovering that the limit has been reached, rather than only finding out when cmxrepsvr fails to start, as described in the "Steps to Reproduce" on SDI-13699, and in SERPM-146. -

Comment from PMFR: For Enterprise SCADA 2021 the limit has already been increased to 25 datasets which addresses the [customer's] requirement in this PMFR.

We will document what the current limit is and what it really means in the Realtime Administration Guide for the distributed OASyS section.

For a future release, we’ll look at adding a usability User Story to allow ADE to warn the administrator that they are at the limit (probably requiring a BLT to check or something along those lines).

Possible solution

In 2021, there was a story to increase the hard-coded limit within the code to allow more than 25 datasets.

Note that the hard-limit is not on the number of datasets, but in how they are combined with system names inside the code. So, it is a runtime permutation limit, not limited to the size of the database

This feature is to add a BLT that can be called from ADE when datasets are being created, that will return information to warn when they are approaching this limit, or have exceeded the limit.

User documentation was created in 2021 explaining this limit, and it can be referred to by ADE when the limit is reached or exceeded.

(This TFS user story captures the history - it is misnamed as a request for an estimate, but it does contain the details of work done.)