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 Delivered
Workspace CICS Transaction Server for z/OS
Categories Runtime
Created by Guest
Created on Feb 17, 2013

RELATED IDEAS

allocate commarea above the line when XCTL

Customer had SOS in below the 16M storage.
The storage allocated below the line were commarea. Many transactions were waiting for file for a long time because of slow DASD response and transactions were building up. Most of transactions executed XCTL to a program where the file IO were waiting, which made many large piece of storage for commarea being allocated in the below the line storage, caused SOS.
The application programming guide states;
"When XCTL is used, CICS ensures that any COMMAREA is addressable by the program that receives it, by copying it below the 16MB line."

I understand IBM has been working hard to relieve the virtual storage constraint. Is this something can be enhanced?

I'd like to suggest;
1. When perform XCTL, inquire the called program's definition for DATALOCATION, if it's defined as ANY then allocate COMMAREA above the line or,
2. Add COMMLOCATION(BELOW|ANY) parameter in the program definition so that the XCTL command can inquire the commarea location and allocate the storage accordingly.

Idea priority Medium
  • 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
    |     Feb 19, 2013

    This requirement is satisfied in CICS TS 5.1 which was generally available from December 14th 2012.

    The Commarea for an XCTL command will be in 31 bit storage if the receiver is amode(31).

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.