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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
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 Transparency
For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - Enterprise Tooling
Product - CICS VSAM Transparency
Rejecting this for now as no other customer has raised this.
Further details from Jeff Sullivan from the original requirement:
CICS Transparent VSAM ability to clone DIM for same table name but different owner.
If a customer has separate VSAM files for test and production, and the files are identical in mapping in both test and production, and the customer wants to keep the same table name in test and production but only wants to rename the owner name to distinguish test and production, it would be far easier to map the table one time, then clone it for all of the other owner (schema) names with their own distinct DIM names.
Business Justification: Even though there is a customer workaround, the ability for the tool to have this as an option would save quite a bit of resource time and would make the product much more marketable. This type of procedure is quite common in standard turnover procedures in order to comply with audits and standards.
Suggested Solution: An option could be added to the manual mapping where the "source" DIM could be referenced, then, the next panel would request the "target" DIM name and the owner. For the user, it would be nice to show, as a non-updated field, the "source" DIM name and the source Owner.Table Name.
The use case is describing the customer pain point. Please describe in detail how such a function would be used.
This will give us a clearer understanding of the interfaces and functions that would have to be provided. Today CICS VT does provide the capability to re-use the generated DIM for files that are clones of each other. This requires the user to make sure the CICS VT DST (Data Set Table) has the correct FCT entry and DIM name for each of the files. With regard to the DDM, are you suggesting that CICS VT needs to provide the capability for this to be automatically re-generated for the files/tables that are clones of each other?