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 17, 2016

Improve CONFIGxx PARMLIB member processing for PPRC environments

Background:
Currently CONFIGxx members are maintained manually by FI for every system in the sysplex with names CONFIG&SYSCLONE. These members contain desired states for
1. Storage and CPU's that are to be online.
2. Channel paths that should be online.
3. Devices that should be online resp. offline
4. Volser's of important devices (Sysres e.g.).

For devices PPRC'ed and managed by GDPS the status for
a) a PPRC primary device is defined as online in CONFIGxx.
b) a PPRC secondary device is defined as offline in CONFIGxx.
The assumption here is that all systems within one sysplex (except the GDPS controlling system) have the same DASD configuration.

The members are used to verify if the running system complies to the currently defined configuration in the CONFIGxx member and detect misconfiguration / prevent problems e.g. after an IPL with an unreflected dynamic change.
This is done via "D M=CONFIG(xx)" command twice a day

The manual "System Commands" states:
"CONFIG[(xx)]
The system is to display the differences between the current configuration
and the configuration described in the CONFIGxx parmlib member."

Idea priority Medium