Path: utzoo!utgpu!water!watmath!clyde!rutgers!sri-spam!ames!amdcad!sun!pitstop!sundc!seismo!uunet!sdrc!scjones From: scjones@sdrc.UUCP (Larry Jones) Newsgroups: comp.os.vms Subject: Re: VMS logicals help -> dir and -> sub-dir Keywords: vms4.5, logicals Message-ID: <206@sdrc.UUCP> Date: 8 Feb 88 23:29:48 GMT References: <722@zycad.UUCP> Organization: Structural Dynamics Research Corp., Cincinnati Lines: 42 In article <722@zycad.UUCP>, kjb@zycad.UUCP (Kevin Buchs) writes: < < If I define a logical as node::disk:[directory] then there is no way to < refer to subdirectories. If I instead define the logical as < node::disk:[directory.] (notice the trailing dot) then this logical does < allow [sub-directory] to be appended. It however cannot be used without < appending a subdirectory, and there is no way to append a null subdirectory. Au contraire (forgive my spelling if incorrect) - there is a way to append a null subdirectory. Just use [000000] like you would on a real disk. < $ dir log1:[spike] < < Directory USER$DISK:[BUCHS.][SPIKE] < < .CMSRC;1 BUFFER.MAC;1 CMS.DIR;1 DEMO.DAT;4 < ... < ... < STIM5.WAV;1 STUB.COM;4 STUB.COM;3 STUB.DIR;1 < %DIRECT-E-OPENIN, error opening LOG1:[SPIKE] as input < -RMS-F-DIR, error in directory name < TEQ.C;2 TEQ.C;1 < < Total of 90 files. < < Notice the output from : dir log1:[spike]? The error message < comes out in the middle of the first directory listing. Is a VAX 785 really < a parallel machine? Nope. I SPRed this a long time ago but DEC doesn't consider it enough of a problem to bother fixing. The output of the DIRECTORY command is buffered and they don't bother to flush the buffer before printing error messages so you get the message in the middle of your listing. You can usually get the same effect from $ DIRECTORY DISK:[*...] as you run into directories where you don't have read permission. -- ---- Larry Jones UUCP: uunet!sdrc!scjones SDRC MAIL: 2000 Eastman Dr., Milford, OH 45150 AT&T: (513) 576-2070 "When all else fails, read the directions."