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 Dec 11, 2011

CICSVR V4.2 use of CLIST for generating forward recovery JCL.

The customer's application, by design, uses DASD only log streams to log after images from the onlines. When using the CICSVR CLIST to generate forward recovery JCL, the CLIST automatically executes a scan of every DFHLGLOG defined to the RCDS control file. This is a problem because these are DASD only log streams and the scan will fail if the user is on the wrong LPAR. The user will always be on the wrong LPAR for a particular DFHLGLOG as the CLIST scans the entire list. Customer has strict standards as there is one DFHLGLOG per CICS region.

This new requirement enables the support personnel to generate forward recovery JCL using the CICS VR CLIST by selecting the specific DFHLGLOG(s) to scan.

Change the CLIST to present a screen to the user that allows him/her to select the particular DFHLGLOG to scan. Although we currently only have a requirement to select one DFHLGLOG, IBM can provide the feature to select multiple logs in case this is necessary in the future.

Idea priority Medium
  • Guest
    Reply
    |
    Mar 25, 2021

    This function has been delivered via APAR PH34215 to CICS VR 5.2.

  • Guest
    Reply
    |
    Aug 20, 2020

    Yes, this is something we would like to do. The status of the RFE is being moved into Planned for a future release.
    Please note the following:
    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
    |
    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 - Enterprise Tooling
    Product - CICS VSAM Recovery

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Enterprise Tooling
    Product - CICS VSAM Recovery

  • Guest
    Reply
    |
    Dec 12, 2011

    This is something we would like to address in a  future release.