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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
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
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.
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.
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.
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?
I think that is very important to create a new parameter to allow OMPROUTE to send requests to the DNS Server
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%
Hello, It is Resolver that needs this enhancement, not OMPROUTE. oops