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.
We are trying to implement IPNODES in our environment. However, I have DNS entries in / etc / hosts (OMVS) and hosts.local (MVS) that resolve the same name to different IP addresses. I can't say if these name resolution entries are still being used by some addres space. To be able to verify that these name resolution entries are still being used, I need to capture name resolution traffic for a long time. But the volume of name resolutions in the environment is very large, which makes it very difficult to process data without being able to filter by IP addresses.
But with CTRACE TRACERES you can capture a trace of resolver activity for specific address spaces or the entire system. Then using IPCS you can format those traces into an output file and then use FIND commands to search for the host names or IP addresses that are of interest. The trace records that you find will have information that helps identify what applications/address space is performing the resolver request and how that request was satisfied (including what file was used). Or are you concerned about the volume of CTRACE data?
The CTRACE TRACERES option does not solve the issue because it also does not offer the possibility of using a specific IP address as a filter. None of the trace options for RESOLVER offers the option of using an IP address as a filter.
Please let us know if the TRACERES CTRACE option on SYSTCPRE resolves your issue.
Note that you can use the CTRACE SYSTCPRE option to enable a resolver trace in a similar fashion to what is produced when TRACE RESOLVER is enabled in the TCPIP.DATA. The SYSTCPRE Option that you want to use is TRACERES. This provides the same output as TRACE resolver but does this using CTRACE for those environments where it is difficult to enable TRACE RESOLVER in TCPIP.DATA. TRACERES is meant to be used by clients. Note you can also include Jobname and/or ASID filters to only record this activity for specific address spaces. Here's a link to the relevant documentation: https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.hald001/ctraceres.htm#ctraceres