HP3000-L Archives

July 2005, Week 4

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:
"Johnson, Tracy" <[log in to unmask]>
Reply To:
Johnson, Tracy
Date:
Mon, 25 Jul 2005 15:37:47 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (40 lines)
Matthew Perdue, Quoting John Clogg <[log in to unmask]>:
> 
> > You can't move a group to another volume set with the ONVS 
> parameter. 
> > The ONVS parameter is available on the ALTGROUP command so you can 
> > alter group attributes of a group that already resides on the named 
> > volume set.  Instead, use the NEWGROUP command to build the 
> group on 
> > the new volume set and PURGEGROUP to remove it from the old one.
> 
> To possibly clarify John's comment, you cannot change a group 
> from the system volume set to a private volume if the group 
> has files in it already. 

Well, unless the NEWGROUP and ALTGROUP commands have been improved since
last I heard, you CAN, and that's how some System and Account Manager's
eat up file space on the system with "orphaned" files in a group that
has lost or moved its "home".  So I typically I STORE them off, PURGE
them, then RESTORE them after the group has a new "HOME."

ALTGROUP needs a new parameter called ";ADOPT" to pick up and move those
orphans!


Tracy Johnson
Measurement Specialties, Inc. 

BT







NNNN

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

ATOM RSS1 RSS2