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 Oct 30, 2018

Remove 24 kb limit on COMMAREA if using DFHTRANSACTION channel

If a DFHTRANSACTION channel is specified the COMMAREA size should not exceed 24 KB.
If exceeding, the abend AXGE is issued (this has been introduced in apar PI76708).
We ask to remove this restriction so we do not have to change the COMMAREA size in
our existing programs.

Idea priority Medium
  • Guest
    Reply
    |
    Jun 12, 2020

    This RFE is satisfied by CICS Transaction Server for z/OS V5.6 which is Generally Available today 12th June 2020.
    For more information see the CICS TS V5.6 Knowledge Center https://www.ibm.com/support/knowledgecenter/SSGMCP_5.6.0/whats-new/intro.html#intro__COMMAREA

  • Guest
    Reply
    |
    Apr 7, 2020

    This RFE is satisfied by CICS Transaction Server for z/OS V5.6 which is announced today 7th April 2020 and which has a planned availability date of 12th June 2020.
    For more information see the CICS TS V5.6 announcement letter
    https://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/7/897/ENUS220-077/index.html&request_locale=en

  • Guest
    Reply
    |
    Sep 9, 2019

    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
    |
    Nov 19, 2018

    This is a candidate for a future release beyond the one currently in development..

  • Guest
    Reply
    |
    Oct 31, 2018

    I agree with this. We got bit when I added a DFHTRANSACTION container and an important transaction started to abend - although we didn't see this until the change was moved into production. It seems like the AXGE abend is based on a number of different variables, so it may happen at 26k in one region, or 30k in another (which is why we didn't see it in test). That calculation is not advertised, so we can't control the abends other than to always ensure we are below 24k. I believe the choice to change the commarea limit in different situations is not a good one, and to go back to an application and ask them to change their commarea length because the rules have changed is against the long standing tradition of backwards compatibility. This application has since eliminated their 30k commarea but we are still waiting to reenable DFHTRANSACTION containers, so there could be more to come.