Monitor End-to-End Access in real time for Audit Purposes

Support for this is also provided in CICS TS 6.1 which is generally available from 17th June 2022.

For more information see https://www.ibm.com/docs/en/cics-ts/6.1?topic=whats-new

Support for this is also provided in CICS TS 6.1 which is announced today April 5th and will GA June 17th 2022.

See Announcement letter https://www.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/2/897/ENUS222-092/index.html&request_locale=en

The functionality requested by Usecase #1 is available by applying CICS APAR PH30252 on CICS TS 5.4, 5.5 or 5.6 and by applying DB2 V12 apar PH31447. The CICS-DB2 Attach must be configured so that the DB2CONN definition for pool threads, or DB2ENTRY definitions specify ACCOUNTREC(UOW) or ACCOUNTREC(TASK).

The functionality requested by Usecase #4 is function that is already available.
Correlation with DB2
For correlation we pass DB2 a 22 byte token, which is the 27 byte lu6.2 uowid with the length bytes stripped off the front, the period removed between netname and luname and the sequence number stripped off, Hence its netname||luname||middle six bytes of stck.

In the DB2 record 101 record the 22 byte token is QWHCTOKN. In the CICS record the network uowid is split into two fields NETUOWPX (containing netname period luname) and NETUOWSX (containing six bytes of clock and sequence number).

So you have to parse and strip the period out of NETUOWPX to get 16 bytes and strip the sequence number off NETUOWSX to give you six bytes and that gives you the 22 bytes to compare against QWHCTOKN.


Correlation with IMS DB
DBCTL supplies CICS with monitoring data, which can then be output to the CICS monitoring domain.
Monitoring data is output to the CICS monitoring domain in the following situations:
• When CICS receives the response to a PSB schedule request from DBCTL, it checks whether this task has already been scheduled successfully to DBCTL. If it has, CICS forces the monitoring data from the previous PSB schedule out; that is, it writes the performance class record for the task and resumes monitoring that task. If it has not been scheduled before, no monitoring processing is done.
• When CICS receives a response from the DBCTL as a result of a COMMIT or ABORT request, CICS outputs the monitoring data, but does not write it.
• In the case of the final PSB schedule for a task, the monitoring data is automatically written at the end of a task

See https://www.ibm.com/support/knowledgecenter/SSGMCP_5.5.0/monitoring/dfht4c0070.html

For the data returned, see https://www.ibm.com/support/knowledgecenter/SSGMCP_5.5.0/monitoring/dfht4a6.html

This is something we would like to address. The RFE is being moved into 'Planned for Future release' status. Please note:
IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion.

Correlation with DB2
For correlation we pass DB2 a 22 byte token, which is the 27 byte lu6.2 uowid with the length bytes stripped off the front, the period removed between netname and luname and the sequence number stripped off, Hence its netname||luname||middle six bytes of stck.

In the DB2 record 101 record the 22 byte token is QWHCTOKN. In the CICS record the network uowid is split into two fields NETUOWPX (containing netname period luname) and NETUOWSX (containing six bytes of clock and sequence number).

So you have to parse and strip the period out of NETUOWPX to get 16 bytes and strip the sequence number off NETUOWSX to give you six bytes and that gives you the 22 bytes to compare against QWHCTOKN.


Correlation with IMS DB
DBCTL supplies CICS with monitoring data, which can then be output to the CICS monitoring domain.
Monitoring data is output to the CICS monitoring domain in the following situations:
• When CICS receives the response to a PSB schedule request from DBCTL, it checks whether this task has already been scheduled successfully to DBCTL. If it has, CICS forces the monitoring data from the previous PSB schedule out; that is, it writes the performance class record for the task and resumes monitoring that task. If it has not been scheduled before, no monitoring processing is done.
• When CICS receives a response from the DBCTL as a result of a COMMIT or ABORT request, CICS outputs the monitoring data, but does not write it.
• In the case of the final PSB schedule for a task, the monitoring data is automatically written at the end of a task

See https://www.ibm.com/support/knowledgecenter/SSGMCP_5.5.0/monitoring/dfht4c0070.html

For the data returned, see https://www.ibm.com/support/knowledgecenter/SSGMCP_5.5.0/monitoring/dfht4a6.html