James Byrne wrote:
> No. It is my understanding that private volume groups must have an
>identically named directory structure on the system volume group
>and that if the private VS is not mounted then this is where things
>will go.  

Well, yes and no.  Accounts and groups that reside on private volume
sets must be defined in both the system directory and the volume set
directory, but I don't believe it is true that you can save files to a
group whose home volume set is not mounted.

As you seem to have discovered, "DISC" is a device class name, not a
volume set name, so there is no conflict between "DISC" and "HAL_DATA,"
because the volumes in the HAL_DATA volume set do belong to the "DISC"
device class.  I'm not sure why the store listing shows volume
restrictions for some files and not others, but it's a common
occurrence.

John

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *