<?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: F$DEVICE lexical in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/f-device-lexical/m-p/3434328#M31655</link>
    <description>Uwe, &lt;BR /&gt;&lt;BR /&gt;I don't remember the introduction of /TERMINAL, but I _DO_ know it became much less relevant, to the extend that I consider it obsolete, at V5.1 (maybe 5.0, never had that on my hands, nor 6.0 nor 7.0, for that matter)&lt;BR /&gt;Under V4.x (and I -think- V3, but unsure)&lt;BR /&gt;Concealed Logical Names had to be /TERMINAL, and so they had to reference the physical device directly.&lt;BR /&gt;But since V5, if you simply omit /terminal, everything works fine, and you can point a concealed device to a directory structure on the concealed logical name for a disk, that does not need to be terminal, and may even translate to another conc. lnm for the disk.&lt;BR /&gt;&lt;BR /&gt;Makes things more simple, which (to me) is always welcome.&lt;BR /&gt;&lt;BR /&gt;hth&lt;BR /&gt;&lt;BR /&gt;Cheers.&lt;BR /&gt;&lt;BR /&gt;Have one on me.&lt;BR /&gt;&lt;BR /&gt;Jan</description>
    <pubDate>Fri, 03 Dec 2004 11:01:39 GMT</pubDate>
    <dc:creator>Jan van den Ende</dc:creator>
    <dc:date>2004-12-03T11:01:39Z</dc:date>
    <item>
      <title>F$DEVICE lexical</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/f-device-lexical/m-p/3434311#M31638</link>
      <description>If one reads:&lt;BR /&gt;&lt;BR /&gt;Lexicals&lt;BR /&gt;  F$DEVICE&lt;BR /&gt;    Arguments&lt;BR /&gt;      search_devnam&lt;BR /&gt;&lt;BR /&gt;         Specifies the name of the device for which F$DEVICE is to search. The asterisk (*)  and the percent sign (%) wildcard characters are allowed in the search_devnam argument.&lt;BR /&gt;&lt;BR /&gt;         Specify the search_devnam argument as a character string expression.&lt;BR /&gt;&lt;BR /&gt;Why would you not be able to use:&lt;BR /&gt;&lt;BR /&gt;$ disk = f$getdvi("$1$DK*","DISK")&lt;BR /&gt;&lt;BR /&gt;It works if you specify f$getdvi("*","DISK"), but I only want info on the scsi disks with allocation class $1$.&lt;BR /&gt;&lt;BR /&gt;* isn't _really_ a wildcard?&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;Art</description>
      <pubDate>Wed, 01 Dec 2004 14:21:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/f-device-lexical/m-p/3434311#M31638</guid>
      <dc:creator>Art Wiens</dc:creator>
      <dc:date>2004-12-01T14:21:06Z</dc:date>
    </item>
    <item>
      <title>Re: F$DEVICE lexical</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/f-device-lexical/m-p/3434312#M31639</link>
      <description>I'm having a bad day here...one more time.&lt;BR /&gt;&lt;BR /&gt;The f$device lexical help reads that you can use an * wildcard...I made a slip in my post (f$getdvi), but in my command procedure I _am_ using f$device and it doesn't work.&lt;BR /&gt;&lt;BR /&gt;Maybe one too many "Cheers" ;-)&lt;BR /&gt;Art</description>
      <pubDate>Wed, 01 Dec 2004 14:22:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/f-device-lexical/m-p/3434312#M31639</guid>
      <dc:creator>Art Wiens</dc:creator>
      <dc:date>2004-12-01T14:22:30Z</dc:date>
    </item>
    <item>
      <title>Re: F$DEVICE lexical</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/f-device-lexical/m-p/3434313#M31640</link>
      <description>Art,&lt;BR /&gt;1. You need to specify device type which is usually "GENERIC_DK".&lt;BR /&gt;2. Unfortunately the "*" has to be a prefix.&lt;BR /&gt;CNSRV1Â» device_name = f$device("*0:","DISK","GENERIC_DK")&lt;BR /&gt;CNSRV1Â» SH SYM DEVICE_NAME&lt;BR /&gt;  DEVICE_NAME = "_$1$DKA400:"&lt;BR /&gt;CNSRV1Â» device_name = f$device&lt;BR /&gt;("*0:","DISK","GENERIC_DK")&lt;BR /&gt;CNSRV1Â» SH SYM DEVICE_NAME&lt;BR /&gt;  DEVICE_NAME = "_$1$DKB100:"&lt;BR /&gt;CNSRV1Â» device_name = f$device("*00:","DISK","GENERIC_DK")&lt;BR /&gt;CNSRV1Â» SH SYM DEVICE_NAME&lt;BR /&gt;  DEVICE_NAME = "_$1$DKA400:"&lt;BR /&gt;CNSRV1Â» device_name = f$device("*:","DISK","GENERIC_DK")&lt;BR /&gt;CNSRV1Â» SH SYM DEVICE_NAME&lt;BR /&gt;  DEVICE_NAME = "_$1$DKA400:"&lt;BR /&gt;CNSRV1Â» device_name = f$device("*100:","DISK","GENERIC_DK")&lt;BR /&gt;CNSRV1Â» SH SYM DEVICE_NAME&lt;BR /&gt;  DEVICE_NAME = "_</description>
      <pubDate>Wed, 01 Dec 2004 18:56:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/f-device-lexical/m-p/3434313#M31640</guid>
      <dc:creator>Lawrence Czlapinski</dc:creator>
      <dc:date>2004-12-01T18:56:28Z</dc:date>
    </item>
    <item>
      <title>Re: F$DEVICE lexical</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/f-device-lexical/m-p/3434314#M31641</link>
      <description>Art,&lt;BR /&gt;&lt;BR /&gt;The following works for me...&lt;BR /&gt;&lt;BR /&gt;$ say f$device("$255$DK*:","DISK")&lt;BR /&gt;! nothing found on this one&lt;BR /&gt;&lt;BR /&gt;$ say f$device("*DK*:","DISK")&lt;BR /&gt;_$255$DKB0:&lt;BR /&gt;&lt;BR /&gt;$ say f$device("_$255$DK*:","DISK")&lt;BR /&gt;_$255$DKB0:&lt;BR /&gt;&lt;BR /&gt;Not quite sure how the matching is done, I will&lt;BR /&gt;have a look at the source listings.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Dave&lt;BR /&gt;</description>
      <pubDate>Wed, 01 Dec 2004 19:52:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/f-device-lexical/m-p/3434314#M31641</guid>
      <dc:creator>David B Sneddon</dc:creator>
      <dc:date>2004-12-01T19:52:51Z</dc:date>
    </item>
    <item>
      <title>Re: F$DEVICE lexical</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/f-device-lexical/m-p/3434315#M31642</link>
      <description>I also found that DISK is not a correct device class (&lt;A href="http://www.sysworks.com.au/disk$vaxdocmar963/decw$book/dy4yaaa6.p130.decw$book#2390)." target="_blank"&gt;http://www.sysworks.com.au/disk$vaxdocmar963/decw$book/dy4yaaa6.p130.decw$book#2390).&lt;/A&gt;&lt;BR /&gt;It should be DC$_DISK.&lt;BR /&gt;&lt;BR /&gt;And the device type should be one of the list &lt;A href="http://www.sysworks.com.au/disk$vaxdocmar963/decw$book/dy4yaaa6.p131.decw$book#2392" target="_blank"&gt;http://www.sysworks.com.au/disk$vaxdocmar963/decw$book/dy4yaaa6.p131.decw$book#2392&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Confusing.&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Thu, 02 Dec 2004 05:18:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/f-device-lexical/m-p/3434315#M31642</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2004-12-02T05:18:24Z</dc:date>
    </item>
    <item>
      <title>Re: F$DEVICE lexical</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/f-device-lexical/m-p/3434316#M31643</link>
      <description>F$DEVICE("*$1$DK*","DISK") works perfectly on our system.</description>
      <pubDate>Thu, 02 Dec 2004 06:47:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/f-device-lexical/m-p/3434316#M31643</guid>
      <dc:creator>Karl Rohwedder</dc:creator>
      <dc:date>2004-12-02T06:47:24Z</dc:date>
    </item>
    <item>
      <title>Re: F$DEVICE lexical</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/f-device-lexical/m-p/3434317#M31644</link>
      <description>Karl,&lt;BR /&gt;&lt;BR /&gt;I agree because I use disk too. But it's not the option that is documented.&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Thu, 02 Dec 2004 06:48:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/f-device-lexical/m-p/3434317#M31644</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2004-12-02T06:48:55Z</dc:date>
    </item>
    <item>
      <title>Re: F$DEVICE lexical</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/f-device-lexical/m-p/3434318#M31645</link>
      <description>From Karl's example and mine above it would&lt;BR /&gt;appear to have something to do with the leading&lt;BR /&gt;underscore character.  "_$1$DK*" works and&lt;BR /&gt;"*$1$DK*" works but "$1$DK*" doesn't.&lt;BR /&gt;Haven't had a chance to check the source listings&lt;BR /&gt;yet.&lt;BR /&gt;&lt;BR /&gt;Dave&lt;BR /&gt;</description>
      <pubDate>Thu, 02 Dec 2004 06:54:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/f-device-lexical/m-p/3434318#M31645</guid>
      <dc:creator>David B Sneddon</dc:creator>
      <dc:date>2004-12-02T06:54:36Z</dc:date>
    </item>
    <item>
      <title>Re: F$DEVICE lexical</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/f-device-lexical/m-p/3434319#M31646</link>
      <description>Working on a not-clustered VMS7.3-1 system, I found that this works:&lt;BR /&gt;&lt;BR /&gt;f=f$device("*&lt;NODENAME&gt;$DK*", "DISK")&lt;BR /&gt;&lt;BR /&gt;Each call will yield the next device (in arbitrary order as the HELP tells me).&lt;BR /&gt;&lt;BR /&gt;So if you just want the $1$-devices, put a * in front and after:&lt;BR /&gt;&lt;BR /&gt;f=f$device("*$1$DK*", "DISK")&lt;BR /&gt;&lt;BR /&gt;may give the required result.&lt;BR /&gt;&lt;BR /&gt;But it isn't very logically you seem to need the both....&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;&lt;BR /&gt;Willem&lt;BR /&gt;&lt;BR /&gt;&lt;/NODENAME&gt;</description>
      <pubDate>Thu, 02 Dec 2004 09:08:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/f-device-lexical/m-p/3434319#M31646</guid>
      <dc:creator>Willem Grooters</dc:creator>
      <dc:date>2004-12-02T09:08:42Z</dc:date>
    </item>
    <item>
      <title>Re: F$DEVICE lexical</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/f-device-lexical/m-p/3434320#M31647</link>
      <description>It appears that it is doing the comparison to the physical device name which always contains a leading underscore.  If you include the underscore or wildcard it, it will match.  If you notice all of the values returned, if a match is found, contain the leading the underscore, so I think this is what it is matching the wildcarded value against.</description>
      <pubDate>Thu, 02 Dec 2004 13:55:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/f-device-lexical/m-p/3434320#M31647</guid>
      <dc:creator>Dale A. Marcy</dc:creator>
      <dc:date>2004-12-02T13:55:19Z</dc:date>
    </item>
    <item>
      <title>Re: F$DEVICE lexical</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/f-device-lexical/m-p/3434321#M31648</link>
      <description>Wim, DC$_ is the prefix for device class. The device class names are the part after the DC$.&lt;BR /&gt;Art,&lt;BR /&gt;ASDEV1Â» device_name=f$device("*$4$*:","DISK")&lt;BR /&gt;ASDEV1Â» sh sym device_name&lt;BR /&gt;&lt;BR /&gt;In a DCL procedure you can do something like:&lt;BR /&gt;$  class = 1&lt;BR /&gt;$ START:&lt;BR /&gt;$  DEVICE_NAME = -&lt;BR /&gt;F$DEVICE("*$''class'$:","DISK","RA60")&lt;BR /&gt;$  IF DEVICE_NAME .EQS. "" THEN EXIT&lt;BR /&gt;$  SHOW SYMBOL DEVICE_NAME&lt;BR /&gt;$  GOTO START&lt;BR /&gt;&lt;BR /&gt;Lawr</description>
      <pubDate>Thu, 02 Dec 2004 14:07:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/f-device-lexical/m-p/3434321#M31648</guid>
      <dc:creator>Lawrence Czlapinski</dc:creator>
      <dc:date>2004-12-02T14:07:51Z</dc:date>
    </item>
    <item>
      <title>Re: F$DEVICE lexical</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/f-device-lexical/m-p/3434322#M31649</link>
      <description>I would say the doc need a review.&lt;BR /&gt;&lt;BR /&gt;In 7.3 : f$dev points to doc of f$getdvi. There it points to examples that don't exist. So no list of allowed values.&lt;BR /&gt;&lt;BR /&gt;If DC$ is a prefix, it should be documented.&lt;BR /&gt;If _ is required, idem.&lt;BR /&gt;&lt;BR /&gt;Since the beginning (87) I have the impression that each VMS OS programmer was free to implement devices his own way (: or not, _, prefixes etc).&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Thu, 02 Dec 2004 14:32:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/f-device-lexical/m-p/3434322#M31649</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2004-12-02T14:32:46Z</dc:date>
    </item>
    <item>
      <title>Re: F$DEVICE lexical</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/f-device-lexical/m-p/3434323#M31650</link>
      <description>&lt;BR /&gt;Seems to me that&lt;BR /&gt;f$device("*$1$dk*:","DISK")&lt;BR /&gt;should work fine.</description>
      <pubDate>Thu, 02 Dec 2004 15:56:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/f-device-lexical/m-p/3434323#M31650</guid>
      <dc:creator>John Yu_1</dc:creator>
      <dc:date>2004-12-02T15:56:37Z</dc:date>
    </item>
    <item>
      <title>Re: F$DEVICE lexical</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/f-device-lexical/m-p/3434324#M31651</link>
      <description>The search name is used with STR$MATCH_WILD.&lt;BR /&gt;&lt;BR /&gt;If any help needs to be improved it is HELP RTL STR$ STR$MATCH because it does not even mention the % and * characters.&lt;BR /&gt;&lt;BR /&gt;Device names do contain a leading underscore which stops logical name translation. That's just how it is. Documented and readily visible with the "*" example&lt;BR /&gt;&lt;BR /&gt;It would seem clear to me that "_xxx" does not match "xxx" but "_xxx", "*xxx" and "%xxx" do match that.&lt;BR /&gt;&lt;BR /&gt;fwiw,&lt;BR /&gt;Hein.&lt;BR /&gt;</description>
      <pubDate>Thu, 02 Dec 2004 18:02:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/f-device-lexical/m-p/3434324#M31651</guid>
      <dc:creator>Hein van den Heuvel</dc:creator>
      <dc:date>2004-12-02T18:02:25Z</dc:date>
    </item>
    <item>
      <title>Re: F$DEVICE lexical</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/f-device-lexical/m-p/3434325#M31652</link>
      <description>Ten points for everyone because it's Christmas! ;-).&lt;BR /&gt;&lt;BR /&gt;Thanks all, I understand now.&lt;BR /&gt;&lt;BR /&gt;Sorry for the delay on points assignment, it's been a "scary" time...a remote VAX (production critical!) working away for the past 10 years had a system disk failure.  No problem ... we'll just get another disk and restore the most recent backup tape.  What's that, you stopped doing backups "a long time ago"?!?!?!?!? :-O&lt;BR /&gt;&lt;BR /&gt;I sent them two disks with v6.2 on them, they mixed up which were mine, which was their old disk! :-O&lt;BR /&gt;&lt;BR /&gt;They've managed to find some 8mm's from "a long time ago".  I'm giving them DCL backup commands over the phone, they're making typo's and typing in things I didn't tell them to!&lt;BR /&gt;&lt;BR /&gt;First tape gave parity errors right off the bat.  Second one's running right now. Hard to say how it will end...&lt;BR /&gt;&lt;BR /&gt;No cheers right now, but thanks,&lt;BR /&gt;Art</description>
      <pubDate>Thu, 02 Dec 2004 19:26:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/f-device-lexical/m-p/3434325#M31652</guid>
      <dc:creator>Art Wiens</dc:creator>
      <dc:date>2004-12-02T19:26:41Z</dc:date>
    </item>
    <item>
      <title>Re: F$DEVICE lexical</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/f-device-lexical/m-p/3434326#M31653</link>
      <description>Art,&lt;BR /&gt;&lt;BR /&gt;let me wish you strength!&lt;BR /&gt;&lt;BR /&gt;And then, if you have wrestled though this, then rhere will be some teaching, I hope?&lt;BR /&gt;And some VERY plain, VERY stupid, VERY short, but VERY consise instructions!&lt;BR /&gt;&lt;BR /&gt;and remember: "may you live in interesting times" is more a curse than a good wish.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Cheers.&lt;BR /&gt;&lt;BR /&gt;Have one on me (and if you get things going again, that IS a deserved one)&lt;BR /&gt;&lt;BR /&gt;Jan&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 03 Dec 2004 05:47:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/f-device-lexical/m-p/3434326#M31653</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2004-12-03T05:47:14Z</dc:date>
    </item>
    <item>
      <title>Re: F$DEVICE lexical</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/f-device-lexical/m-p/3434327#M31654</link>
      <description>Prefixing a device name with '_' to stop any further translation is very old and even predates the TERMINAL logical name attribute, which, if I recall correctly, was introduced with VAX/VMS V4.0 when the logical name system was overhauled.</description>
      <pubDate>Fri, 03 Dec 2004 07:12:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/f-device-lexical/m-p/3434327#M31654</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2004-12-03T07:12:41Z</dc:date>
    </item>
    <item>
      <title>Re: F$DEVICE lexical</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/f-device-lexical/m-p/3434328#M31655</link>
      <description>Uwe, &lt;BR /&gt;&lt;BR /&gt;I don't remember the introduction of /TERMINAL, but I _DO_ know it became much less relevant, to the extend that I consider it obsolete, at V5.1 (maybe 5.0, never had that on my hands, nor 6.0 nor 7.0, for that matter)&lt;BR /&gt;Under V4.x (and I -think- V3, but unsure)&lt;BR /&gt;Concealed Logical Names had to be /TERMINAL, and so they had to reference the physical device directly.&lt;BR /&gt;But since V5, if you simply omit /terminal, everything works fine, and you can point a concealed device to a directory structure on the concealed logical name for a disk, that does not need to be terminal, and may even translate to another conc. lnm for the disk.&lt;BR /&gt;&lt;BR /&gt;Makes things more simple, which (to me) is always welcome.&lt;BR /&gt;&lt;BR /&gt;hth&lt;BR /&gt;&lt;BR /&gt;Cheers.&lt;BR /&gt;&lt;BR /&gt;Have one on me.&lt;BR /&gt;&lt;BR /&gt;Jan</description>
      <pubDate>Fri, 03 Dec 2004 11:01:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/f-device-lexical/m-p/3434328#M31655</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2004-12-03T11:01:39Z</dc:date>
    </item>
    <item>
      <title>Re: F$DEVICE lexical</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/f-device-lexical/m-p/3434329#M31656</link>
      <description>I was talking about:&lt;BR /&gt;&lt;BR /&gt;$ define /TRANSLATION_ATTRIBUTES=TERMINAL&lt;BR /&gt;&lt;BR /&gt;The CONCEALED attribute is a different matter - it is for display purposes, but, yes, the combination of both attributes has always been 'interesting'.&lt;BR /&gt;&lt;BR /&gt;VAX/VMS V3 had 3 fixed logical name tables (process?, group and system). One could not see any other tables.</description>
      <pubDate>Fri, 03 Dec 2004 13:56:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/f-device-lexical/m-p/3434329#M31656</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2004-12-03T13:56:46Z</dc:date>
    </item>
    <item>
      <title>Re: F$DEVICE lexical</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/f-device-lexical/m-p/3434330#M31657</link>
      <description>Uwe,&lt;BR /&gt;&lt;BR /&gt;&lt;QUOTE&gt;&lt;BR /&gt;VAX/VMS V3 had 3 fixed logical name tables (process?, group and system). &lt;BR /&gt;&lt;/QUOTE&gt;&lt;BR /&gt;make that four:&lt;BR /&gt;Process, Job, Group, and System; only those, and searched in that fixed order.&lt;BR /&gt;&lt;BR /&gt;&lt;QUOTE&gt;&lt;BR /&gt;The CONCEALED attribute is a different matter - it is for display purposes, but, yes, the combination of both attributes has always been 'interesting'.&lt;BR /&gt;&lt;/QUOTE&gt;&lt;BR /&gt;&lt;BR /&gt;well... "display" purposes...  not untrue, but it mostly serves to let directories be presented as devices, allowing for many "logical", and dynamic, devices mapped upon one physical.&lt;BR /&gt;Your interpunction of 'interesting' suggest things like puzzling, confusing, troublesome, or the likes of that.&lt;BR /&gt;Especially after the obligation for /TERMINAL has been lifted from /TRANS=CONCEAL, I hardly found any issue, and I grew really fond of the concept, even up to the degree that I count it as one of the things that makes VMS so great and so flexible.&lt;BR /&gt;(only one wish still standing: recursiveness, ie, allowing a directory within a concealed device to be the root of another one)&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&lt;BR /&gt;</description>
      <pubDate>Fri, 03 Dec 2004 16:02:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/f-device-lexical/m-p/3434330#M31657</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2004-12-03T16:02:48Z</dc:date>
    </item>
  </channel>
</rss>

