- In an environment where we use the code page IBM-1147.
- Within the slapd.conf have set:
authCodeset IBM-1147
- And in the following section:
database catss_utf
suffix "host=testsystem,o=ca,c=us"
enable_cmd_dump
enableVerify
codeset IBM-1147
naming_mode tss
HostUFNOverride ./user_TSS_UFNs.conf
- It is important to know that the way to address requests to LDAP, has to be done using the code UTF-8.
- To check what the environment variables look like, you can issue:
printenv
It should show something like:
_BPX_TERMPATH=OMVS
PATH=/usr/lpp/java/J7.0/bin:.:/bin
SHELL=/bin/sh
COLUMNS=80
_=/bin/printenv
STEPLIB=GSK.SGSKLOAD:DB2.DB2810.SDSNEXIT:DB2.DB2810.SDSNLOAD:CEE.SCEERUN:CEE.SCE
ERUN2
LOGNAME=myacid
LIBPATH=/usr/lpp/java/J7.0/bin:/lib:/usr/lib:
TERM=dumb
HOME=/u/myacid
LINES=39
DSNAOINI=/cai/caldap/caldap.odbcini.xe52
JAVA_HOME=/usr/lpp/java/J7.0
TZ=UTC0
- You have to set the following variable to have your LDAP receiving a LDIF file in UTF-8 to be interpreted correctly.
You can issue:
export LC_ALL=Fr_FR.IBM-1147
- Afterward, you can issue LDAPSEARCH, LDAPMODIFY commands using with LDIF file in IBM-1147 environment.
- Else, the LDIF file won't be transfer to the LDAP in UTF-8 and unpredictable issue may occur.
- You have to be at maintenance level RO93183.
- This is valid whatever the page code is.