|
|
|
Reason:
During initialization, CA VM:Secure could not find any lines in the VMSECURE MESSAGES file with the correct message format. The correct format is a four‑digit message number immediately followed by a one‑character severity code, then one blank space followed by the message text. This file is probably not a messages file. CA VM:Secure initialization fails.
Action:
Use a text editor such as XEDIT to edit the VMSECURE MESSAGES file to determine if it is a valid VMSECURE MESSAGES file. If you cannot find the correct messages file, reload the VMSECURE MESSAGES file from the installation tape and restart CA VM:Secure. If necessary, your system administrator can contact Technical Support.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |