Fixes are available
Closed as program error.
On 64 bit windows installation of Directory Server both 32 bit and 64 bit command line clients (such as ldapsearch) gets installed. The wrapper cmd files (such as idsldapsearch.cmd or ldapsearch.cmd) from the bin folder calls / executes the 64 bit executable only. There is no method to invoke the 32 bit executable with out editing the wrapper cmd file.
Copy idsldapsearch.cmd into idsldapsearch32.cmd Modify the idsldapsearch32.cmd file to change the PATH and call the 32 bit exe: set PATH=%IDS_LDAP_HOME%\lib;%PATH% ... "%IDS_LDAP_HOME%\bin\32\%IDS_TMP_PROG%" %*
Currently on a 64 bit windows system, the ldap client command wrappers are hard coded to invoke the 64 bit executable only. To invoke the 32 bit client executable, the ldap client command wrappers must be updated manually. TDS provided ldap client utilities are enhanced to use env variable IDS_LDAP_BIT_MODE on windows platforms. This env variable already exists for unix platforms. Setting IDS_LDAP_BIT_MODE to 32 will make the ldap client command wrappers to invoke 32 bit ldap client executables. If this variable is not set it will work as default behavior per OS bit mode. This means 32 bit executalble will be invoked by the client command wrapper on a 32 bit windows system. Similarly 64 bit executable will be invoked by the client command wrapper on a 64 bit windows system. To invoke the 32 bit ldap client executable on 64 bit windows system set the following env variable before using client utilities in a command prompt: set IDS_LDAP_BIT_MODE=32 This will invoke 32 bit executable for execution.
The fix for this APAR will be contained in the following maintenance packages: | interim fix | 18.104.22.168-ISS-ITDS-IF0054 |
Reported component name
IBM TIV DIR SER
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
IBM TIV DIR SER
Fixed component ID
Applicable component levels