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 Jun 21, 2014

Reuse CEEPIPI enclave during multiple EXEC CICS LINK/RETURNs to/from XPLINK programs within the same CICS task.

Running under 1 CICS task, a Cobol driver program does thousands of EXEC CICS LINKs to a C program (Program1) that is compiled with XPLINK. And each time Program 1 is invoked it does an EXEC CICS LINK to a C program (Program2) that is compiled with XPLINK.

Each EXEC CICS LINK to an XPLINK program builds a new CEEPIPI enclave environment. And each EXEC CICS RETURN from an XPLINK program destroys that environment. So a CICS task designed as described above will build and destroy thousands of CEEPIPI enclave environments. The overhead of that is significant.

The requirement is to save and reuse the CEEPIPI environment for the life of the CICS task so that multiple EXEC CICS LINK invocations of the same program by the same task requires only 1 CEEPIPI enclave.

If this RFE is implemented, in the prior example the CEEPIPI enclave for Program1 is built only once and destroyed only once, and the CEEPIPI enclave for Program2 is built only once and destroyed only once.

Idea priority High
  • Guest
    Reply
    |
    Nov 17, 2016

    Whilst this requirement is valid, based on our current plans and priorities, it is not likely that this could be implemented in the next 12 months, or in the next CICS TS release. Correspondingly 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