Reason:
The indicated CMS file was not located when required. CA VM:Secure may have been looking for the file on a user's minidisk or on a minidisk belonging to the CA VM:Secure service virtual machine depending on the command being executed. The command terminates with return code 28.
Action:
If CA VM:Secure is not managing any file pools and the file name and file type in the message is FILEPOOL EXEC, you can ignore this message. Otherwise, contact Technical Support.
Reason:
If your site has configured CA VM:Secure for SFS, CA VM:Secure displays this message during initialization. It indicates that the access mode for MAINT 193 (where the FILEPOOL EXEC is found) conflicts with a mode specified for the VMSECURE product minidisks. The CA VM:Secure ASSIGN and CHANGE commands use the CMS FILEPOOL EXEC to rename an individual file space within a file pool.
Action:
Ensure that the access mode for MAINT 193 is different from any mode specified on an ACCESS record in the PRODUCT CONFIG file.
|
Copyright © 2014 CA.
All rights reserved.
|
|