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 Other
Created by Guest
Created on Oct 15, 2014

Experiencing SOS in EDSA Storage not releasing

A transaction is a mirror transaction that reads file SRSEVENT. After SOS condition, we see the transaction abending with an AFCI. We are seeing the storage in ECDSA did not free. We were curious why Storage did not free after the transaction abended .
The transaction was making a request EXEC CICS READ UPDATE for the same record. The design of CICS File Control is that these control blocks are not actually owned by a task, they are owned and managed by CICS. When a task needs to get a VSWA or FRTE it either gets one off the free chain or GETMAINs a new one if none is available. When the task completes it places the control block back onto the free chain. This explains why the storage was not released when the rouge task was purged. CICS File Control has worked, according to this design, for a very long
time now, however this issue does demonstrate that this there is scope for improvement

Idea priority High
  • Guest
    Reply
    |
    Mar 1, 2021

    This requirements has been re-assessed. We have no plans for this to be implemented and so this requirement is being declined at this point. The requirement will be kept in the RFE system and might be reassessed in the future. You also have an opportunity to resubmit in twelve months time if you wish it to be reconsidered then.

  • Guest
    Reply
    |
    Oct 5, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Transaction Processing
    Product - CICS Transaction Server

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Transaction Processing
    Product - CICS Transaction Server

  • Guest
    Reply
    |
    Oct 20, 2014

    This is a candidate for a future release.