Can someone tell me how to stop ashell from logging mkdir commands to ashlog.log? only trace option i have set is SIGHUP

thanks

mkdir commands are logged if TRACE=FOPENS or if there is an error in the operation. (The FOPENS trace is pretty verbose anyway, so it didn't seem as if adding mkdir to it would be a big deal, unless you open very few files but create a lot of directories.)

To doublecheck which traces are on, just use SET TRACE. If confirmed that FOPENS is not set, then it suggests that an error is occurring in the mkdir.

What does the log message say?

the error portion explains it then as the directory already exists. I took the shortcut of just attempting to create it with out checking if it exists and since i attempt to create each time i go to create the file, upto 1000 per directory, my ashlog.log fills up with these. thanks

I am probably speaking out of turn and you probably already use this but.

xcall miamex,3

If you setup the parameters right you can get back a status of non zero if the directory does not exist. I use this alot for converting to and from native and amos.

Again just ignore this if I am behind.

thanks, looks like i was following jacks suggestion in the documentation for miamex 97 and saving myself a step

Both points are valid (i.e. you could avoid the error by checking first, as Ken suggests, but on the other hand, as I myself suggested, checking is basically no more efficient than just trying to create the directory.)

I think I'll remove the automatic log message feature when the error is simply "directory already exists".