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 Nov 26, 2020

Identify the jobnames of the batch requests via EXCI.

Customer would like to identify the jobnames of the batch requests via EXCI.
He suggested to put this information in the PHAPPLID (APPLID from previous hop data) field and additionaly in the DFHSN1500 message.
Customer has pointed that there is a WUI field "EXCI client identifier" from EXCI Resource Table
that already provides this information in-flight.
With this information in the SMF110 records (PHAPPLID field) would be possible to build historical reports (via CICSPA, e.g.) and map the main jobnames that issue EXCI requests to the CICS regions.

Idea priority Medium
  • Guest
    Reply
    |
    Jul 6, 2022
    This requirement specifically concerned EXCI requests from non CICS regions calling CICS. You do not use EXCI from CICS regions.

    For CICS to CICS communications the PHAPPLID field in the origin data already reports the APPLID of the calling CICS region. This requirement addresses the case of non CICS client using EXCI to call CICS. In this case the PHAPPLID field contains the jobname of the non CICS client.
  • Guest
    Reply
    |
    Jun 27, 2022

    Hello. Please, do you know if this feature will also identify the applid from external CICS regions?

    Thank you. Paulo

  • Guest
    Reply
    |
    Jun 17, 2022
    Support for this is provided in CICS TS 6.1 which is generally available from 17th June 2022.

    For more information see https://www.ibm.com/docs/en/cics-ts/6.1?topic=whats-new
  • Guest
    Reply
    |
    Apr 5, 2022
    Support for this is provided in CICS TS 6.1 which is announced today April 5th and will GA June 17th 2022.

    See Announcement letter https://www.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/2/897/ENUS222-092/index.html&request_locale=en
  • Guest
    Reply
    |
    Apr 29, 2021

    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
    |
    Jan 25, 2021

    This is a candidate for a future release

  • Guest
    Reply
    |
    Nov 26, 2020

    Attachment (Use case)