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 Jul 6, 2012

Remote SYSID returned to caller after DPL (SHARE requirement SSCICS11013)

CICS should return the region/sysid/applid where the DPL request actually ran to the caller.

Debugging and diagnositics will become much easier, especially in large shops that have dozens or even hundreds of AOR regions.

The SYSID could be provided back to the user in a number of ways:
1)New field in the EIB.
2)New option on a DPL command: EC LINK PROG(xxx) DPLSYSID(ws-aor)
3)Reuse an old field: EX LINK PROG(xxx) SYSID(ws-aor). If sysid is left blank, then CICS knows to invoke CPSM/Dynamic Routing, and then return the actual sysid in the sysid field.

Idea priority Medium
  • Guest
    Reply
    |
    May 5, 2016

    We have assessed this requirement. We have no current plans for this to be implemented and so 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.

    CICS resource monitoring reports the destination of a DPL, or transaction tracking can be used for live transactions.

  • 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
    |
    Nov 25, 2013

    This is Mark Roberts from HSBC.

    One of the extensions to this request I'd also like to see is for CICS to return to the initiator of a LINK (i.e. at link-level 1) the stack of CICS a particular request passed through.

    For example, if we have a delivery channel in CICA and the first application to be invoked in CICB, when a secondary application is invoked by CICB to something residing in CICC, this stack would contain 'CICA'; 'CICB'; 'CICC'.

    Ideally some indication of the times at which we entered and left each CICS would be useful. EIBDATE+EIBTIME would be a good start but something more precise (e.g. the extended timestamp provided by DB2) would be even better.

    Finally, some SMF-like data (e.g. programs accessed via LINKs; transactions started and the CICS region associated with the invoked API) would be useful.

  • Guest
    Reply
    |
    Jul 26, 2012

    I just learned that my "unsupported technique" does not always work (i.e., finding the TCTSE immediately after the LINK command). Having the remote sysid is a huge help with diagnostics.