<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Strange behaviour from DCL PIPE in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/strange-behaviour-from-dcl-pipe/m-p/5035029#M35681</link>
    <description>Problem solved.&lt;BR /&gt;Thanks</description>
    <pubDate>Wed, 21 Mar 2007 06:38:24 GMT</pubDate>
    <dc:creator>Jimson_1</dc:creator>
    <dc:date>2007-03-21T06:38:24Z</dc:date>
    <item>
      <title>Strange behaviour from DCL PIPE</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/strange-behaviour-from-dcl-pipe/m-p/5035022#M35674</link>
      <description>Hi, &lt;BR /&gt;&lt;BR /&gt;Can anyone explain the following behaviour to me.&lt;BR /&gt;&lt;BR /&gt;1.  Create the following command procedure:&lt;BR /&gt;&lt;BR /&gt;  $ create a.com&lt;BR /&gt;  $ write sys$output "This works        : _TNA366:"       ! use your terminal process name&lt;BR /&gt;  $ write sys$output "This doesn't work : ''f$getjpi("","TT_PHYDEVNAM")'"&lt;BR /&gt;  &lt;CTRL-Z&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;2.  Execute it:&lt;BR /&gt;&lt;BR /&gt;  $ @a.com&lt;BR /&gt;  This works        : _TNA366:&lt;BR /&gt;  This doesn't work : _TNA366:&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;3.  Now, try the following PIPE command&lt;BR /&gt;&lt;BR /&gt;  $ pipe @a.com | search sys$input TNA366&lt;BR /&gt;  This works        : _TNA366:&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Why couldn't it find the second string?&lt;BR /&gt;&lt;BR /&gt;JamesP&lt;BR /&gt;&lt;BR /&gt;&lt;/CTRL-Z&gt;</description>
      <pubDate>Tue, 20 Mar 2007 09:43:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/strange-behaviour-from-dcl-pipe/m-p/5035022#M35674</guid>
      <dc:creator>Jimson_1</dc:creator>
      <dc:date>2007-03-20T09:43:04Z</dc:date>
    </item>
    <item>
      <title>Re: Strange behaviour from DCL PIPE</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/strange-behaviour-from-dcl-pipe/m-p/5035023#M35675</link>
      <description>pipe show proc | type sys$input&lt;BR /&gt;&lt;BR /&gt;Answer : because the process has no terminal.&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Tue, 20 Mar 2007 10:03:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/strange-behaviour-from-dcl-pipe/m-p/5035023#M35675</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2007-03-20T10:03:58Z</dc:date>
    </item>
    <item>
      <title>Re: Strange behaviour from DCL PIPE</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/strange-behaviour-from-dcl-pipe/m-p/5035024#M35676</link>
      <description>JamesP,&lt;BR /&gt;&lt;BR /&gt;welcome to the OpenVMS ITRC forum.&lt;BR /&gt;&lt;BR /&gt;Pipes are implemented using sub-processes, which may not have an associated terminal. That's why TT_PHYDEVNAM is returned as an empty string.&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Tue, 20 Mar 2007 10:12:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/strange-behaviour-from-dcl-pipe/m-p/5035024#M35676</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2007-03-20T10:12:48Z</dc:date>
    </item>
    <item>
      <title>Re: Strange behaviour from DCL PIPE</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/strange-behaviour-from-dcl-pipe/m-p/5035025#M35677</link>
      <description>The logical tt is however still pointing to your terminal.&lt;BR /&gt;&lt;BR /&gt;pipe write sys$output f$tr("tt") | type sys$input&lt;BR /&gt;FTA14:&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Tue, 20 Mar 2007 10:13:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/strange-behaviour-from-dcl-pipe/m-p/5035025#M35677</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2007-03-20T10:13:53Z</dc:date>
    </item>
    <item>
      <title>Re: Strange behaviour from DCL PIPE</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/strange-behaviour-from-dcl-pipe/m-p/5035026#M35678</link>
      <description>Of course...&lt;BR /&gt;&lt;BR /&gt;Why didn't I think of that?&lt;BR /&gt;&lt;BR /&gt;Cheers guys</description>
      <pubDate>Tue, 20 Mar 2007 10:31:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/strange-behaviour-from-dcl-pipe/m-p/5035026#M35678</guid>
      <dc:creator>Jimson_1</dc:creator>
      <dc:date>2007-03-20T10:31:11Z</dc:date>
    </item>
    <item>
      <title>Re: Strange behaviour from DCL PIPE</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/strange-behaviour-from-dcl-pipe/m-p/5035027#M35679</link>
      <description>James,&lt;BR /&gt;&lt;BR /&gt;first,&lt;BR /&gt;WELCOME to the VMS forum!&lt;BR /&gt;&lt;BR /&gt;please review &lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/helptips.do?#33" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/helptips.do?#33&lt;/A&gt;&lt;BR /&gt;to thank those that helped&lt;BR /&gt;&lt;BR /&gt;Proost.&lt;BR /&gt;&lt;BR /&gt;Have one on me.&lt;BR /&gt;&lt;BR /&gt;jpe</description>
      <pubDate>Wed, 21 Mar 2007 03:46:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/strange-behaviour-from-dcl-pipe/m-p/5035027#M35679</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2007-03-21T03:46:57Z</dc:date>
    </item>
    <item>
      <title>Re: Strange behaviour from DCL PIPE</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/strange-behaviour-from-dcl-pipe/m-p/5035028#M35680</link>
      <description>You may make use of the MASTER_PID functin to obtain information of the master process inside the pipe, e.g.&lt;BR /&gt;&lt;BR /&gt;$ write sys$output "This works : _TNA366:" ! use your terminal process name&lt;BR /&gt;$ pid = F$Getjpi("","MASTER_PID")&lt;BR /&gt;$ write sys$output "This doesn't work : ''f$getjpi(PID,"TT_PHYDEVNAM")'"&lt;BR /&gt;&lt;BR /&gt;regards Kalle</description>
      <pubDate>Wed, 21 Mar 2007 04:40:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/strange-behaviour-from-dcl-pipe/m-p/5035028#M35680</guid>
      <dc:creator>Karl Rohwedder</dc:creator>
      <dc:date>2007-03-21T04:40:08Z</dc:date>
    </item>
    <item>
      <title>Re: Strange behaviour from DCL PIPE</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/strange-behaviour-from-dcl-pipe/m-p/5035029#M35681</link>
      <description>Problem solved.&lt;BR /&gt;Thanks</description>
      <pubDate>Wed, 21 Mar 2007 06:38:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/strange-behaviour-from-dcl-pipe/m-p/5035029#M35681</guid>
      <dc:creator>Jimson_1</dc:creator>
      <dc:date>2007-03-21T06:38:24Z</dc:date>
    </item>
  </channel>
</rss>

