license.sh | License checker tool - We 're in a beta phase

If you want to make sure the empty column is not there, you can always remove the column by doing for example: License.drop(labels="EMPLOYEE_ID", axis=1, inplace=True) I am not entirely sure where you want which column removed, so I cannot give a more complete solution.

Ok here is what I ended up doing. Basically the window closing kicks off a task that will wait for the release to happen and then invoke the shutdown. This is what I was trying to do before but it didn't seem to work in async void method but it seems to be when done this way. Here is the new handler:

I suspect that the cause of your symptom is that the account specified for enable_MQFunctions command line does not have a password at the time that enable_MQFunctions tries to run. You can prove this by looking at db2diag.log to see the exact authentication failure message, and/or by looking at the /etc/passwd entry for that account just before you run enable_MQFunctions.

You can expand the Dockerfile to configure the Db2 for MQ entirely during the docker build instead of running those steps after docker run or in entrypoints. That way you are responsible for all the steps inside the Dockerfile and it will be repeatable without manual intervention after the docker run command. It also means that your built image is pre-baked with all of the required configuration which will then be persistent. You need to have enough competence with scripting in the Dockerfile to get the desired outcome.

When correctly done, the enable_MQFunctions will operate properly during docker build, so if you are getting errors it's because you are doing it incorrectly.

I can successfully configure the database and run enable_MQFunctions all inside the Dockerfile, with these steps below (because of using a non-root install of Db2), so all the configuration is already in the built image.

• after installing Db2 and before db2start the Dockerfile should create /home/db2inst1/sqllib/userprofile (which will run whenever the instance-owner accounts dots in its db2profile from .bash_profile or .profile), to do these steps:

  -- append /opt/mqm/lib64 to LD_LIBRARY_PATH

  -- export AMT_DATA_PATH=/opt/mqm

  -- prepend /opt/mqm/bin on the PATH

• chown db2inst1:db2iadm1 /home/db2inst1/sqllib/userprofile

• after installing Db2 and before db2start, the Dockerfile should run these steps:

  -- db2set DB2COMM=TCPIP

  -- db2set DB2ENVLIST=AMT_DATA_PATH

  -- db2 -v update dbm cfg using federated yes immediate

• set a password for db2inst1 account in the Dockerfile

• the Dockerfile can then run db2start, create the database ( i call it sample, you can call it whatever you like) and run the fragment below as user db2inst1 to first create the required objects in the database used by the MQ functions:

su -db2inst1 -c "( db2 -v connect to sample ; \ db2 -tvf /home/db2inst1/sqllib/cfg/mq/amtsetup.sql; \ db2 -v list tables for schema DB2MQ ; \ exit 0 ) "

Notice that you have to run amtsetup.sql in a subshell ,as shown, to explicitly exit 0, because amtsetup.sql always returns non-zero exit code even when it completes successfully. So you want the docker build to continue in that case.

If all the above steps completed successfully and MQ is already successfully installed, later in the Dockerfile you can run the enable_MQFunctions as follows:

I use ARG INSTANCE_PASSWORD to specify the db2inst1 password, which can come from external.

su - db2inst1 -c "( . ./.profile ;\ db2start ;\ db2 -v activate database sample ;\ cd /home/db2inst1/sqllib/cfg ; \ /home/db2inst1/sqllib/bin/enable_MQFunctions -echo -force -n sample -u db2inst1 -p $INSTANCE_PASSWORD ; \ db2stop force ; \ exit 0)"

The Python interpreter you started in your example is not the one in the environment. conda info -a says python version : 3.7.0.final.0 and yet your interpreter says Python 3.6.5

The problem should become apparent when you activate your environment and run which python which should be pointing to the activated env but probably doesn't.

How did you create those environments? Make sure to set the python=XX option or the new environment uses the interpreter from the base/root environment rather than installing a new one. I.e. conda create -n my_environment python=3.7

Edit: Sorry, I just looked up and tested conda info -a. python version : XX seems to be referring to the base env not the currently active one.

I'm leaving this answer here, since even though my reasoning seems to be wrong, it may still be helpful.

Assuming you did everything else correctly - problem is different formats of signatures produced by openssl and .NET. Signature produced (and expected) by openssl is (surprise!) again ASN.1 encoded. Run