Library_Symbol_Names

   The symbols exported by the LDAP$SHR OpenVMS run-time library
   differ from those specified in the IETF C LDAP API specification.

   The header file LDAP.H maps user references to LDAP API function
   names to the appropriate LDAP$SHR symbol name. Therefore, any
   application wishing to use the OpenVMS LDAP API must include the
   version of LDAP.H that ships with OpenVMS.

   All of the functions in the OpenVMS LDAP library are prefixed
   with the facility code "LDAP$".

   For those functions where the caller's pointer size is
   significant, the name of the 64-bit entry point will have a "_
   64" suffix, while the name of the 32-bit jacket will have a "_32"
   suffix. Functions that are not sensitive to pointer size have no
   special suffix.

   For example, the function ldap_modify() is sensitive to the
   caller's pointer size (because one of its arguments is an
   array of pointers). Therefore, the library exports symbols for
   LDAP$LDAP_MODIFY_64 and LDAP$LDAP_MODIFY_32. For the function
   ldap_simple_bind(), which is not sensitive to the caller's
   pointer size, a single entry point, LDAP$LDAP_SIMPLE_BIND, exists
   in the library.

   Because OpenVMS imposes a 31-character limit on the length of
   symbol names, certain functions in the library have names which
   are abbreviated versions of the public API name. For example,
   in the case of the function ldap_parse_sasl_bind_result(), the
   library provides two entry points, namely LDAP$LDAP_PRS_SASL_
   BIND_RES_32 and LDAP$LDAP_PRS_SASL_BIND_RES_64.