HP3000-L Archives

February 1999, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Jeff Woods <[log in to unmask]>
Reply To:
Jeff Woods <[log in to unmask]>
Date:
Mon, 1 Feb 1999 16:44:28 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (36 lines)
At 11:57 AM -0800, Michael D. Hensley wrote:
>Sam Knight:
>> Can a private volume set be changed to additional system volume

<snip>

>5. Alter all of the groups that were on the userset to HOMEVS=
>   (or PURGE all of the groups/accounts)

<snip>

>Step 5 is the most work...

BULDACCT.PUB.SYS can make that a much easier task, though perhaps not a simpler
one.

Another way I've handled such things is to build a list of groups that need to
be "tweaked" using :LISTGROUP or more often :REPORT and then editing the
resulting file into a job stream or command file to make all the changes.  QUAD
and QEDIT make that pretty straightforward with their ability to change column
ranges in multiple lines with a single command.  In both those editors, the
resulting commands can even be executed directly in the editor.

In either case, it's a good idea to check any job $STDLISTs for errors or other
unexpected results.

BTW, the HOMEVS can only be changed if there are no files present in a mounted
old HOMEVS.

A quick test I usually do after making HOMEVS changes is to build a dummy file
in one of the groups.  If that succeeds, files should be able to be restored
into the volset.
--
Jeff Woods
[log in to unmask]  [PGP key available here via finger]

ATOM RSS1 RSS2