pipe @clock and transport and global

I have a named transport, and a pipe referencing said transport. The pipe will not function unless I turn on the global clock even though the transport works without global being on. Am I correct in assuming that this is because pipe creates a 'setclock' when you give a name to the @clock instead of binding it to a transport?

So in the above situation, with global on, and a named transport on, would the named pipe be in time, or would it be set by when you turned on global?