<[log in to unmask]> on 11/6/98 wrote:

>  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?

    <Remainder of Original Thread Snipped>

Greg,

Many moons ago I was foolish enough to move all of my third party software onto
its own private volume set.  Yes, it can be done and all those tools you
mentioned will work from a private volume set.  HOWEVER, you will find that all
(or nearly ALL, I don't recall that clearly) of the third party installation
routines ASSUME the system volume set (or don't provide for a private volume set
install).  So, that means that you have to set up all of the groups and accounts
ahead of time by hand on your private volume set or the install fails.
Hindsight has taught me that you could first install the software on the system
volume set and then using BULDACCT create the necessary jobs to move it anywhere
you wanted (providing you have the disc space on the system volume set).
However, that involves additional work and more chances for things to go wrong.

My advice, leave well enough alone!

- John Hornberger
  Sr. Systems Programmer
  General Signal Services (A subsidiary of SPX corp.)
  [log in to unmask]