Enhance DB2 profile history tables for DataSharing subsystems - column STATUS

DB2 profile and attributes tables have related history tables, SYSIBM.DSN_PROFILE_HISTORY and SYSIBM.DSN_PROFILE_ATTRIBUTES_HISTORY. These history tables contain information regarding enabled profiles and attributes that were processed by a -START PROFILE command.
Whether a profile and its attribute(s) have been accepted, or rejected, can be seen in column STATUS. The description of the STATUS values varies depending on whether or not profile tables are used in data sharing subsystems.

Without data sharing, a STATUS value might be either
- 'ACCEPTED &additional-info', or
- 'REJECTED &reason'.
To query the STATUS of a profile or attribute, a query as the following might be sufficient:
SELECT STATUS
FROM SYSIBM.DSN_PROFILE_HISTORY
WHERE PROFILE_TIMESTAMP => '&timestamp';
(similar query for the attribute history table)

With data sharing, the STATUS value has changed, it now shows
- 'ACCEPTED BY &db2-member &additional-info', or
- 'REJECTED BY &db2-member &reason'.
As profiles are started per DB2 member, querying the status per DB2 member now requires:
SELECT STATUS
FROM SYSIBM.DSN_PROFILE_HISTORY
WHERE PROFILE_TIMESTAMP => '&timestamp'
AND SUBSTR(STATUS,13,4) = CURRENT MEMBER;
(similar query for the attribute history table)

This difference in the STATUS column should be removed, making it easier to have automated processes checking the result of -START PROFILE commands.
It will be more convenient to have the name of the affected DB2 member in another (or additional) column of the history tables.