Skip to Main Content
IBM Data and AI Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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 ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


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.

IBM Employees should enter Ideas at https://ideas.ibm.com


Status Needs more information
Created by Guest
Created on Jul 5, 2023

REBUILD - After recovery of TS is NPSI improvement

Recovered SEMHNSA Partition 1 which has a NPSI. Rebuild has no idea that only partition 1 was recovered and rebuilds all the partitions for NPSI XEMHUNSA. Believe improvements need to be made to make the REBUILD know that only partition 1 needs to be rebuilt and the non-recovered partitions needs only to be unloaded and loaded back to the NPSI. This should work similar to REORG where only partitions that are being reorged are unloaded/sorted and others partitions in the NPSI are just unloaded.

Needed By Quarter
  • Guest
    Reply
    |
    Feb 20, 2024

    Opened case. This is a defect.

  • Guest
    Reply
    |
    Feb 20, 2024

    When the following is run, REBUILD only does the partitions in the listdef.


    LISTDEF RECOVERX

    INCLUDE TABLESPACE DLOADMB1.SMBMMEE

    PARTLEVEL (616,631,686,742)


    RECOVER LIST RECOVERX

    TOLOGPOINT X'00000000C17235531C14' PARALLEL 4

    REBUILD INDEXSPACE LIST RECOVERX SCOPE PENDING


    When the following is run, the RECOVERY utility will only recover PARTLEVEL (616,631,686,742), but the REBUILD will do all partitions. I was wondering if there was a way to have the information passed from the RECOVER to the REBUILD so that the REBUILD only does the recovered partitions. The information is in SYSCOPY.

    LISTDEF RECOVERX

    INCLUDE TABLESPACE DLOADMB1.SMBMMEE


    RECOVER LIST RECOVERX

    TOLOGPOINT X'00000000C17235531C14' PARALLEL 4

    REBUILD INDEXSPACE LIST RECOVERX SCOPE PENDING

  • Guest
    Reply
    |
    Dec 4, 2023

    Rebuild step shows every logical part of the NPSI is being rebuilt. Should this be a bug instead of an idea?

  • Guest
    Reply
    |
    Dec 4, 2023

    XEME4PR1 and XEME5PR1 are NPSIs and the logical part are in RBDP, but REBUILD does the whole NPSI. I have the whole joblog but don't see how to attach it.

    DSNT360I > ***********************************

    DSNT361I > * DISPLAY DATABASE SUMMARY

    * GLOBAL

    DSNT360I > ***********************************

    DSNT362I > DATABASE = DDV99EM1 STATUS = RW

    DBD LENGTH = 2394524

    DSNT397I >

    NAME TYPE PART STATUS PHYERRLO PHYERRHI CATALOG PIECE

    -------- ---- ----- ----------------- -------- -------- -------- -----

    XEME1PR1 IX 0001 RW

    -THRU 0031

    XEME1PR1 IX 0032 RW,RBDP

    XEME1PR1 IX 0033 RW

    -THRU 0152

    XEME1PR1 IX

    XEME2PR1 IX 0001 RW

    -THRU 0031

    XEME2PR1 IX 0032 RW,RBDP

    XEME2PR1 IX 0033 RW

    -THRU 0152

    XEME2PR1 IX

    XEME3PR1 IX 0001 RW

    -THRU 0031

    XEME3PR1 IX 0032 RW,RBDP

    XEME3PR1 IX 0033 RW

    -THRU 0152

    XEME3PR1 IX

    XEME4PR1 IX L0001 RW

    -THRU 0031

    XEME4PR1 IX L0032 RW,RBDP*

    XEME4PR1 IX L0033 RW

    -THRU 0152

    XEME4PR1 IX L*

    XEME5PR1 IX L0001 RW

    -THRU 0031

    XEME5PR1 IX L0032 RW,RBDP*

    XEME5PR1 IX L0033 RW

    -THRU 0152

    XEME5PR1 IX L*

    XEMEUPR1 IX 0001 RW

    -THRU 0031

    XEMEUPR1 IX 0032 RW,RBDP

    XEMEUPR1 IX 0033 RW

    -THRU 0152

    XEMEUPR1 IX


    DSNU551I > 338 15:45:36.11 DSNUCRUL - INDEX NAME= DV99.XEME4PR1 PART=13 IS EMPTY

    DSNU555I > 338 15:45:36.11 DSNUCRUL - UNLOAD PHASE STATISTICS - NUMBER OF RECORDS PROCESSED=0

    DSNU705I 338 15:45:36.12 DSNUCRIB - UNLOAD PHASE COMPLETE - ELAPSED TIME=00:00:00

    DSNU349I > 338 15:45:36.17 DSNURBXZ - BUILD PHASE STATISTICS - NUMBER OF KEYS=0 FOR INDEX DV99.XEME4PR1

    DSNU349I > 338 15:45:36.18 DSNURBXZ - BUILD PHASE STATISTICS - NUMBER OF KEYS=0 FOR INDEX DV99.XEME5PR1

    DSNU3350I 338 15:45:36.18 DSNUGSRP - SORT TASK SW02: 0 RECORDS SORTED, ESTIMATED 0, VARIATION -1 PERCENT

    DSNU3352I 338 15:45:36.18 DSNUGSRP - SORT TASK SW02: USED DFSORT

    DSNU3354I 338 15:45:36.18 DSNUGSRP - SORT TASK SW02: MEMORY BELOW THE BAR: OPTIMAL 6 MB, USED 6 MB

    DSNU3350I 338 15:45:36.18 DSNUGSRP - SORT TASK SW01: 0 RECORDS SORTED, ESTIMATED 0, VARIATION -1 PERCENT

    DSNU3352I 338 15:45:36.18 DSNUGSRP - SORT TASK SW01: USED DFSORT

    DSNU3354I 338 15:45:36.18 DSNUGSRP - SORT TASK SW01: MEMORY BELOW THE BAR: OPTIMAL 6 MB, USED 6 MB

    DSNU391I 338 15:45:36.19 DSNUCRIB - SORTBLD PHASE STATISTICS. NUMBER OF INDEXES = 2

    DSNU392I 338 15:45:36.19 DSNUCRIB - SORTBLD PHASE COMPLETE, ELAPSED TIME = 00:00:00

    DSNU3357I 338 15:45:36.24 DSNUGULM - MAXIMUM SORT AMOUNT ESTIMATION VARIATION WAS 0 PERCENT

    DSNU3355I 338 15:45:36.24 DSNUGULM - TOTAL SORT MEMORY BELOW THE BAR: OPTIMAL 12 MB, USED 12 MB

    DSNU1039I 338 15:45:36.24 DSNUGULM - PROCESSING LIST ITEM: TABLESPACE DDV99EM1.SEMEPR1 PARTITION 14

    DSNU3340I 338 15:45:36.30 DSNUCRIB - UTILITY PERFORMS DYNAMIC ALLOCATION OF SORT DISK SPACE

    DSNU395I 338 15:45:36.39 DSNUCRIB - INDEXES WILL BE BUILT IN PARALLEL, NUMBER OF TASKS = 5

    DSNU3345I 338 15:45:36.39 DSNUCRIB - MAXIMUM INDEX PARALLELISM IS 5 BASED ON NUMBER OF INDEXES

    DSNU3342I 338 15:45:36.39 DSNUCRIB - NUMBER OF OPTIMAL SORT TASKS = 2, NUMBER OF ACTIVE SORT TASKS = 2

    DSNU551I > 338 15:45:36.41 DSNUCRUL - INDEX NAME= DV99.XEME5PR1 PART=14 IS EMPTY

    DSNU555I > 338 15:45:36.41 DSNUCRUL - UNLOAD PHASE STATISTICS - NUMBER OF RECORDS PROCESSED=0

    DSNU705I 338 15:45:36.41 DSNUCRIB - UNLOAD PHASE COMPLETE - ELAPSED TIME=00:00:00

    DSNU349I > 338 15:45:36.43 DSNURBXZ - BUILD PHASE STATISTICS - NUMBER OF KEYS=0 FOR INDEX DV99.XEME4PR1

    DSNU3350I 338 15:45:36.44 DSNUGSRP - SORT TASK SW02: 0 RECORDS SORTED, ESTIMATED 0, VARIATION -1 PERCENT

    DSNU3352I 338 15:45:36.44 DSNUGSRP - SORT TASK SW02: USED DFSORT

    DSNU3354I 338 15:45:36.44 DSNUGSRP - SORT TASK SW02: MEMORY BELOW THE BAR: OPTIMAL 6 MB, USED 6 MB

    DSNU349I > 338 15:45:36.46 DSNURBXZ - BUILD PHASE STATISTICS - NUMBER OF KEYS=0 FOR INDEX DV99.XEME5PR1

    DSNU3350I 338 15:45:36.46 DSNUGSRP - SORT TASK SW01: 0 RECORDS SORTED, ESTIMATED 0, VARIATION -1 PERCENT

    DSNU3352I 338 15:45:36.46 DSNUGSRP - SORT TASK SW01: USED DFSORT

    DSNU3354I 338 15:45:36.46 DSNUGSRP - SORT TASK SW01: MEMORY BELOW THE BAR: OPTIMAL 6 MB, USED 6 MB

    DSNU391I 338 15:45:36.47 DSNUCRIB - SORTBLD PHASE STATISTICS. NUMBER OF INDEXES = 2

    DSNU392I 338 15:45:36.47 DSNUCRIB - SORTBLD PHASE COMPLETE, ELAPSED TIME = 00:00:00

    DSNU3357I 338 15:45:36.50 DSNUGULM - MAXIMUM SORT AMOUNT ESTIMATION VARIATION WAS 0 PERCENT

    DSNU3355I 338 15:45:36.50 DSNUGULM - TOTAL SORT MEMORY BELOW THE BAR: OPTIMAL 12 MB, USED 12 MB

    DSNU1039I 338 15:45:36.50 DSNUGULM - PROCESSING LIST ITEM: TABLESPACE DDV99EM1.SEMEPR1 PARTITION 15

    DSNU3340I 338 15:45:36.56 DSNUCRIB - UTILITY PERFORMS DYNAMIC ALLOCATION OF SORT DISK SPACE

    DSNU395I 338 15:45:36.60 DSNUCRIB - INDEXES WILL BE BUILT IN PARALLEL, NUMBER OF TASKS = 5

    DSNU3345I 338 15:45:36.60 DSNUCRIB - MAXIMUM INDEX PARALLELISM IS 5 BASED ON NUMBER OF INDEXES

    DSNU3342I 338 15:45:36.60 DSNUCRIB - NUMBER OF OPTIMAL SORT TASKS = 2, NUMBER OF ACTIVE SORT TASKS = 2

    DSNU551I > 338 15:45:36.60 DSNUCRUL - INDEX NAME= DV99.XEME5PR1 PART=15 IS EMPTY

    DSNU551I > 338 15:45:36.60 DSNUCRUL - INDEX NAME= DV99.XEME4PR1 PART=15 IS EMPTY

    DSNU555I > 338 15:45:36.60 DSNUCRUL - UNLOAD PHASE STATISTICS - NUMBER OF RECORDS PROCESSED=0


  • Admin
    Chris Pomasl
    Reply
    |
    Oct 17, 2023

    Thank you for submitting this Db2 Utilities Suite for z/OS enhancement request.

    This requirement is in ‘Need More Information’ status.

    Please answer the following request from the development team:

    Today, after a part level PIT RECOVER is performed on the base table space, the associating logical partition of the NPSI is placed into RBDP for subsequent REBUILD INDEX operation. It is up to the end user to decide whether to only rebuild the needed logical partition(s), or rebuild the entire NPSI. So we are not clear on the need for the proposed enhancement unless there is other reasons not documented for further consideration.

    We appreciate your input to the Db2 Utilities Suite for z/OS development team. We also hope that you will continue to submit ideas for improvements as customer feedback is a key component to shaping the future direction of Db2 Utilities Suite for z/OS.

    Sincerely,

    Db2 Utilities Suite for z/OS Team