Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Delivered
Categories Runtime
Created by Guest
Created on Mar 26, 2020

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

The requirement is to monitor end-to-end access from requester to the databases. The audit information must be available in real time to a Security Information and Event Management system (QRadar). Monitoring is for both inbound and outbound access to and from the mainframe. Auditors need the ability to correlate the user ID, the transaction or application, and the database access.

Idea priority High
  • Guest
    Reply
    |
    Jun 17, 2022
    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
  • Guest
    Reply
    |
    Apr 5, 2022
    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
  • Guest
    Reply
    |
    Mar 19, 2021

    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

  • Guest
    Reply
    |
    Nov 13, 2020

    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.

  • Guest
    Reply
    |
    May 11, 2020

    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