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 Delivered
Workspace CICS VSAM Recovery for z/OS
Categories Runtime
Created by Guest
Created on Apr 2, 2012

RELATED IDEAS

CICSVR needs to be re-architected to allow only 1 unique module for DWW1SCSR and DWW1VS00.

It seems that there is this documentation that states the CICSVR library
(LPA) must be installed (placed) prior to the MVS (zos) library per
item http://www-01.ibm.com/support/docview.wss?uid=swg21192432
Our MVS Team has brought this to our attention as an AUDIT item and
needs to be corrected.
Following is what they have stated;
Create an exit point like most products use. Then if the exit is not
there, the product does not come in. A usermod does not satisfy, CICSVR
maint to module and ZOS Maint to module. ZOS usermod would never see
the CICSVR change.When other products do a usermod, they basically
create a dynamic exit. So it never changes. Then CICSVR maint never
touches the usermod unless they change their interface. Then ZOS
usermod works. Any ZOS change hits and it will not go on till we remove
the usermod. This according to our MVS Team is unacceptable. We have an AUDIT item that duplicates LPA module cannot exist. Also
conflicting is installation by two separate products.

Per previous discussion, it the CICSVR module is bad, the image will
not IPL.
Again, unaccpted.

Suggestion: Support a standard exit that CICSVR will be called if it
exist like most products used. Or create a standard usermod for ZOS
that can call the CICSVR routine and does not come up if module not
found.

Both cases solves duplication and does not touch the normal IPL
process.

Idea priority Medium
  • 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
    |     Jun 13, 2014

    This requirement is satisfied by CICS VR 5.2 which is general available from date of June 13th 2014.

  • Guest
    Reply
    |     Apr 8, 2014

    This requirement is satisfied by CICS VR 5.2 which was announced 7th April 2014 with a planned general availability date of June 13th 2014. For more information see the IBM CICS Tools for  z/OS, V5.2 announcement letter

    http://www.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an&subtype=ca&supplier=897&letternum=ENUS214-153

    DFSMS apar OA42354 is also required to be applied.

  • Guest
    Reply
    |     Feb 7, 2014

    The problem of duplicate modules names and having to specify libraries in the right order, will not be solved using exits. A future releases of CICS VR could rename the modules in question. DFSMS could be changed to detect the presence or not of CICS VR. This can be achieved in a way that provides compatibility with old and new releases of CICS VR. This removes the duplicate module problem and the requirement to have libraries in a certain order.

    This is something we would like to address. The RFE is being moved into 'Planned for Future release' status.  Please note:
    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
    |     Feb 7, 2014

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - Enterprise Tooling
    Product - CICS VSAM Recovery
    Component - Runtime

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Transaction Processing
    Product - CICS Transaction Server
    Component - Other

  • Guest
    Reply
    |     Apr 12, 2013

    The problem of duplicate modules names and having to specify libraries in the right order, will not be solved using exits. A future releases of CICS VR could rename the modules in question. DFSMS could be changed to detect the presence or not of CICS VR. This can be achieved in a way that provides compatibility with old and new releases of CICS VR. This removes the duplicate module problem and the requirement to have libraries in a certain order.

    This is something we would like to address. The RFE is being moved into 'Planned for Future release' status.  Please note:
    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
    |     May 17, 2012

    This is a candidate for inclusion in a future release.

  • Guest
    Reply
    |     Apr 4, 2012

    This is a CICS VR requirement. For future reference CICS VR requirements should be raised under Product family of Enterprise Tooling and then Product CICS VR.

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.