z/OS Connect SMF123 Enhancements

Objective
To add more data to the z/OS Connect Audit record for auditing and monitoring purposes.

Description
As the SMF123 record is described as the z/OS Conned Audit record, it would be appropriate that more information from USS log files should be written to the SMF123 records so existing reporting functionality (provided by SAS MXG and similar products) can be utilised.

Technical Requirements (Information which would prove useful)
1. Cut records for all attempted API runs, make it such that the z/OS Connect product is auditable. This includes:
a) Unsuccessful API runs (401s at z/OS Connect level)
b) Any other scenario where an end user perf
orms a z/OS Connect action and it is not logged.

2. Include the following information already available via HTTP logs to SMF:
a) HTTP response code.
b) Whether a service was started or stopped (all we see currently is that the status has changed, not to what).
c) Whether an API was started or stopped (all we see currently is that the status has changed, not to what).
d) Whether an API is updated (overwritten) by ano
ther.

3. Include the error message written to stderr where there is one (when 500 returned).

4. Include target system data, which backend system the API called

5. Include which program or transaction was called via an API in CICS or IMS