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 Sep 19, 2012

Enhance EP support to include "implicitly referenced" API fields as well as API calls performed by mirror program

Current EP behavior:
1. Currently, the Event Processing (EP) actual event supported fields are only those fields which have explicitly referenced in the CICS API call.
Other API data which are not part of the API call are not available to the EP Adapter (EPA).
2. Although optional API fields might not be available during execution time, the EP editor does not warn the user about it.
3. An optional API field that was referenced as a source field for event data extraction but actually not available to EPA at run time because it was not referenced in the API call,
is still referenced by the Event Descriptor container, although its related data container (e.g. DFHEP.DATA.nnnnn) does not exist.
This behavior leads to an error (Resp=110, Resp2=10) when the EPA is trying to get it.
4. API calls from mirror program (DFHMIRS) are not available to EP at all.
Requested enhancements:
1. Make "implicitly referenced" fields be available to the EPA.
E.g. on RETURN from LINK/XCTL make available the returned COMMAREA and Channel+Containers.
2. On the event editor, please warn the user about referenced fields which might not be available to EPA at run time.
3. Please ensure consistency between Event Descriptor container and its related DATA containers.
4. Please make mirror program API calls available for EP mechanism.

Idea priority High
  • Guest
    Reply
    |
    May 7, 2020

    This requirement has been re-assessed. It is not likely that this will be implemented in the next 12-24 months and so it 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