z/OSMF - Network Configuration Assistant - Traffic Descriptor smart filtering

Currently in a Traffic Descriptor the Job Name filter does accept wildcard character as the last character. This works but depending on jobname pattern this can result in a large list of traffic types in a traffic descriptor. If the differentiator for a Job Name is in the middle it is not possible to have the wildcard character there and I have to code the full list of different Job Names which is cumbersome (and error prone). So why not offer the ability to use wildcard characters as well in the middle?

Example: I have to cover traffic descriptor for 4 Job Name User ID combinations:

• DBP1DIST with user USRP0001
• DBT1DIST with user USRT0001
• DBD1DIST with user USRD0001
• DBE1DIST with user USRE0001

I could now define a pattern for a Job Name like 

• DB*DIST with user USR*0001 

and all are covered. However, as this is not possible I have to define a large list of types (not exhaustive).

• DBP* with user USRP*
• DBP* with user USRT*
• DBP* with user USRD*
• DBP* with user USRE*
• DBT* with user USRP*
• DBT* with user USRT*
• DBT* with user USRD*
• DBT* with user USRE*
• [ongoing for others]
  
  offering wildcard characters in the middle would allow me to reduce the list of 16 required types down to 1.

Context:

The above would be part of a client rule for DB2 DIST address space to connect to all other DB2 Servers (accepting TLS connections only) available in the environment.