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 20, 2021

TCPIP Sysplex Autonomics with CSM constrain

VTAM CSM FIXED Storage arise 80% CONSTRAIN situation due to a high demand of TCP workload with 4 OSA 10 Gb interfaces.
But returns to a level under 80% immediately. This situation repeats more than 1000 times in 2 hours.
TCPIP Sysplex Autonomics doesn't detect the situation, and finally OSAs interfaces hangs several times.

We think than Sysplex Automics should act in this case and force the affected TCPIP stack from Sysplex functions.

Idea priority Medium
  • Guest
    Reply
    |
    May 29, 2023

    Really more than 2 years for this answer?


  • Guest
    Reply
    |
    May 29, 2023
    The reason that Sysplex Autonomics did not react to the fact that CSM fixed storage exceeded the 80% threshold is because Sysplex Autonomics will only react if a condition persists for the entire timer interval that is specified on the GLOBALCONFIG SYSPLEXMONITOR statement (defaults to 60 seconds). In your scenario, the system kept going below and above the 80% threshold very frequently, so Sysplex Autonomics could never wait long enough to determine if a persistent condition existed. The correct solution in this case is to increase the amount of fixed storage that can be configured to CSM, via the IVTCSM00 parmlib member, to prevent this back and forth over the 80% threshold.