You may want to remove a file pool from the CA VM:Secure SFS configuration if you no longer want it managed by CA VM:Secure or if you have removed it from the system.
Removing a file pool from the CA VM:Secure configuration for SFS deletes that file pool from administration by CA VM:Secure; it does not delete it from SFS itself. If you remove a file pool, you must make provisions for managing it outside CA VM:Secure.
You can remove a file pool from the CA VM:Secure configuration for SFS only if there are no space allocations for it made through CA VM:Secure. This means that you must delete all the *FP= records that reference the file pool. If the *FP= record contains only the file pool to delete, delete this record. If the *FP= record references the file pool to delete and another file pool, delete only the reference to the file pool to delete.
Example:
Suppose you want to delete file pool VMXA from the CA VM:Secure configuration but leave file pool VMXB. User ID FRED contains this record in the source directory entry. Change the following record:
*FP= VMXA VMXB
To the following:
*FP= VMXB
User ID BARNEY contains this record in the source directory entry:
*FP= VMXA
Delete the entire record.
The easiest way to delete *FP= records is to execute the VMXBKP01 utility to create a USER DIRECT file. Look at this file to come up with a list of all user IDs that have *FP= records that refer to the user ID you want to delete. Then use the VMSECURE EDIT command to edit the affected user IDs and update or delete the *FP= records as described above.
Data on removed file pools remain owned by the owners who used that space when it was managed by CA VM:Secure.
To remove a file pool from the CA VM:Secure SFS configuration
vmsecure config sfs
This command displays the SFS Configuration Menu.
If you do not want to remove the file pool from CA VM:Secure administration, enter no.
When you press Enter to confirm or reject the deletion and that deletion is accepted, CA VM:Secure returns you to the screen that displays known file pools.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |