Suitable Replacement for SNAP_GET_APPL_V95

SNAP_GET_APPL_V95 got introduced with Db2 9.5 but is deprecated in actual versions/releases.

MON_GET_CONNECTION is declared as the replacement for this ‘old’ procedure, but the scope of the replacement procedure is different!

Thus MON_GET_CONNECTION needs to be enhanced to optionally provide the same scope of connection information as SNAP_GET_APPL_V95 does!

SNAP_GET_APPL_V95 provides connection information for the whole instance, when called at any database currently connected by the user within that instance,

while MON_GET_CONNECTION provides that connection information for the currently connected database only.

MON_GET_CONNECTION has to be enhanced with a parameter that allows to specify the scope of output when calling the procedure, that the option to get the connection information for the whole instance is still provided.

Without that option, MON_GET_CONNECTION is NOT a valid replacement of SNAP_GET_APPL_V95, and thus this old procedure should NOT get discontinued before MON_GET_CONNECTION gets this specific enhancement.

We addressed the lack of functionality, and that MON_GET_CONNECTION is NOT the valid replacement for SNAP_GET_APPL_V95, via case already, but this was claimed to be a design issue, although the documentation is NOT correct at that point, claiming MON_GET_CONNECTION to be the replacement of SNAP_GET_APPL_V95!

Business Justification:

Currently SNAP_GET_APPL_V95 is used by our automation software to obtain the connection information for the whole instance AND per database with a single request to one database within that instance, in an environment with several hundred instances and several thousand databases.
We have several application databases per instance and there’s always one systems management database defined, which is used for that data collection purpose.
If this enhancement request is not fulfilled, we would have to rewrite that data collection to connect to every single database within that instance to obtain the same level of information!
Besides the enormous effort for re-programming, this would cause add systems management request to application databases, which are not needed.

As the connection information has to be obtained by MON_GET_CONNECTION from the instance level anyhow and has to be filtered for the currently connected database, so why not providing the whole data on request?