APAR status
Closed as program error.
Error description
BF Installer doesn't handle DB changes post-install on upgrade
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * **************************************************************** * PROBLEM DESCRIPTION: * **************************************************************** * RECOMMENDATION: * **************************************************************** Users affected: users who updated their buildforge.conf file. Problem summary: During the upgrading, install do not write the new db info read from buildforge.conf to upgrade.res. So the perl installer will just use the old definition find in main.res. To avoid this problem, user can change ?bfinstall?/Manage/main.res according to buildforge.conf. After in release 7.1.3.3, this problem should be gone.
Problem conclusion
Delivered in Build Forge, 7.1.3.3
Temporary fix
Comments
APAR Information
APAR number
PM58791
Reported component name
BUILD FORGE EE
Reported component ID
5724S2702
Reported release
712
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-02-22
Closed date
2012-05-25
Last modified date
2012-05-25
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
BUILD FORGE EE
Fixed component ID
5724S2702
Applicable component levels
R712 PSN
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSB2MV","label":"Rational Build Forge"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.1.2","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
25 May 2012