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.

Add a new idea Subscribe
Status Not under consideration
Workspace CICS Transaction Server for z/OS
Categories Runtime
Created by Guest
Created on May 22, 2017

RELATED IDEAS

A Global User Exit for Program Check Recovery

Can we have a Global User Exit which is driven for program checks in a CICS region, similar to the PROGRAM_CHECK_RECOVERY mechanism which LE uses in its "shunt routines" to test pointers during its CEEDUMP processing.

The consumer (probably an IBM or ISV product) would enable the GLUE at CICS startup.

Whenever a program check occurs, CICS will drive the GLUE, passing:
- the PSW
- registers if easy

The GLUE will decide if it cares about the program check and return with one of two return codes:
- "CICS should not process the program check, but should resume to address XXXXXXXX provided by the GLUE."
- "CICS should continue with normal abend processing"

Naturally several consumers might want to set their own GLUEs, so CICS will call them in sequence, as it does with other GLUES.

I think that it would be acceptable to document a restriction that the GLUE should only be used to determine if a program check should be handled by the GLUE-setter, or continue to be processed by CICS abend processing (and not be used for any other purpose) - and for it to forbid the use of XPI or API.

Idea priority Medium
  • Guest
    Reply
    |     Jun 13, 2017

    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
    |     May 22, 2017

    Tony, this functionality has been available in CICS for decades. Take a look at the DFHPEP user replaceable module, documented here:
    https://www.ibm.com/support/knowledgecenter/SSGMCP_5.3.0/com.ibm.cics.ts.recrestart.doc/topics/dfht23l.html

    Eons ago, back when IBM first made the "macro level" CSA fetch protected, I wrote a version of DFHPEP that would detect the resulting abends and effect a retry of the offending program, allowing it to continue on.

    Rob Garrett

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.