Enable Class Inheritance for the DB2 CONTROL Parm Values

Please enable Class Inheritance for the DB2 Control Parm values. Presently the Class Inheritance for the defined DB2 Control parms are not working as documented. Please refer to IBM's Defining Automation Policy manual starting on page 12 under the "Inheritance and Defaulting" section to reference how APL Class inheritance functions.
The issue that is preventing this class inheritance from working as expected is that the DB2 Control parms starting with the Subsystem ID field are all grouped together when it comes to inheritance. So either all the parms can be inherited, or none of them are. The problem is that the Subsystem ID will always be a unique value and must be defined within the DB2 Instance. Using a AOCCLONE variable or system symbolic variable for the DB2 Subsystem ID will not work either if any of the systems(LPARs) contains more than one DB2 subsystem. Thus this grouping of the DB2 Control Parm values is preventing the Class Inheritance of these same parm values.
One of two simple solutions can be applied to resolve this issue and enable class inheritance to function as documented:
1) The best option would be to simply remove the DB2 Subsystem ID from the all-or-nothing group of DB2 control parms. This would allow the DB2 Subsystem ID field to be defined independent of the remaining numerical DB2 Control parms that still could be grouped together for inheritance. Therefore, the DB2 Subsystem ID could still be defined locally at the Instance, but all the other DB2 Control parm values could be inherited from the upper class structure.
2) The second best solution and least desirable would be to enable Application Symbolics to be used in the Subsystem ID field. This way the DB2 Subsystem value is associated with the DB2 definition and is defined local to the DB2 definition itself.