DB2_DMU_DEFAULT=IMPLICITLYHIDDENMISSING, if set at instance level then we should not need it to be specified again in import command just like 9.7 clients

We are facing an issue for version 11.1. FP5 where we are able to load the data into a table with a column in a table which has IMPLICITLY HIDDEN column, In the past we were able to run the import and not specified the column name and it has worked. With new version, it should work as db2profile registry is set as below .

DB2_DMU_DEFAULT=IMPLICITLYHIDDENMISSING

Informational tokens are "DB2 v11.1.4.5", "special_40265",
"DYN1911120100AMD64_40265", and Fix Pack "5

I tried to do some testing around this and able to run the import without any column names locally without any issues. While testing we found that if they use db2 client version 9.7 it works, however with higher versions like 11.1.5.1 it doesn’t work

with 11.1.5.1 client we get issue below
SQL2437N The data movement command failed because the utility was unable to
resolve how implicitly hidden columns should be processed. No data was moved.

Reason for RFE :: client behaviour has changed from 9.7 onwards, even IBM was able to reproduce the problem in 10.1, 10.5, 11.1

It is not forward compatible and doesn't work in newer versions. As this worked in 9.7 it should work for other versions as well

FIX was ::

db2set DB2_DMU_DEFAULT=IMPLICITLYHIDDENMISSING" on the client side or adding the import command : modified by implicitlyhiddenmissing.

ideally like 9.7clients , server side registry should be honoured

When it is set on server, why it is relying on what is on client. This is clearly a BUG. something which was working 9.7 and stopped working after that.