Implement Paging Feature on RDS Range Retrieval

Problem Description:

IBM RDS 5.2.1 (IBM LDAP server) in corporate configuration as connected to our Department’s corporate LDAP (Active Directory) receive result sets with max 1500 users. The implication is once we pass more than 1500 users in a query the result set is cut-off and any new users beyond the 1500 are not able to login to DOORS/Rational Change applications.

IBM has been able to replicate the configuration and confirmed that the parameter ‘MaxValRange’ play a role in this issue and confirmed that having that parameter value set to 1500 will limit number of users synchronized with corporate LDAP server.

Enhancement Request:

Implement requested feature on RDS Range Retrieval.

The diagram below describes how each user has a number of user properties: FirstName, LastName and so on. One of the properties, GroupMemebership may have extensive number of elements (over 1500) . In the current configuration the number of elements (elements in a property) is limited to 1500, AD will not send back a result set of more than 1500 and will cut off any exceeding elements. This behaviour results in the issue described below in the Problem Description and results in broken referential integrity inside RDS server

Adding Range Retrieval would split property elements in pages, first 1500 elements then in a next page another 1500 elements. In implementing this the MaxValRange parameter does not need to be increased above the 1500 threshold and all elements would be retrieved in subsequent pages.Enhancement Request:

Implement requested feature on RDS Range Retrieval.

The diagram below describes how each user has a number of user properties: FirstName, LastName and so on. One of the properties, GroupMemebership may have extensive number of elements (over 1500) . In the current configuration the number of elements (elements in a property) is limited to 1500, AD will not send back a result set of more than 1500 and will cut off any exceeding elements. This behaviour results in the issue described below in the Problem Description and results in broken referential integrity inside RDS server

Adding Range Retrieval would split property elements in pages, first 1500 elements then in a next page another 1500 elements. In implementing this the MaxValRange parameter does not need to be increased above the 1500 threshold and all elements would be retrieved in subsequent pages. (See attached files for Diagram)