Hourglass support/enhancement for DDF workload with LEGACYDB2QUALIFICATION=Y.

HourGlass doesn't support all kinds of z/OS DB2 DDF workload when the HourGlass option LEGACYDB2QUALIFICATION=Y is used.
This is a request for a full support of DDF workload for customers using LEGACYDB2QUALI=Y.

For DB2 workload it is possible to define within the HourGlass Control Center which kind of workload should be adjusted from HourGlass.
In case LEGACYDB2QUALI=N there are 4 fields for classification:
DB2 SSID
Plan Name
SQL-ID
Logical Jobname

In case LEGACYDB2QUALI=Y there are 2 fields for classification:
Jobname
Userid

The LEGACYDB2QUALI=Y is the mandatory option for us. Here we can use the well-defined JOBNAME to classify the right workload without difference between batch and db2 workload.
We cannot switch to LEGACYDB2QUALI=N.

But we have also applications on non-z/OS-platforms that request information (including time information) from z/OS DB2 via the z/OS DB2 Distributed Data Facility (DDF). This workload is running as a z/OS SRB, not as a TCB. Today hourglass is not able to adjust the day/time settings for this kind of DB2 workload (SRBs) if LEGACYDB2QUALY=Y is used.

Suggestion for the enhancement:
With HourGlass it should be feasible to adjust the date-/time-settings for all DDF workload whatever qualification options are used.
Although LEGACYDB2QUALI=Y is set, it should be possible to classify the "DDF workload" with these 3 fields
DB2 SSID: ssid
Plan Name: planname
SQL-ID: userid
Up to now this is only possible for LEGGACYDB2QUALI=N.
It doesn't make sense to classify this DDF workload with jobname! The DDF workload is running as Enclave SRB with a system generated enclave token (no static jobname).