Hi all, I've got an account on a user volume set which I want to migrate to the system volume set on another system. After playing with NEWACCT and NEWGROUP commands for a few minutes I figure the easiest way to recreate the account structure is with: BULDACCT: endtest%vsacct=<carriage return> Well, it worked and it didn't: report @.endtest ACCOUNT FILESPACE-SECTORS CPU-SECONDS CONNECT-MINUTES /GROUP COUNT LIMIT COUNT LIMIT COUNT LIMIT ENDTEST 0 ** 0 ** 0 ** */MCT 0 ** 0 ** 0 ** */MHSUM 0 ** 0 ** 0 ** */PRODFILE 0 ** 0 ** 0 ** */PRODJCL 0 ** 0 ** 0 ** */PRODLIB 0 ** 0 ** 0 ** */PRODOBJ 0 ** 0 ** 0 ** */PRODSQL 0 ** 0 ** 0 ** */PUB 0 ** 0 ** 0 ** */SCHEMA 0 ** 0 ** 0 ** */SQLGEN 0 ** 0 ** 0 ** */XPRODJCL 0 ** 0 ** 0 ** */XPRODLIB 0 ** 0 ** 0 ** */XPRODSQL 0 ** 0 ** 0 ** As you may know, all those cute little *'s in front of the group names indicate that they are user volume groups; and a listgroup of one these shows: Garth: listgroup mct.endtest ******************** GROUP: MCT.ENDTEST DISC SPACE: 0(SECTORS) PASSWORD: ** CPU TIME : 0(SECONDS) SECURITY--READ : GU CONNECT TIME: 0(MINUTES) WRITE : GU DISC LIMIT: UNLIMITED APPEND : GU CPU LIMIT : UNLIMITED LOCK : GU CONNECT LIMIT: UNLIMITED EXECUTE : GU PRIV VOL : YES SAVE : GU FILE UFID: $055D0004 $3BD15939 $00195FBE $59032439 $1784B86C MOUNT REF CNT: n/a HOME VOL SET : CAP: BA,IA Note the PRIV VOL: YES while HOME VOL SET is blank. Cool! I just love the strange things you can do with user volumes. -- Evan