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 4, 2019

Enhance EXEC CICS ASSIGN with ASRABEAR option

The EXEC CICS API for ASSIGN returns many data items related to program checks (e.g. ASRAKEY, ASRAINTRPT, ASRAREGS, ASRAPSW, etc).

But the one item that is not available to the ASSIGN API, that would be of great benefit for solving a wild branch, is the BEAR (Breaking Event Address Register).

It could be requested either as

EXEC CICS ASSIGN ASRABEAR(8-bytes).

Idea priority Low
  • Guest
    Reply
    |
    Jan 8, 2020

    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.

  • Guest
    Reply
    |
    Sep 5, 2019

    This is the same as RFE 73322.

    All this information, and a lot more, is provided in the TACB which is available in the various XPCABND related global user exits as well as the PEP. The TACB (and an abend can create more than one!) is where we've always added new abend related information; not only is the BEAR in there but there's also things like the TEA (useful for 0C4s), application context (where applicable), and now the vector registers and so on. These global user exits and the PEP are driven very close to when the actual abend occurred, any sort of processing in a HANDLE ABEND PROGRAM is always going to be a suspect since a lot may have happened in between. Doing something in the XPCxxx GLUEs and/or the PEP is going to be a much more useful, more accurate and is where we will generally add new information as/when required (vector registers being a recent case in point).