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.

Add a new idea Subscribe
Status Not under consideration
Workspace z/OS
Categories Communications Server
Created by Guest
Created on Oct 22, 2019

RELATED IDEAS

Resolver resilience (routing to the DNS) needs to be improved

I opened a case with IBM where OSNMPD was building .boots files with the Loopback address inside instead of the Stack Static VIPA. It turns out that the Resolver was unable at that point during startup to obtain a route to the DNS and just gave up the ghost. Because of that, OSNMPD was unable to obtain the Stack Static VIPA from the Resolver and thus defaulted to loopback.

There are retry parameters in TCPIP.DATA (ResolverTimeout, ResolverUDPRetries) but they only start working when the Resolver has obtained a route to the DNS.

What I'm suggesting is that there be new parameters available to the Resolver configuration so that it will retry initial attempts to connect to the DNS. That way the resolver will be more resilient of network startup delays.

Jon Bell, of IBM support, was able to give a comprehensive explanation of what was happening so he would be a very good reference.

Idea priority Low
  • Guest
    Reply
    |     Jul 15, 2022
    This item is unlikely to be given high enough priority to be placed into product plan. A recommended workaround would be to use a local hosts file for resolving local host names.

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.