Problem:

Is there a way of stopping MFDEBUG.LOG being generated or changing its location.

Resolution:

There is no way to specify an alternate location for the MFDEBUG.LOG file.  However, you can affect its generation by trying the following:

1) Create a "read-only" dummy mfdebug.log file in the folder.  This should

   stop any new versions of the file being created.

2) Another option would be to set the runtime tunable called:

   signal_regime

   (see online documentation for full details).  You would need to set this option

   to signal 11 with a value of 2.

3) Alternatively (and probably the best option) is to identify the reason for the exception and

    to fix it within your application.