But that's a pretty good way to do it.

The "directories" of off the "root" must in fact be MPE accounts (whose
names appears in all caps when using HFS syntax), built with NEWACCT, on the
private volume set. The "subdirectories" within those "directories" must
actually be MPE groups (also appearing in all caps) built with NEWGROUP,
also on and homed to the private volume set. This also limits any files or
actual directories to 16 character long names, but any files in those
directories can have longer names. The Apache implementation appears to take
advantage of this, locating all of its directories under the PUB group. We
use this with Oracle and with SAMBA. So the examp6.sql file for Oracle is
/ORADATA/DEMO/examp6.sql. As far as Oracle knows, ORADATA is a directory off
of the root, but MPE knows that this is an account, and that DEMO is a
group. Being able to have Oracle on a private volume set with mirroring made
having a disc error much, much less worrisome.

To prevent someone from creating files or directories on the system
volumeset for an account that you want on a private volume set, you can
prohibit their use with
ALTACCT ACCOUNT;FILES=0;ONVS=MPEXL_SYSTEM_VOLUME_SET
Files, groups, and directories can be built on the system volume set, but
allocation of space will fail. I can send you examples of how this works in
practice offlist, or I believe that may be in the listserv archives under
"Disc Limit" in January of this year.

> -----Original Message-----
> From: John Zoltak [SMTP:[log in to unmask]]
> Sent: Tuesday, October 27, 1998 9:33 AM
> To:   [log in to unmask]
> Subject:      Re: HFS files and private volumes.
>
> Olek,
>
> AFAIK there is no way, except to build your HFS structure under a group
> entry.
>
> John Zoltak
> North American Mfg Co