Fixes are available
APAR status
Closed as program error.
Error description
DBM config parms not being set during rsp file install of DB2 Runtime Client V9.5 FP2 RSP file parameters DIAGLEVEL, DIAGPATH etc that are not being set during installation. We also tried out for some different parameters like but none of them were updated the default values were only set. http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp According to this link we can create any number of instances but in this case only the last instance created is taken into account. The earlier versions supported the change in the RSP file installations The reason why earlier version (v8 and earlier) of RTCL supported the changed parameters in the rsp file is: The RTCL has been developed/built differently from other db2 products since v91ga. It is very different from v8 RTCL. The v91 (and later) RTCL install image is just one single setup.exe, while v8 RTCL and other v91/v95 db2 install images have many files in them, such as most files are under ~\db2\windows\ in the images. FYI, v8.2 Runtime Client-Lite is similar as the v9 (and later) Runtime Client, both are merge module based products. V9.1 gets rid of the traditional RTCL, and enhanced the v8.2 Runtime Client-Lite to make it as the new RTCL
Local fix
If you want to set your own dbm cfg configuration, one workaround will be to install RTCL on one machine, configure it customly. Then, export its instance configuration. Then, when you install rtcl on other machine via a rsp file based silent install, import that instance configuration (Note: set its full path/fileName for the keyword: DB2.CLIENT_IMPORT_PROFILE.
Problem summary
Users Affected: All users using V91FP7 and prior. Problem Description: DBM config parms not being set during rsp file install of DB2 Runtime Client V9.5 FP2 RSP file parameters DIAGLEVEL, DIAGPATH etc that are not being set during installation. We also tried out for some different parameters like but none of them were updated the default values were only set. http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp According to this link we can create any number of instances but in this case only the last instance created is taken into account. The earlier versions supported the change in the RSP file installations The reason why earlier version (v8 and earlier) of RTCL supported the changed parameters in the rsp file is: The RTCL has been developed/built differently from other db2 products since v91ga. It is very different from v8 RTCL. The v91 (and later) RTCL install image is just one single setup.exe, while v8 RTCL and other v91/v95 db2 install images have many files in them, such as most files are under ~\db2\windows\ in the images. FYI, v8.2 Runtime Client-Lite is similar as the v9 (and later) Runtime Client, both are merge module based products. V9.1 gets rid of the traditional RTCL, and enhanced the v8.2 Runtime Client-Lite to make it as the new RTCL problem Summary: LOCAL FIX: If you want to set your own dbm cfg configuration, one workaround will be to install RTCL on one machine, configure it customly. Then, export its instance configuration. Then, when you install rtcl on other machine via a rsp file based silent install, import that instance configuration (Note: set its full path/fileName for the keyword: DB2.CLIENT_IMPORT_PROFILE.
Problem conclusion
First fixed in DB2 UDB Version DB2 V91, FixPak 8
Temporary fix
Comments
APAR Information
APAR number
JR31731
Reported component name
DB2 UDB ESE WIN
Reported component ID
5765F4101
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-01-20
Closed date
2009-10-09
Last modified date
2009-10-09
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
DB2 UDB ESE WIN
Fixed component ID
5765F4101
Applicable component levels
R910 PSY
UP
[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910"}]
Document Information
Modified date:
07 October 2021