Truusvlugindewind
Programmer
Interesting thought:
Recently I changed the AUTHENTICATION from "server encrypt" to "client" for one of the databases. Something to do with win/ODBC applications forcing users to type their password over and over again.
A few minutus later I was (positive)surpised:
At my client's it is 100% MS-windows. Because I want to monitor the databases using "db2top" I installed linux as a vmWare image with expressC & db2top.
That image could be used to monitor all my databases....Nice!
Except the one I just changed. The O.S.user db2inst1 (standard nix instance owner) can not make contact that database even when I specify the "user/using" parameters. The other databases do not object to an O.S. user which is not known in the domain.
So that one better database seems saver. Hence my conclusion specified in the topic title.
Recently I changed the AUTHENTICATION from "server encrypt" to "client" for one of the databases. Something to do with win/ODBC applications forcing users to type their password over and over again.
A few minutus later I was (positive)surpised:
At my client's it is 100% MS-windows. Because I want to monitor the databases using "db2top" I installed linux as a vmWare image with expressC & db2top.
That image could be used to monitor all my databases....Nice!
Except the one I just changed. The O.S.user db2inst1 (standard nix instance owner) can not make contact that database even when I specify the "user/using" parameters. The other databases do not object to an O.S. user which is not known in the domain.
So that one better database seems saver. Hence my conclusion specified in the topic title.