IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. 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.

Add a new idea Subscribe
Status Delivered
Workspace GDPS
Created by Guest
Created on Oct 22, 2019

RELATED IDEAS

GDPS z/OS Proxy shutdown

Using GPDS V4.1 and V4.2 Metro with z/OS Proxy systems.
Today, when shutting down multiple systems or a site thru a script, the systems are shut down in the following order

1 - stop main sysplex - parallel
2 - stop xDR managed systems - parallel
3 - stop Native Linux

In our case, when we want to shut down a site as quickly as possible thru a script. The site includes both a classic GDPS Metro Sysplex and some GDPS z/OS Proxy systems. The shutdown takes longer than necessary. That is caused by the fact that the main GDPS sysplex and the GDPS z/OS Proxy systems are not shut down in parallel.

In below example, we do a Site1 -> Site 2 move.
Systems in the scripts are
K041 - alternative Ksys
MVST - 'Normal' Asys - in same sysplex as K041
S102 - z/OS Proxy system


15:14:16 S1MAINT PLANNED/STANDARD ACTION STARTED
15:14:16 SYSPLEX='STOP MVST S102 K041' STARTED
15:23:10 XDR STOPZP ACTION INITIALIZED FOR S102
15:28:11 SYSPLEX='STOP MVST S102 K041' ENDED RC=0
15:28:11 SYSPLEX='RESET S102' STARTED
15:28:40 XDR KSYSTEM ACTION INITIALIZED FOR S102
15:28:32 SYSPLEX='RESET S102' ENDED RC=0
15:28:32 DASD='SWITCH HYPERSWAP RESYNCH' STARTED

Systems MVST and K041 are stopped first.
When down, the Proxy system S102 is stopped.
This is causing longer shutdown time than needed.

It would be of great value of there where some way of controlling the shutdown sequence. One way could be to have GDPS Option controlling this, indicating if serial or parallel shutdown should be done.

Idea priority Medium
  • Guest
    Reply
    |     Apr 15, 2022
    This requirement is satisfied by GDPS Metro 4.5 which is generally available on March 31, 2022.
  • Guest
    Reply
    |     Apr 30, 2020

    Although my prior comment said we had no plans to use z/OS Proxy in discussing this more recently with Bengt he says this RFE would also be applicable to VM x/DR shutdown in parallel with z/OS - which makes this RFE of high importance to us because of impact to RTO on region switching.

  • Guest
    Reply
    |     Jan 30, 2020

    N/A, no z/OS proxy systems

  • Guest
    Reply
    |     Jan 28, 2020

    low - Currently dont use GDPS scripts for site swaps but this would make it a viable option

  • Guest
    Reply
    |     Jan 15, 2020

    Don't use z/OS Proxy

  • Guest
    Reply
    |     Jan 14, 2020

    We don't use proxy systems.

  • Guest
    Reply
    |     Jan 14, 2020

    Low priority as we do not use a proxy system.

  • Guest
    Reply
    |     Jan 8, 2020

    This is our 3rd ranked item for Batch 11.

    Controlling the shutdown sequence and speeding the overall shutdown should be available.

  • Guest
    Reply
    |     Jan 7, 2020

    Low. No use of z/OS proxy feature

  • Guest
    Reply
    |     Jan 7, 2020

    We are not users of proxy systems at this time.

  • Guest
    Reply
    |     Dec 10, 2019

    High - I agree in total with the requester

  • Guest
    Reply
    |     Dec 9, 2019

    Medium - More parallelism is always an advantage I think.

  • Guest
    Reply
    |     Dec 6, 2019

    LBG
    Priority Medium.

  • Guest
    Reply
    |     Dec 3, 2019

    Would decrease our outage times for site swaps

  • Guest
    Reply
    |     Dec 2, 2019

    This is low priority for us. Our proxy usage pre-dates the STOP option for z/OS Proxy, so our established procedures are already working to our satisfaction.

    While having the option for GDPS to issue the shutdown command for each system might save a small amount of operation interaction, when we do a wide shutdown (for 4-site region switch) we have enough console operator manpower available because it is a time-sensitive scenario.

  • Guest
    Reply
    |     Dec 2, 2019

    We've also noticed this worse behaviour of GDPS Metro V4 compared to GDPS/PPRC V3.14 for xDR with z/VM.
    A xDR z/VM system was shut down AFTER ALL z/OS Systems were shutdown.
    This is totally the opposite of what is targeted by the GDPS Design Council RTO Workgroup.
    A timing example showed in the SDF trace:

    16:46:18 SYSPLEX='STOP MVS1 ZVM1' STARTED
    16:54:39 START OF PHASE 1, STOP SA MP PRODUCTION CLUSTERS
    16:56:37 SYSPLEX='STOP MVS1 ZVM1' ENDED RC=0

    In this example we lose 2 minutes by the current serialization of shutdowns.

    For FI this is a HIGH priority issue.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.