This is an IBM Automation portal for Cloud Platform products. 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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Please minimize RPC chatter on RPCs number 27 and 28 are HOSTINFO and CLNT_LIST_REGISTER.
Request is to cut down or provide some site configurable options to chatty RPCs. In this case "lsclient" is never used. It seems an excess of RPCs are sent from clients to registry server to gather information that may not be necessary.
There is some very chatty code in RPC calls proc-27 and proc-28. The client calls and requests something, then the rgy server sends back his ?last known uname ?a, and last known license server? Then a couple rpc's later, client sends his current uname ?a and his current license server info.
RPCs number 27 and 28 are HOSTINFO and CLNT_LIST_REGISTER. HOSTINFO is used for some things that the client needs to know (if server is same OS type or different), we may not be able to skip it--but we can analyze to see. CLNT_LIST_REGISTER could certainly use some tuning/frequency adjustments.
Do not place IBM confidential, company confidential, or personal information into any field.