ohlund@A.PSY.CMU.EDU.UUCP (01/27/87)
We're having problems using search paths with logical names which define pseudo devices. Specifically, on some of local machines have a logical name, PSY$LOCAL, defined as follows: $ define/system/exec/translat=concealed psy$local - _dua0:[local.],dub0:[local.] This definition works correctly when reading files from either physical disk, but if an attempt is made to write to the second disk in the search path, the write fails. For example, the directories: dua0:[local.system] and dub0:[local.data] are both subdirectories and appear as psy$local:[system] and psy$local:[data]. The command sequence $ create psy$local:[system]a.dat succeeds. However, the sequence: $ create psy$local:[data]a.dat fails with the error message: %CREATE-E-OPENOUT, error opening PSY$LOCAL:[DATE]A.DAT; as output -RMS-E-DNF, directory not found -SYSTEM-W-NOSUCHFILE, no such file This happens consistently. Anyone have any answers?