Reason:
While CA VM:Secure was processing the DASD CONFIG file during system initialization, CA VM:Secure determined that two or more EXTENT records on the volume overlapped or defined space past the end of the volume. Initialization fails.
Action:
Correct the DASD CONFIG file before starting CA VM:Secure again.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |