PJ40871: UPGRADE OPENLDAP TO NEWER MAINTENANCE LEVEL
Closed as program error.
See problem summary.
APAR NUMBER: PJ40871 PRODUCT: z/TPF FUNCTIONAL AREA: Open LDAP Support SHIPPED IN PUT: 10 ABSTRACT: zTPF OpenLDAP support for OpenLDAP 2.4.35 with Berkeley Database (BDB) 5.3.21. PACKAGE CONTENTS: Source Segments: (C) base/cntl/tpf_bdb.cntl (C) base/cntl/tpf_ldap.cntl (C) base/include/tpf/c_proc.h (C) base/include/tpf/i_netd.h (C) base/macro/iproc.mac (C) base/openldap/cats.mak (C) base/openldap/ccmp.mak (N) base/openldap/cdac.mak (C) base/openldap/cdbr.mak (C) base/openldap/cdel.mak (C) base/openldap/clap.mak (C) base/openldap/cllb.mak (C) base/openldap/cmdr.mak (C) base/openldap/cmod.mak (C) base/openldap/cpas.mak (C) base/openldap/cser.mak (C) base/openldap/cwai.mak (N) base/openldap/headers/ac/socket.h (N) base/openldap/headers/ac/syslog.h (N) base/openldap/headers/ac/time.h (C) base/openldap/headers/db_config.h (C) base/openldap/headers/lber.h (C) base/openldap/headers/ldap.h (N) base/openldap/headers/ldap_log.h (N) base/openldap/headers/lutil.h (N) base/openldap/headers/portable.h (C) base/openldap/ldap_etoa.c (N) base/openldap/ldap_tpf.c (N) base/openldap/ztpf_files/usr/bin/db_archive (C) base/rt/cinet5.c (C) base/rt/cinet7.c (N) base/rt/crt0_bdb.c (C) base/rt/crt0_ldap.c (C) base/rt/crt0_ldap_client.c (C) base/rt/tpflinkobjs.mak (C) tpftools/include_ztpf/maketpf.env_cats (C) tpftools/include_ztpf/maketpf.env_ldap (C) tpftools/include_ztpf/maketpf.env_ldap_client Object Only Binaries: None. Configuration Independent Binaries: (C) base/lib/libCLTY.so (C) base/lib/libtpflinkobjs.a (C) base/load/CLTY.so (C) base/load/CLTZ.so (C) base/obj/cinet5.o (C) base/obj/cinet7.o (N) base/obj/crt0_bdb.o (C) base/obj/crt0_ldap.o (C) base/obj/crt0_ldap_client.o Support Files: base/lst/cinet5.lst base/lst/cinet7.lst base/lst/crt0_bdb.lst base/lst/crt0_ldap.lst base/lst/crt0_ldap_client.lst base/lst/CLTY.map base/lst/CLTZ.map OTHER BINARIES TO BUILD: YES (N) opensource/ldap/output/obj/ldap_tpf.o (C) <sys>/load/IPAT.so (C) opensource/lib/libCATS.so (C) opensource/lib/libCLLB.so (C) opensource/load/CATS.so (C) opensource/load/CCMP.so (N) opensource/load/CDAC.so (C) opensource/load/CDBR.so (C) opensource/load/CDEL.so (C) opensource/load/CLAP.so (C) opensource/load/CLLB.so (C) opensource/load/CMDR.so (C) opensource/load/CMOD.so (C) opensource/load/CPAS.so (C) opensource/load/CSER.so (C) opensource/load/CWAI.so (N) opensource/ldap/output/obj/force_build.o (C) opensource/bdb/output/obj/db_recover.o (C) <sys>/obj/ipat.o COMMENTS: This project upgrades zTPF to use OpenLDAP 2.4.35 and Berkeley Database 5.3.21. The following items were addressed: 1) Multiple master support - previous OpenLDAP version 2.4.6 contained numerous bugs. 2) There were no Data Collection/Data Reduction counters specifically to support OpenLDAP messages. 3) No mechanism existed on zTPF to ensure that a server remains active in a multiple server environment if zTPF automatically recycled a server. 4) zTPF support for OpenLDAP did not take advantage of relative path names in .mak files, forcing segment names to be renamed to be unique. 5) Berkeley Database db_archive utility was not supported on zTPF. 6) Numerous code modifications in the ported code made it difficult to migrate to newer versions of OpenLDAP and BDB.
SOLUTION: zTPF OpenLDAP support has been updated to support OpenLDAP 2.4.35 and Berkeley Database 5.3.21. The following additional items are now supported: 1) With the latest version of OpenLDAP, a more reliable multiple master support is now supported. 2) Data Collection/Data Reduction counters have been added to support OpenLDAP messages. The TCP/IP network services database file (/etc/services) needs to be updated with an entry for OpenLDAP and any associated port being used (typically 389). Please see zTPF TCP/IP network services database support documentation for more information about how to use this file. 3) When OpenLDAP servers are automatically recycled by zTPF, for example when ZOLDR support activates a new program used by OpenLDAP, zTPF will automatically serialize recycling of zTPF OpenLDAP servers to ensure that a server remains active in a multiple server environment. 4) OpenLDAP .mak files have been updated to use relative path names. 5) The Berkeley Database db_archive utility has been added to allow better management of Berkeley Database log files. 6) zTPF modifications have been removed from the ported code to not tie zTPF support to a specific version. Important note: Co-requisites for this APAR are OpenLDAP 2.4.35 and Berkeley Database 5.3.21 which will need to be downloaded directly from www.openldap.org and www.oracle.com websites, respectively. This APAR is not compatible with the previous versions of OpenLDAP and Berkeley Database supported on zTPF and downloaded from the zTPF web page. Please see zTPF Support for OpenLDAP User's Guide for more information about installing these products. These new versions will work with any previous OpenLDAP database that was created with the previous versions. COREQS: YES 1) OpenLDAP 2.4.35 and Berkeley Database 5.3.21. 2) PJ41135 3) PJ41130 4) PJ41321 MIGRATION CONSIDERATIONS: YES Application programming interface (API) changes: ZFILE db_archive Hardware, software, and configuration changes: As noted in the Solution section of this APEDIT, new versions of OpenLDAP and Berkeley Database need to be downloaded and built for zTPF. Communications changes: As mentioned in the Solution section above, file /etc/services needs to be updated for OpenLDAP in order for Data Collection/Date Reduction to count OpenLDAP messages. Build and load process changes: Please see zTPF Support for OpenLDAP User's Guide for information about installing and building OpenLDAP and Berkeley Database on zTPF. Installation validation: Starting an OpenLDAP server with a debug level of 256 will send debug messages to the console. A version is included in the debug messages that can be used to verify the correct version is loaded on zTPF. For example, define the OpenLDAP server using the following command and then start it: ZINET ADD S-ldap PGM-Clap MODEL-DAEMON USER-root act-oper XPARM--f /test/slapd.conf -d 256 A debug level of 256 would typically be used to debug a problem. BUILD COMMANDS AND INSTRUCTIONS: YES #maketpf commands for linux maketpf -f tpflinkobjs crt0_bdb.o crt0_ldap.o crt0_ldap_client.o maketpf tpflinkobjs link maketpf -f CLTY cinet5.o maketpf -f CLTZ cinet7.o maketpf -f IPAT maketpf CLTY link TPF_VERIFY_LINK_REFS=NO maketpf CLTZ link maketpf -f CATS maketpf -f CDBR maketpf -f CDAC maketpf -f CLLB maketpf -f CLAP maketpf -f CWAI maketpf -f CSER maketpf -f CPAS maketpf -f CMDR maketpf -f CMOD maketpf -f CDEL maketpf -f CCMP maketpf CLTY link ipat tpfstub UPDATED INFORMATION UNITS: YES z/TPF and z/TPFDF Migration Guide: PUT 2 and Later z/TPF and z/TPFDF System Installation and Support Reference z/TPF Operations z/TPF Support for OpenLDAP User's Guide z/TPF System Performance and Measurement Reference See your IBM representative if you need additional information. DOWNLOAD INSTRUCTIONS: http://www.ibm.com/software/htp/tpf/maint/maintztpf.html APAR URL: http://www.ibm.com/software/htp/tpf/ztpfmaint/put10/PJ40871.htm
Reported component name
Reported component ID
NoSpecatt / Xsystem
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
Fixed component ID
Applicable component levels
Translate this page: