Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Paged search considerations z/OS IBM Tivoli Directory Server Administration and Use for z/OS SC23-6788-00 |
|
Paged searches allow an LDAP client to control the rate at which search entries are returned by requesting a page of entries at a time (the number of entries in a page is controlled by the client request). The LDAP client proceeds through the search result set by issuing successive requests for the next page of entries. The LDAP server manages paged search requests in storage, caching the returned entries for the result set until they are retrieved by the client. Pervasive use of this capability by client applications increases the storage requirements of the LDAP server to hold these result sets. In particular, very large result sets use large amounts of storage for a paged search. If paged searches are enabled in the LDAP server, consider increasing the storage allowed in the LDAP server. If necessary, consider running the LDAP server in 64-bit addressing mode. The following configuration options contribute in controlling the
resources that might be used for paged search requests:
See cn=configuration for more information about the ibm-slapdPagedResLmt and ibm-slapdPagedResAllowNonAdmin attributes in the cn=configuration entry. Also, see pagedResults for more information about the pagedResults server control. |
Copyright IBM Corporation 1990, 2014
|