Using a PURGEGROUP to clean volumes up
February 9, 2018
Is using PURGEGROUP a way to clean up where groups reside on multiple volume sets? I want to remove groups from Volumesets that aren't considered HOMEVS.
Tracy Johnson says
The syntax for a command on group PUB.CCC might read
PURGEGROUP PUB.CCC;ONVS=USER_SETSW
Denys Beauchemin says
The ALTGROUP, PURGEGROUP and NEWGROUP commands act on the specified volumeset after the ONVS keyword.
The HOMEVS keyword is used to specify in which volumeset the group is supposed to reside and where the files will be found in a LISTF or FOPEN.
If you have the same group.account existing on multiple volumesets and they have files in them, the entries on volumesets—other than what is in HOMEVS for that group—are invisible. If you want to get to them, you need to point the group's HOMEVS to that volumeset and then you can get to the files.
If there are no files in the group.account of other volumesets, it's not a big deal.
Keven Miller says
You could review the volume scripts available that were once on HP's Jazz server.
Take care in using the PURGEGROUP command. You can have files existing in the same group name, on separate volumes—which makes mounting that group a problem. So make sure the group on the volume is clean of files you might desire before the PURGEGROUP.
HP's documentation for the PURGEGROUP command has a similar warning.
Do not attempt to purge the PUB group of the SYS account. The public group of the system account, PUB.SYS, cannot be completely purged. If you specify this group in the group name parameter, all non-system and inactive files are purged, which seriously impairs the proper functioning of the entire system.