Closed as documentation error.
If the Operating System API (getCanonicalHostname) is not able to retrieve a fully hostname because the local network configuration is not enough, then TPM will try to get this info directly invoking nslookup from the target machine using the current RXA session.
This is working as designed. 1. There is no requirement in TPM to have computer name = Fully Qualified Domain Name (FQDN). 2. Since the DNS server set for the endpoints is not the DNS server set for TPM, TPM cannot see those FQDNs, so it is correct to not store them as computer names in DCM. The TPM Network discovery does not necessarily use the fully qualified hostname because of its network configuration. The value returned will be the output of the hostname command at the target.
This documentation update will be included in the 7.1.1 release
Reported component name
TPM FOR SW
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following: