|  | 
	The MTU command procedure copies certain MS files to the current
	directory for temporary use. After the operation is complete, these
	files are deleted.
	If you are set default to MCC_COMMON, then these files are already
	present in the current working area and need not be copied. The
	question is which directory were you sitting in while running MTU ?
	If the command procedure did not copy any files, then it will not
	try deleting them. (Note that, in any case, only the highest version 
	is deleted). 
	Rahul.
 | 
|  | Rahul
I was setting in a different directory using the "master" copy of the MCC
data dictionary in that directory.  I had a logical, "MCC_BACKUP" defined
to point to this directory, and upon running the "MCC_MIB_COMPILER" launched
appl from the ICMP, I redefined MCC_COMMON as a search string pointing to 
first MCC_BACKUP, then SYS$COMMON:[MCC].
The previously mentioned .MS files are gone from MCC_COMMON (SYS$COMMON:[MCC]).
So for some reason they must have been deleted because the flags were set.
I've been trying to come up with this procedure to compile MIBs and update 
the "master" copy of the data dictionary in a different directory (MCC_BACKUP)
and everything appeared to work on several iterations.  Now that this has 
happened, I have no clue why.
A copy of the command procedure that I wrote to do  the above follows:
$ set def mcc_common
$ DEFINE MCC_COMMON MCC_BACKUP,sys$common:[mcc]
$ on error then goto exit
$ @mcc_common:mcc_TCPIP_MTU
$ copy mcc_backup:*dictionary*.* sys$common:[mcc]*.*
$ copy mcc_backup:*definition*.* sys$common:[mcc]*.*
$ purge /keep=2
$ WRITE SYS$OUTPUT -
  "In order for MIB updates to take effect, you must stop and restart MCC."
$EXIT:
$ Deassign MCC_COMMON
$ INQUIRE PAUSE "o Press the RETURN to exit..."
$ set def mcc_common
$ exit
Is there something glaringly wrong with this concept?
Thanks
Merlin
 |