Greg asks:
> I remember being told that most of our third party software (we have Adager,
> SuprTool and VeSoft's packages, among others) had to be on the system volume
> set, which made little sense to me, but I did not care to argue the point at
> that time, as we were testing DR as well as creating private volume sets.
> Can anyone clarify if this is generally the case?

It generally isn't a requirement.  However, two things to keep in mind:

   1) some software (HP and vendors!) might not understand "private volumes".

      For example, it's a no-no for software to assume it can
      simply rename a file from one group to another within an account.
      (You can't do that if one group is on one volume set, and the other
      group is on another)

      Also, packages put on a user volume set might create groups later ...
      are they smart enough to create them on the same volume set?  (Unlikely)
      (BTW, one reason why Jeff Vance's command files are nice, but
      inadequate as a solution to the user-expressed need: ability to specify
      a default volume set for an account ... it ought to be part of the
      :ALTACCT command!)

   2) the system is quite capable of running without any of the user volume
      sets mounted.

      So...you might choose to put important packages (like HourGlass,
      SPLash! and the Lund Toolboxes) on the system volume
      set (MPEXL_SYSTEM_VOLUME_SET), and less important packages (like
      everything else :), on user volume sets.     Note the smiley!

      Seriously, we looked at this and made a concious decision for
      each product/package/application as to what volume set it should
      be on.  Our web server is on MPEXL_SYSTEM_VOLUME_SET, because
      it's quite important to our business.

--
Stan Sieler                                          [log in to unmask]
                                     http://www.allegro.com/sieler.html