PQ60557: BBOMCFG REPLACES CUSTOMER'S LDAP FILES | |||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description The ++HOLDDATA for UQ99329 suggested running the bbomcfg program. This replaced the ldap configuration information modified by the customer with new files. The old ones were named *.update. This lost customization done by the customer and caused their environment to not work. The received BBON8901E in the SM EUI. . BBOMCFG should not be in the business of overwriting customized files.Local fix Merge changes from customized files into new files.Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V4.0.1 for z/OS and OS/390 * **************************************************************** * PROBLEM DESCRIPTION: ++HOLDDATA for PTF UQ99329 * * instructed the customer to run the * * BBOMCFG job after applying the PTF. * * When the customer ran the BBOMCFG * * job, it copied new LDAP config * * files to the $CBCONFIG/<PLEX>/etc/ldap * * directory and renamed the existing * * config files with a *.update extension. * * The customer had customized the * * original config files, and these * * changes were not merged into the new * * files created by BBOMCFG. When the * * customer re-started the daemon and * * tried to connect with the the System * * Management End User Interface * * (Administration and Operations * * applications), also known as the SM * * EUI, the customer received a * * BBON8901E error message. * **************************************************************** * RECOMMENDATION: * **************************************************************** The BBOMCFG job calls bbomcfg.sh, a REXX script. This script checks the system's $CBCONFIG/<PLEX>/etc/ldap directory for the existence of various LDAP config files. If it finds one of these config files, it simply renames the existing file with a *.update extension and then copies a new version of the config file to the directory. Many customers make changes to the various LDAP config files. As it currently operates, the bbomcfg.sh does not merge these changes into the new LDAP config files that it copies to the HFS. Unless customers are notified of this in the ++HOLDDATA which instructs them to run BBOMCFG, they will have to manually merge all of their changes into the new files.Problem conclusion The bbomcfg.sh script was modified to retain existing LDAP config files on the customer's system. The output in the bbomcfg.out log file will indicate this as follows: .. /WebSphere390/CB390/PLEX1/etc/ldap/SY1.bboslapd.conf (retained) /WebSphere390/CB390/PLEX1/etc/ldap/SY1.bboldif.cb (retained) .. In the future, the ++HOLDDATA will inform customers of any changes they must make to their LDAP config files. APAR PQ60557 is associated with SERVICE LEVEL W401063 of WebSphere Application Server V4.0.1 for z/OS and OS/390.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: UQ66412 Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 401
Software edition:
Reference #: PQ60557
IBM Group: Software Group
Modified date: Jun 5, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.