The following messages are displayed on the VM:Operator System window and in the current syslog file when logfile processing must
erase the oldest syslog file from the syslog disk because the syslog disk has become full:
<<< snip >>>
DMSRNM002E File CMS EXEC A not found
DMSRNM002E File CMS$$VMY EXEC A not found
<<< snip >>>
Release : 3.1
Component : CA VM:Operator
When the oldest syslog file on the syslog disk is erased because the syslog disk has become full, the following messages are also displayed
on the System window and in the current syslog file:
<<< snip >>>
DMSRNM002E File CMS EXEC A not found
DMSRNM002E File CMS$$VMY EXEC A not found
<<< snip >>>
The root cause of this problem is that the VM:Operator service machine has a file named CMS EXEC on a read-only extension to the server's A-disk, but does not have a CMS EXEC file on the A-disk itself. You can rename or erase the CMS EXEC file on the read-only extension disk to prevent the display of the DMSRNM002E messages.