Skip to Main Content
IBM Z Hardware and Operating Systems Ideas Portal


This is the public portal for all IBM Z Hardware and Operating System related offerings. 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 Future consideration
Workspace z/OS
Categories DFSMS OCEOV
Created by Guest
Created on Dec 19, 2019

Abend0C4 in IFGDEBLK+13C at level UA97888 without FRR established

Client is worried that CLOSE abends without RECOVERY ROUTINE ESTABLISHED
as indicated by Software Logrec Record for ABEND0C4 at IFGDEBLK+13C (DEBCHECK during CLOSE) with: „THERE WAS NO RECOVERY ROUTINE ESTABLISHED."
Details:
A user program run in ABEND0C4 in LE (Language Environment).
LE ABEND0C4 was being handled in RTM and percolation to task termination (IFG0TC0A).
During task termination a CLOSE is done by CSECT IFG0TC0A+151A (UA97327) for a JES2 SYSOUT DS.
During CLOSE ABEND0C4 in IFGDEBLK+13C (UA97888) occured without RECOVERY ROUTINE established indicated by LOGREC entry.
Reason for ABEND0C4 in IFGDEBLK+13C was: SUB SYSTEM ACB was overlaid
Note:
Case was already discussed with development.
They were surprised that CLOSE does not correctly handle a bad DCB or ACB address or an overlaid DCB or ACB, and accepted an RFE to change this.

Idea priority Medium