Enhance Db2 System profiles to allow exceptions

System profiles are being used to control applcompat levels for distributed connections.  This is being done by trapping on the default db2 driver COLLECTION NULLID then setting the attributes to another collection using a higher applcompat.  This works really well until we need to have exceptions  for various reasons, ie driver is incompatible and want to put a temporaty exception on.

The filtering as documented has an order in which the filters are applied and this means in order to apply an exception you have to use a lower filter criteria. 

This is the order:

1. IP address or domain name, in the LOCATION column.
2. Product identifier, in the PRDID column.
3. Role and authorization identifier, in both ROLE and AUTHID columns. Within this category, Db2 uses the following order of precedence:
   1. ROLE and AUTHID
   2. ROLE only
   3. AUTHID only
4. Server location name, location alias, or database name, in the LOCATION column.
5. The location name of a requester, for monitored threads from a Db2 for z/OS requester, in the LOCATION column.
6. Collection identifier and package name, in both COLLID and PKGNAME columns. Within this category, Db2 uses the following order of precedence:
   1. COLLID and PKGNAME
   2. COLLID only
   3. PKGNAME only
7. Client application name, user identifier, or workstation name, in the following columns:
   1. CLIENT_APPLNAME
   2. CLIENT_USERID
   3. CLIENT_WRKSTNNAME

So in this case a profile using COLLID = NULLID can only be overridden by using CLIENT_*

If we want to use another criteria like location we cant as it is overriden  by COLLID.

There are many use cases I can think of where having the exception capability especially when using wildcarding that would be useful, this is just one case.