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 Not under consideration
Workspace z/OS
Created by Guest
Created on Mar 19, 2024

Add a parameter to control the time allowed between IPLs in different CPCs (message ILR031A)

Hello,
 

(We use z/OS 2.5 and GDPS 4.6)


We use GDPS to perform DR scenarios.

In our DR scenario testing, we've mastered the process and can now perform the whole process in less than 20 minutes. 

We currently DR the Production systems in 21-22 minutes and plan to go below 20 as well soon.

When we IPL the LPARs on the other CPC, we get the following messages:
ILR030A
ILR031A

According to the documentation, this message might appear when a new CPC is detected and the last CPC used the protected datasets less than 20 minutes ago.

We bypassed this problem by adding the ILR031A reply to the Auto Reply mechanism (member AUTORxx in the PARMLIB).

To avoid this false error entirely, I suggest adding a parameter to IECIOSxx (or any other member in the PARMLIB you deem appropriate) to control the time allowed between IPLs in difference CPCs.

I understand the need for this protective mechanism, however, adding a user controlled parameter will enable the user to decide the "intensity" of this protection.  The user will be able to make a knowledgeable decision and avoid what he/she regards as a false error.

Thanks in advance

Idea priority Low
  • Guest
    Reply
    |
    Apr 4, 2024
    .IBM does not see a strong business justification case for implementing the request.
  • Guest
    Reply
    |
    Apr 2, 2024
    IBM does not see a strong business justification case for implementing the request.