Skip to Main Content
IBM Z Hardware and Operating Systems Ideas Portal


This is the public portal for all IBM Z Hardware and Operating System related offerings. 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 Future consideration
Workspace z/OS
Categories BCP_IOS
Created by Guest
Created on Nov 16, 2023

SPOF health checker support for multivolume datasets and provide selection pattern

1) for DB2 LOGCOPY it is recommended to allocate a stripe format dataset

     The SPOF health checker should check that all of the volumes for DSN1 are on different CUs than for DSN2

     Example : Disk Controller : CU1 with Volser V1, V2 and CU2 with Volser V3, V4

     CU1: V1,  V2

     CU2: V3,  V4

    LOGCOPY1.DS36 : Volser   V1,  V2V3,  V4

    LOGCOPY2.DS36 : Volser   V3,  V4V1,  V2

    Currently only the first volumes are checked, result: LOGCOPY1 and LOGCOPY2 are on different CUs

    The health checker should check all volumes of the multivolume dataset: result: LOGCOPY1 and LOGCOPY2 are on the same CU

 

2) with a wildcard : '=' the same suffix of  DSN1, DSN2 should be checked

    The list is clearer and all datasets are checked

   Example: LOGCOPY1.DS01 to DS036 checked with LOGCOPY2.DS01 to DS36 

   Instead of writing

   DSN1(LOGCOPY1.DS01)

   DSN2(LOGCOPY2.DS01)

   …..

   DSN1(LOGCOPY1.DS36)

   DSN2(LOGCOPY2.DS36)  

  replace with

   DSN1(LOGCOPY1.=)   

   DSN2(LOGCOPY2.=) 

 

   

   

    

    

Idea priority Medium