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.

Add a new idea Subscribe
Status Not under consideration
Workspace CICS VSAM Transparency for z/OS
Categories Runtime
Created by Guest
Created on Mar 4, 2016

RELATED IDEAS

COMMIT does not free up the locks owned by all DB2 threads

We have a program with VSAM files migrated to DB2 via CICS VSAM Transparency. These files are read & updated each with their own unique DIM per file. The mainline program is calling a new dynamic subroutine which handles all of the commits by issuing a EXEC SQL COMMIT END-EXEC. To accomplish all of this, the customer had to
change PGM=pgmname to PGM=IKJEFT01 and the SYSTSIN control card points to the same plan that is in the VIDPLAN. The COMMIT program was successfully bound to the database. However, even after issuing the COMMIT, it does not free up the locks owned by all threads.

Development response:
The symptoms reported are CICS VT working as designed. In order to
perform a DB2 commit in the application subtasking must be enabled.
This is to insulate the CICS VT activity from the native DB2
activity. As they noticed when subtasking is active there is a
separate TCB for each DIM that is used and by definition this means
a separate DB2 thread. When the COMMIT is performed it will only
commit the changes made under the application DB2 thread leaving
the CICS VT DB2 threads under the control of CICS VT. When the job
ends these changes will then be committed.

Idea priority High
  • Guest
    Reply
    |     Apr 9, 2020

    I discussed this with CICS VT development and they confirmed that CICS VT is working as designed as described above. No other CICS VT has reported this as an issue.

  • Guest
    Reply
    |     Mar 8, 2016

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Enterprise Tooling
    Product - CICS VSAM Transparency
    Component - Runtime
    Source - Other

    For recording keeping, the previous attributes were:
    Brand - Servers and Systems Software
    Product family - Enterprise Tooling
    Product - CICS Interdependency Analyzer
    Component - Runtime
    Source - Other

  • Guest
    Reply
    |     Mar 5, 2016

    The product says: Product:
    CICS Interdependency Analyzer but it is actually for CICS VSAM Transparency

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.