Need to add extra fields in KM5_Address_Space_Storage_SubKey table to filter the ASID showing memory constraint symptoms

This RFE is a spin off from PMR 22839.

Problems with current design:
- adress space selection not granular enough: the example here is an MQ broker with multiple jobs with the same jobname and we only want to monitor some of them (one?) based on stepname and/or pgmname.
- not able to collect for nearly enough address spaces: they have hundreds of WAS regions that they want to monitor. We can't possibly collect for that many (48 address spaces used to cause TEMS quiesce!), nor would we want to because of ...
- unnecessary overhead: collecting thousands of rows for each address space has to be expensive. That's a waste if we don't need it.

proposed solution (Enhancement Request):
We don't want to collect thousands of rows of data for any address space until we know that it is behaving badly. Collect minimal amount of data (like output of LSQA minor command) for a much bigger list of address spaces (all?) then the user can use a query with ASID (from a link) to get the complete details if/when needed.

Workaround:
System Automation will be used to dynamically build a list of ASIDs to monitor on each system from a master list of jobname/stepname. Then, using an M1 session on each system, SA will issue PEEK <ASID> / LSQA for each address space and collect the "Available For User Pvt". If that is below the threshold, an alert will be raised. The process repeats every 10 or 15 minutes.