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 Apr 30, 2012

Additional cleanup for VARY TCPIP,,SYSPLEX

When configured for SYSPLEXMONITOR a system may receive a "EZZ9675E SYSPLEX PROBLEM DETECTION CLEANUP HAS FAILED FOR
TCPIP" message, setting several flags (XFCVT_PDCFAIL_Event/XFPD_Partial_cleanup) which essentially marks TCPIP as a non-member of the TCPplex and requires a restart to recover. This situation may happen on a system which is experiencing high CPU condition or perhaps extremely high paging rates. The TIMERSEC parm offers some control over the interval before EZZ9675E is issued. The problem is that regardless of what this is set to, basically once EZZ9675E comes out it is non-recoverable save for a TCPIP restart. I'd like to see if some manner of recover-ability can be implement for this or similar messages which might set the "partial cleanup" flag.

Specifically, I'm wondering if a "FORCE" parameter can be implemented for the V TCPIP,,SYSPLEX,JOINGROUP/LEAVEGROUP parameters which could possibly clean up the XFCVT_PDCFAIL_Event/XFPD_Partial_cleanup or similar flags. Perhaps this wouldn't be allowed for all flavors of condition flags, but maybe certain ones would be allowed to recover from.

Idea priority High
  • Guest
    Reply
    |
    Jul 22, 2021

    A FORCE command would essentially be a TCP/IP recycle. There is a technote describing why a TCP/IP recycle is needed. https://www.ibm.com/support/pages/why-zos-tcpip-issuing-message-ezz9675e-and-how-should-we-respond-it
    This RFE will be closed.

  • Guest
    Reply
    |
    Nov 19, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - z Systems Software
    Product - z/OS Communications Server

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Enterprise Networking
    Product - z/OS Communications Server