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 Not under consideration
Categories Runtime
Created by Guest
Created on Feb 23, 2017

In CICS: Allow products, like CICS VT, to be driven at end of task processing and before the syncpoint.

CICS VT intercepts CICS File Control requests in the File Contol GLUEs and converts them to DB2 requests. These are leaving the DB2 cursors OPEN.
When the task reaches end of task syncpoint, Recovery Manager calls DB2 to PREPARE and COMMIT before the RMI RMRO call for COMMIT to call the end of task TRUEs.
This is too late for CICS VT to tell DB2 to CLOSE the cursors. When a subsequent transaction picks up the same thread, there is a partial signon to deal with the OPEN cursors.
This causes an SMF 101 record to be cut and the volume of these can be considerable in a busy region.
What is required is the ability for a product, like CICS VT, to be driven at end of task processing and before the syncpoint. This would allow CICS VT to know that the application had completed its File Control requests and so it could then instruct DB2 to perform its necessary housekeeping before the syncpoint. Today no such exit point exists.

Idea priority High
  • Guest
    Reply
    |
    May 29, 2017

    Checking with DB2 colleagues, there is a way to suppress DB2 101 records, namely when starting accounting you can specify XPLAN(plan-name) on the start command, but that would mean:
    1) You would no accounting records for that plan at all (so not just the 'premature' ones will be suppressed)
    2) A lot of customers start the DB2 accounting trace when DB2 starts (via ZPARM setting) - If you do that, there is NO option to suppress certain plans.
    In that case you would have to stop using the ZPARM and have some automation in place that detects that DB2 is started
    (there is a DSN9022I msg - start db2 normal completion (or something like that)) that they can use as a trigger for automation to issue the start trace(a) xplan(yy) command.

    Would suppressing accounting in this way be a way round the problem ?