|
|
|
Reason:
You entered a command, such as DELENTRY, that caused CA VM:Secure to try to delete a file space; however, CA VM:Secure does not manage the file pool in which the file space resides. This problem occurs when there is an invalid *FP= record in the directory entry of the user that owns the file space. This record is invalid because it identifies a file pool that CA VM:Secure does not manage. Most likely, someone copied this directory entry from a system on which CA VM:Secure does manage the specified file pool. The file space is not deleted.
Action:
Use the EDIT command to remove the invalid *FP= record, and then try your command again.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |