IBM Z Hardware and Operating Systems Ideas Portal
Hide about this 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 Delivered
Workspace z/OS
Categories Communications Server
Created by Guest
Created on May 12, 2013

RELATED IDEAS

Create a new parameter to allow OMPROUTE to send requests to the DNS Server a specified number of times. related to EZZ3908E.

We are receiving numerous EZZ3908E errors where the DNS Server is not responding before the timeout occurs.

I would like to address 2 things.

First is that these occur during off hours and there may only be one request. It fail so there is a 100% failure rate. No matter what percentage I code it is going to fail.

Second is that the next 5 minute interval recovers as the failure percentage is 0%. There are also 0 searches. So what does that tell us about being able to reach the DNS Server.?

I propose setting up a parameter that would cause OMPROUTE to do its own searching / polling of he DNS Server all the time. If the value was set to 10, then it would do 10 searches every 5min interval. This would at lease give a more accurate picture of if the DNS Server is reachable or not. It would also give a better idea of when it became unavailabe and for how long. As it is now, it could have been down for hours before and after the EZZ3908E gets displayed. If there is only a single request that failed and nothing before or after that for hours.

Idea priority Low
  • 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

  • Guest
    Reply
    |     Sep 19, 2013

    This function is available via the AUTOQUIESCE parameter in the Resolver configuration that was introduced in z/OS V1R13.  The AUTOQUIESCE parameter will trigger the resolver to also perform its own queries to the DNS to ensure that more samples of the DNS health are available before making a decision on the DNS server being unresponsive or responsive once again.  The AUTOQUIESCE function also minimizes manual operations that would be otherwise required if a DNS server is unresponsive, as the next available DNS in the TCPIP.DATA file can be used for queries.

  • Guest
    Reply
    |     Sep 19, 2013

    This function is available via the AUTOQUIESCE parameter in the Resolver configuration that was introduced in z/OS V1R13.  The AUTOQUIESCE parameter will trigger the resolver to also perform its own queries to the DNS to ensure that more samples of the DNS health are available before making a decision on the DNS server being unresponsive or responsive once again.  The AUTOQUIESCE function also minimizes manual operations that would be otherwise required if a DNS server is unresponsive, as the next available DNS in the TCPIP.DATA file can be used for queries.

  • Guest
    Reply
    |     Aug 9, 2013

    We have not implemented this parameter yet. The environment where this was occuring has been in a change freeze because the data center was moving to another location. The migration is complete now so we will review and decide if we will implement.

  • Guest
    Reply
    |     Jun 17, 2013

    Specifying the AUTOQUIESCE parameter in the Resolver configuration should alleviate the concern mentioned in this RFE. The AUTOQUIESCE parameter will trigger the resolver to also perform its own queries to the DNS to ensure that more samples of the DNS health are available before making a decision on the DNS server being unresponsive or responsive once again. The AUTOQUIESCE function also minimizes manual operations that would be otherwise required if a DNS server is unresponsive, as the next available DNS in the TCPIP.DATA file can be used for queries. Have you tried this function? If not, can you try it and see if it alleviates the issue?

  • Guest
    Reply
    |     May 17, 2013

    I think that is very important to create a new parameter to allow OMPROUTE to send requests to the DNS Server

  • Guest
    Reply
    |     May 15, 2013

    Here are a few of the messages we saw.
    SYSB 13101 21:37:22.98 00000010 *EZZ9308E UNRESPONSIVE
    NAME SERVER DETECTED AT IP ADDRESS 159.202.50.190
    SYSB 13101 21:37:23.01 00000000 EZZ9310I NAME SERVER
    159.202.50.190 004
    004 00000000 TOTAL NUMBER OF
    QUERIES SENT 2
    004 00000000 TOTAL NUMBER OF
    FAILURES 1
    004 00000000
    PERCENTAGE 50%

    SYSB 13101 21:37:23.01 00000010 *EZZ9308E UNRESPONSIVE
    NAME SERVER DETECTED AT IP ADDRESS 159.202.20.190
    SYSB 13101 21:37:23.02 00000000 EZZ9310I NAME SERVER
    159.202.20.190 006
    006 00000000 TOTAL NUMBER OF
    QUERIES SENT 1
    006 00000000 TOTAL NUMBER OF
    FAILURES 1
    006 00000000
    PERCENTAGE 100%

    SYSB 13101 21:42:23.02 00000000 EZZ9309I NAME SERVER IS
    NOW RESPONSIVE AT IP ADDRESS 159.202.50.190
    SYSB 13101 21:42:23.03 00000000 EZZ9310I NAME SERVER
    159.202.50.190 264
    264 00000000 TOTAL NUMBER OF
    QUERIES SENT 0
    264 00000000 TOTAL NUMBER OF
    FAILURES 0
    264 00000000
    PERCENTAGE 0%

    SYSB 13101 21:42:23.05 00000000 EZZ9309I NAME SERVER IS
    NOW RESPONSIVE AT IP ADDRESS 159.202.20.190
    SYSB 13101 21:42:23.05 00000000 EZZ9310I NAME SERVER
    159.202.20.190 266
    266 00000000 TOTAL NUMBER OF
    QUERIES SENT 0
    266 00000000 TOTAL NUMBER OF
    FAILURES 0
    266 00000000
    PERCENTAGE 0%

  • Guest
    Reply
    |     May 15, 2013

    Hello, It is Resolver that needs this enhancement, not OMPROUTE. oops

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.