Support SQL Type ("SQL Object Type") as an Object Attribute Merged

With the pervasiveness of SQL on IBM i and the fact that most public-visible new release features are simply SQL enhancements, the SQL Type of an object is becoming more and more important to application development. As of this point in time, *DTAARA, *FILE, *PGM, and *SRVPGM objects can have an SQL Type associated with them. Currently, only *FILE objects expose the SQL Type to the developer or end-user and developer. For example, we need to use the QUSRMBRD API to get the *FILE's SQL Type but QUSROBJD does not expose this attribute for other objects, but it should.
If SQL is to fluid to incorporate into the rest of the interfaces that expose object properties, then a new QUSRSQLA (Retrieve SQL Object Attributes) API is longer overdue. With this API as SQL evolves on the system, it can be enhanced to support/return the information needed, while things like QUSROBJD and QGY* remain unchanged.

Using system interfaces like WRKOBJPDM, WRKOBJ, QUSROBJD, or 3rd Party tools like SQL iQuery, COZTOOLS, TAATOOLS, etc. provide virtually no way to view the SQL attribute of Sequence, FUNCTION, PROCEDURE of an object that is also an "SQL Object".
Today, the only interface is via the OBJECT_STATISTICS SQL UDTF which requires the end-user to use SQL to get this information--this severely limits the ability to build tool that list and process objects, find where-used references with SQL context, and provide a full solution to IBM i customers.
Tomorrow, when User Spaces or Independent Indexes and perhaps even Data Queues also are utilized by SQL as an "SQL Object" how will those objects be seemlessly integrated into such existing tools if no SQL Type attribute is accessible through a lower-level interface?