Make Db2 Connect ready for the future (which is already here)

Hi IBM Community, hi IBM Support,

as part of a Red Hat Enterprise Linux version change, at the moment we have to set up many new server systems for the application software we support.
Our application software relies heavily on DB2 and so the IBM Data Server Runtime Connect Client für Linux is an important part of our software stack. 
Our software uses both the C-libraries and java-libraries (for JDBC-Type 4 connections) from the Db2 Connect Client.
Sadly the installation and update process for the DB2 Connect Client on Linux is a constant source of problems. 
Of course there are some problems which root in our internal processes for packaging and shipping of software, but after over 15 years of watching the struggle I’ve come to the conclusion that there are also some fundamental problems with the installation sources which are provided by IBM. IBM should modernize the way the Connect Client gets shipped or should offer a lightweight alternative how to connect to DB2.
These shortcomings are becoming increasingly apparent in view of the containerization of software and automatization of installation processes, as already mentioned in the idea [DB24LUW-I-1889]. We also see the same problems on the Windows side, as mentioned in idea [DB24LUW-I-1864].
Nearly every other component of our software stack is provided as an native linux (rpm) package which comes either from the RedHat repositories or other repository sources and can easily be installed and updated.

For the DB2 Connect Client we need a specific (manual) process to bundle new versions into an installation package.
The problems include:

• 32bit Prerequisites: We must still install libstdc++*.i686 pam-devel.i686 although we only want to use 64bit version.
• The installation procedure differs depending on whether DB2 Connect Client was already installed or not (db2icrt vs db2setup). The upgrade command can not be used if it is an root-installation. 
  The installation procedure differs depending on which version was previously installed.
  Our solution to this, is to always remove the installed old version, which also involes multiple manual steps and leads to other problems.
• We must implement a process to monitor errors which occur during installation, because they only appear in the db2setup.log file.
• The installation process is splitted:
  The installation process involves at first the calling of the db2setup command (with a provided rsp-File) and later the installation of gskcrypt64 and gskssl64 rpm-packages, which are not connected very well. In case of an update sometimes the gskit-rpm packages must be updated too, sometimes not (see IBM documentation). 
  This leads to the situation that we must check if there are older versions of gsk-packages still installed on the server and remove them manually.

IBM releases new products that include modern installation processes and are “cloud-ready”, while older components like Connect Client don’t get the necessary attention to stay technologicaly up to date. It would be great if the Connect Client would be shipped as rpm Package (maybe in a lightweight version).

Kind regards

Daniel