<?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: lexical function to provide fully qualified domain name ? in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/lexical-function-to-provide-fully-qualified-domain-name/m-p/3440885#M48338</link>
    <description>I agree that adding this functionality will&lt;BR /&gt;be useful. I have filed an internal problem&lt;BR /&gt;report to track this request. I hope to be&lt;BR /&gt;able to implement it for the next version&lt;BR /&gt;(Post V8.2)&lt;BR /&gt;&lt;BR /&gt;Guy</description>
    <pubDate>Tue, 14 Dec 2004 08:11:18 GMT</pubDate>
    <dc:creator>Guy Peleg</dc:creator>
    <dc:date>2004-12-14T08:11:18Z</dc:date>
    <item>
      <title>lexical function to provide fully qualified domain name ?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/lexical-function-to-provide-fully-qualified-domain-name/m-p/3440873#M48326</link>
      <description>I haven't got the latest OpenVMS Version to check, but is there anything planned as far as providing an additional arguement to provide the TCPIP_FULLNAME similar to the existing arguement  DECNET_FULLNAME for the F$GETSYI lexical function?</description>
      <pubDate>Fri, 10 Dec 2004 09:18:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/lexical-function-to-provide-fully-qualified-domain-name/m-p/3440873#M48326</guid>
      <dc:creator>john Dite</dc:creator>
      <dc:date>2004-12-10T09:18:27Z</dc:date>
    </item>
    <item>
      <title>Re: lexical function to provide fully qualified domain name ?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/lexical-function-to-provide-fully-qualified-domain-name/m-p/3440874#M48327</link>
      <description>John,&lt;BR /&gt;&lt;BR /&gt;I can't see anything like this in E8.2&lt;BR /&gt;&lt;BR /&gt;How about using &lt;BR /&gt;&lt;BR /&gt;$ x=f$trnlnm("TCPIP$INET_HOST")+"."+f$trnlnm("TCPIP$INET_DOMAIN")&lt;BR /&gt;$ sho sym x&lt;BR /&gt;  X = "axpvms.invenate.local"&lt;BR /&gt;&lt;BR /&gt;Volker</description>
      <pubDate>Fri, 10 Dec 2004 09:30:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/lexical-function-to-provide-fully-qualified-domain-name/m-p/3440874#M48327</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2004-12-10T09:30:24Z</dc:date>
    </item>
    <item>
      <title>Re: lexical function to provide fully qualified domain name ?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/lexical-function-to-provide-fully-qualified-domain-name/m-p/3440875#M48328</link>
      <description>&lt;BR /&gt;John,&lt;BR /&gt;&lt;BR /&gt;Just looked at my notes of the TUD. Nothing Guy Peleg said points in that direction.&lt;BR /&gt;But couldn't you just translate the logical names TCPIP$INET_HOST and TCPIP$INET_DOMAIN and glue them together?&lt;BR /&gt;&lt;BR /&gt;Greetz,&lt;BR /&gt;&lt;BR /&gt;Kris (aka Qkcl)&lt;BR /&gt;</description>
      <pubDate>Fri, 10 Dec 2004 09:41:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/lexical-function-to-provide-fully-qualified-domain-name/m-p/3440875#M48328</guid>
      <dc:creator>Kris Clippeleyr</dc:creator>
      <dc:date>2004-12-10T09:41:54Z</dc:date>
    </item>
    <item>
      <title>Re: lexical function to provide fully qualified domain name ?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/lexical-function-to-provide-fully-qualified-domain-name/m-p/3440876#M48329</link>
      <description>Hi Volker,&lt;BR /&gt;&lt;BR /&gt;Speedy is your second name! ;-)&lt;BR /&gt; &lt;BR /&gt;Thanks for the reminder. But it would still be nice to have equivalent Lexical functions that give you the info that gethostbyname and gethostbyaddr do in the context of a program.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 10 Dec 2004 09:42:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/lexical-function-to-provide-fully-qualified-domain-name/m-p/3440876#M48329</guid>
      <dc:creator>john Dite</dc:creator>
      <dc:date>2004-12-10T09:42:53Z</dc:date>
    </item>
    <item>
      <title>Re: lexical function to provide fully qualified domain name ?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/lexical-function-to-provide-fully-qualified-domain-name/m-p/3440877#M48330</link>
      <description>Yes, why did nobody bring this up earlier?&lt;BR /&gt;&lt;BR /&gt;and the previous entries add up nicely to a friendly request to Guy!&lt;BR /&gt;&lt;BR /&gt;John, your original question was for F$GETSYI to have TCPIP_FULLNAME, as an argument.&lt;BR /&gt;On your later entry you name "gethostbyname" and "gethostbyaddr" as the standard functions in higher languages.&lt;BR /&gt;I suppose the latter two have some more value than the first, but maybe if one is done, it is not very much more complex to do all?&lt;BR /&gt;.. and I would suggest an extension: if a node has multiple addresses (and probably associated names) would it then be possible to set up a context to scan over all values?&lt;BR /&gt;(say, in the spirit of F$SEARCH).&lt;BR /&gt;&lt;BR /&gt;Maybe you can leave this thread collect other ideas for about a week, and then mail the URL to Guy?&lt;BR /&gt;&lt;BR /&gt;Proost.&lt;BR /&gt;&lt;BR /&gt;Have one on me.&lt;BR /&gt;&lt;BR /&gt;Jan</description>
      <pubDate>Fri, 10 Dec 2004 10:08:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/lexical-function-to-provide-fully-qualified-domain-name/m-p/3440877#M48330</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2004-12-10T10:08:28Z</dc:date>
    </item>
    <item>
      <title>Re: lexical function to provide fully qualified domain name ?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/lexical-function-to-provide-fully-qualified-domain-name/m-p/3440878#M48331</link>
      <description>Please remember that a TCP/IP host can have multiple IP adresses and multiple names. There is no easy 1:1 mapping as in DECnet.</description>
      <pubDate>Fri, 10 Dec 2004 10:25:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/lexical-function-to-provide-fully-qualified-domain-name/m-p/3440878#M48331</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2004-12-10T10:25:28Z</dc:date>
    </item>
    <item>
      <title>Re: lexical function to provide fully qualified domain name ?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/lexical-function-to-provide-fully-qualified-domain-name/m-p/3440879#M48332</link>
      <description>Uwe,&lt;BR /&gt;&lt;BR /&gt;yes, and that is why I was suggesting the context-construct!&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>Fri, 10 Dec 2004 13:32:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/lexical-function-to-provide-fully-qualified-domain-name/m-p/3440879#M48332</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2004-12-10T13:32:04Z</dc:date>
    </item>
    <item>
      <title>Re: lexical function to provide fully qualified domain name ?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/lexical-function-to-provide-fully-qualified-domain-name/m-p/3440880#M48333</link>
      <description>My appologies Jan - I have missed it.&lt;BR /&gt;&lt;BR /&gt;But what sources would you include?&lt;BR /&gt;- local hosts database&lt;BR /&gt;- DNS server&lt;BR /&gt;-- how do you deal with round-robin and load balancers?</description>
      <pubDate>Sun, 12 Dec 2004 14:57:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/lexical-function-to-provide-fully-qualified-domain-name/m-p/3440880#M48333</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2004-12-12T14:57:03Z</dc:date>
    </item>
    <item>
      <title>Re: lexical function to provide fully qualified domain name ?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/lexical-function-to-provide-fully-qualified-domain-name/m-p/3440881#M48334</link>
      <description>Uwe,&lt;BR /&gt;&lt;BR /&gt;(just thinking with my keyboard now)&lt;BR /&gt;&lt;BR /&gt;- I guess the context construct by default would scan through ALL.&lt;BR /&gt;&lt;BR /&gt;- by analogy with f$getjpi and f$getqui, the context range could be modified by f$context.&lt;BR /&gt;&lt;BR /&gt;- maybe, as an analogy to f$getjpi(x,"rightslist"), it should also be possible to have ALL values at once in a string (to be able to check any presence). With the new string length limitations that will probably more feasable than at the old limit.&lt;BR /&gt;&lt;BR /&gt;- or, enabling reverse lookup, return False or True for a name-address combination.&lt;BR /&gt;&lt;BR /&gt;----  of course, I would gladly retract these for any better ideas!!&lt;BR /&gt;&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>Mon, 13 Dec 2004 05:17:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/lexical-function-to-provide-fully-qualified-domain-name/m-p/3440881#M48334</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2004-12-13T05:17:23Z</dc:date>
    </item>
    <item>
      <title>Re: lexical function to provide fully qualified domain name ?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/lexical-function-to-provide-fully-qualified-domain-name/m-p/3440882#M48335</link>
      <description>I'm with Jan;&lt;BR /&gt;a lexical function with context like f$getqui may be usefull.&lt;BR /&gt; &lt;BR /&gt;Antonio Vigliotti&lt;BR /&gt;</description>
      <pubDate>Tue, 14 Dec 2004 02:29:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/lexical-function-to-provide-fully-qualified-domain-name/m-p/3440882#M48335</guid>
      <dc:creator>Antoniov.</dc:creator>
      <dc:date>2004-12-14T02:29:52Z</dc:date>
    </item>
    <item>
      <title>Re: lexical function to provide fully qualified domain name ?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/lexical-function-to-provide-fully-qualified-domain-name/m-p/3440883#M48336</link>
      <description>agreed have this system info suggestion, but there is a drawback. What about the fact a system can have multiple NICs - each configured with it's own IP address and, potentially, it's own name? Even on one address there can be multiple names - and making matters even more complicated, if you're hosting different websites (apache's 'virtual hosts') you may have multiple names on ONE address ("CNAME" in DNS but this is no obligation!)&lt;BR /&gt;You may have to end up with running down a list, like F$PID or F$SEARCH.&lt;BR /&gt;</description>
      <pubDate>Tue, 14 Dec 2004 03:12:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/lexical-function-to-provide-fully-qualified-domain-name/m-p/3440883#M48336</guid>
      <dc:creator>Willem Grooters</dc:creator>
      <dc:date>2004-12-14T03:12:20Z</dc:date>
    </item>
    <item>
      <title>Re: lexical function to provide fully qualified domain name ?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/lexical-function-to-provide-fully-qualified-domain-name/m-p/3440884#M48337</link>
      <description>C'mon Willem,&lt;BR /&gt;&lt;BR /&gt;read the whole thread!&lt;BR /&gt;&lt;BR /&gt;That is exactly what most of the discussion was about!&lt;BR /&gt;&lt;BR /&gt;Proost.&lt;BR /&gt;&lt;BR /&gt;Have one on me.&lt;BR /&gt;&lt;BR /&gt;Jan</description>
      <pubDate>Tue, 14 Dec 2004 04:02:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/lexical-function-to-provide-fully-qualified-domain-name/m-p/3440884#M48337</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2004-12-14T04:02:32Z</dc:date>
    </item>
    <item>
      <title>Re: lexical function to provide fully qualified domain name ?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/lexical-function-to-provide-fully-qualified-domain-name/m-p/3440885#M48338</link>
      <description>I agree that adding this functionality will&lt;BR /&gt;be useful. I have filed an internal problem&lt;BR /&gt;report to track this request. I hope to be&lt;BR /&gt;able to implement it for the next version&lt;BR /&gt;(Post V8.2)&lt;BR /&gt;&lt;BR /&gt;Guy</description>
      <pubDate>Tue, 14 Dec 2004 08:11:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/lexical-function-to-provide-fully-qualified-domain-name/m-p/3440885#M48338</guid>
      <dc:creator>Guy Peleg</dc:creator>
      <dc:date>2004-12-14T08:11:18Z</dc:date>
    </item>
    <item>
      <title>Re: lexical function to provide fully qualified domain name ?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/lexical-function-to-provide-fully-qualified-domain-name/m-p/3440886#M48339</link>
      <description>Great Guy!</description>
      <pubDate>Tue, 14 Dec 2004 08:16:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/lexical-function-to-provide-fully-qualified-domain-name/m-p/3440886#M48339</guid>
      <dc:creator>john Dite</dc:creator>
      <dc:date>2004-12-14T08:16:50Z</dc:date>
    </item>
  </channel>
</rss>

