CMSTSO Pipelines Discussion List <[email protected]> wrote on 07/13/2015 01:38:28 PM:
> From: Alan Altmark/Endicott/IBM@IBMUS > To: [email protected] > Date: 07/13/2015 01:38 PM > Subject: Re: Pipe Hostid issue > Sent by: CMSTSO Pipelines Discussion List <[email protected]> > > On Monday, 07/13/2015 at 04:30 EDT, Michael Harding/Oakland/IBM@IBMUS > wrote: > > Interestingly, on one of our internal "jumbo" systems where the host > > returned by IDENTIFY will vary depending on one's cpuid as set up in the > > directory, the output from the socket(getname) call agrees with identify > in > > the caller's machjne, while the pipe hostname stage returns what the > stack > > sees. > > Because both get their information from the TCPIP DATA file. And when > getting data from the TCPIP DATA file, the search is qualified by the NJE > node node, which is determined by cpuid. > > 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 > Except that I would have expected the socket call also to get the stack's view of things or why bother? Which also begs the question of how pipelines does it if not a socket call. -- Mike Harding z/VM System Support /sp
