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 Not under consideration
Categories z/TPFDF
Created by Guest
Created on Mar 28, 2014

CRUISE should allow the aggregation of smaller tables into one large super table or a table of tables

CRUISE should allow aggregation of smaller tables into one large super table or a table made up of other tables. This would allow multiple tables to be run as a single job from start to finish.
Instead of taking REF-ID parameters as input, the Super Table (or System Table) would take other CRUISE Tables as arguments. These tables would then be run serially. When one completes the next one would be started. Appropriate status and completion messages would be displayed at the start and end.
This could be restricted just to CAPTURE or could also be allowed for a VERIFY function.
For the “CAPTURE”, one common set of BFA tapes would be generated. However, there would be a marker or separator record between the end of one individual table and the start of the next. This will allow the RESTORE to work in stages. Each individual table would be restored from start to finish before reading the next set of data records from the BFA tape.
This will result in smaller XREF files and keep them from getting too large and needing a very large allocation. This will improve the performance of the file address exchange phases of the restore (FAD EXCHANGE). When one table restore is finished the XREF files would be initialized.

Idea priority Medium
  • Guest
    Reply
    |
    Oct 14, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - z Systems Software
    Product - z/TPF

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Transaction Processing
    Product - z/TPF

  • Guest
    Reply
    |
    May 20, 2014

    We feel that a lot the functionality described (running multiple CRUISE tables serially) can be achieved today using automation. One of the benefits described is to have smaller XREF files to improve performance. We believe we can make a change to improve the performance of processing the XREF files that will apply to all of CRUISE processing, not just when it is desired that multiple tables are run. We would include that as part of RFE 4908, which specifically targets how CRUISE cross-reference files are allocated and used. The biggest part of the requirement that would not be addressed is the request for a common set of BFA tapes to be used to process multiple tables.

    Due to resources and priority, IBM does not intend to do this in the forseeable future.