3.1.5.3 Making Further Account Mapping Requests to the Server

The User Name Mapping Protocol client continues to make further DUMPALLMAPSXXX_PROC requests, each time increasing the value of MapRecordIndex to the total number of map records returned by the server so far for this enumeration. For example, if the first reply returned 15 records, and the second reply returned 12 records, the third request in the sequence sets the MapRecordIndex to 27 (15 + 12). The User Name Mapping Protocol client continues to make requests until there are no more account mappings to retrieve from the server. This is indicated by a DUMPALLMAPSXXX_PROC reply that contains zero records (MappingRecordCount is 0), or if the next DUMPALLMAPSXXX_PROC request would set MapRecordIndex to TotalMappingRecordCount. TotalMappingRecordCount is returned in the server DUMPALLMAPSXXX_PROC response.

If at any point the values of CurrentVersionTokenHighPart, CurrentVersionTokenLowPart, or TotalMappingRecordCount returned by the server in the DUMPALLMAPSXXX_PROC response change from the initial values returned when MapRecordIndex was set to 0 in the DUMPALLMAPSXXX_PROC request, the current enumeration MUST be abandoned and restarted with a new DUMPALLMAPSXXX_PROC request (MapRecordIndex equal to 0).