On Monday, 07/13/2015 at 12:38 EDT, Bob Cronin <[email protected]> wrote: > Hello all, > PIPE Hostid | Console has begun reporting 192.168.1.64 (which is clearly > nonsense) for one of our mainframes, but when I resolve its hostname > directly, I get its actual IP address, 9.63.66.64, as expected. Why would > Hostid be returning the wrong answer? I suspect some fat fingered > misconfiguration of something, somewhere, but don't know enough about how > this all works to pinpoint the likely cause (so I can go after support to > get it fixed). Any thoughts?
HOSTID issues the TCP/IP GETHOSTID function which returns the IP address of the "primary interface" of the TCP/IP stack. The primary interface is identified by the PrimaryInterface configuration statement in PROFILE TCPIP. Lacking that, it is the first interface defined in the HOME list. Alan Altmark Senior Managing z/VM and Linux Consultant Lab Services System z Delivery Practice IBM Systems & Technology Group ibm.com/systems/services/labservices office: 607.429.3323 mobile; 607.321.7556 [email protected] IBM Endicott
