Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!cbatt!ucbvax!A.PSY.CMU.EDU!ohlund
From: ohlund@A.PSY.CMU.EDU.UUCP
Newsgroups: mod.computers.vax
Subject: Pseudo-device search lists
Message-ID: <8701280356.AA07659@ucbvax.Berkeley.EDU>
Date: Tue, 27-Jan-87 14:42:47 EST
Article-I.D.: ucbvax.8701280356.AA07659
Posted: Tue Jan 27 14:42:47 1987
Date-Received: Thu, 29-Jan-87 03:32:58 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 26
Approved: info-vax@sri-kl.arpa

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?