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/VM
Created by Guest
Created on Nov 20, 2017

z/VM 6.4 SSI PDR

z/VM 6.x SSI Persistent Data Record.
Okay, we Flash all of our z/VM DASD while z/VM is Active and then back those Flashed DASD to tape. So, we restore all the volumes at our Disaster Recovery Site and then try to IPL the first z/VM 6.x SSI member into the SSI but fail because the PDR thinks all the SSI members are active because they were when we performed the Flash of the z/VM DASD. I want functionality built into CP that would give you the option, just like the JES2 on z/OS XCF Sysplex messages listed below, where it gives you the option to continue the initialize or not when it does not know the status of the other members in the MAS, SYSPLEX, etc. We don't want to recreate or repair the PDR. We want CP to give us the option to reinitialize the PDR and SSI if it can't determine the status of the z/VM SSI members.

z/OS SYSPLEX
IXC405D
REPLY I TO INITIALIZE THE SYSPLEX, J TO JOIN SYSPLEX sysplex-name, OR R TO REINITIALIZE XCF

JES2
CKPT1 556
(SYS1.HASPCKPT ON JES2K1)
*$HASP405 JES2 IS UNABLE TO DETERMINE IF OTHER MEMBERS ARE ACTIVE
*045 $HASP420 REPLY 'Y' IF ALL MEMBERS ARE DOWN (IPL REQUIRED), 'N' IF
R 045,Y
IEE600I REPLY TO 045 IS;Y

Idea priority Medium
  • Guest
    Reply
    |
    Aug 18, 2020

    See comments below.

  • Guest
    Reply
    |
    Mar 27, 2019

    Yes, it does. Sorry for the late response and thank you for this information.

  • Guest
    Reply
    |
    Nov 27, 2017

    Sorry - should have said "If you are CERTAIN that the other members are indeed down".

  • Guest
    Reply
    |
    Nov 27, 2017

    Are you aware of the CLEARPDR IPL parameter? It causes the PDR to be reinitialized, after prompting you to ensure that the other cluster members are down, enabling the first member to come up in the DR site. Here's the recommended procedure to use:

    On the first SSI member, in the parameter field on the HMC Load panel, specify the console which you want z/VM to use
    when IPLing, and continue with the Load. This will bring you to the Stand Alone Program Loader (SAPL) panel. In the IPL
    PARAMETERS section, add the CLEARPDR parameter. Do not alter any existing parameters. Continue with the IPL using
    PF10. (For more information on CLEARPDR, see the System Operation manual, Chapter 2, Using the Stand Alone Program
    Loader).

    The CLEARPDR parameter will cause the following messages to be displayed:

    HCPASK1660I CLEARPDR IPL parameter specified. All other systems in the SSI cluster must be shut down.
    HCPASK1634A If any other systems in the SSI cluster are running,
    HCPASK1634A system integrity will be compromised and data
    HCPASK1634A corruption may occur.
    HCPASK1634A Confirm that the following systems are shut down:
    HCPASK1634A
    HCPASK1634A Confirm the persistent data record (PDR) is located
    HCPASK1634A on volume
    HCPASK1634A Enter GO to continue with the clearing of the PDR.
    HCPASK1634A After that normal IPL continues. To abort the IPL,
    HCPASK1634A enter STOP.

    If you are CERTAIN that the other member is indeed down, issue "GO" and continue with the IPL. Otherwise, issue "STOP"
    and contact IBM support personnel before proceeding.

    When the first member has completed IPL, IPL the other members normally. IMPORTANT: Do NOT use the CLEARPDR
    parameter when IPLing on the other SSI members.

    Does this address the requirement? If not, why not?

    --Romney White, IBM