A-Shell/Linux uses the native
unlink command to erase files, under the theory that it handles a lot of extra conditions that would otherwise require superfluous investment in redundant wheel invention. If the
unlink command returns an error, A-Shell logs it, under that theory that we really don't expect any errors from an erase operation. The most likely error, and the one in this case (2 or ENOENT) is file-not-found, but ERASE.LIT checks for that condition in advance, and presumably most applications would as well.
You can easily trigger this error message by executing a single-line program consisting of :
The question is why are you getting so many of these? Since the filespec looks like some kind of sequentially-generated work file, I would first check to see if you are perhaps trying to KILL it twice? (Note that if you SET TRACE FOPENS ON, then you'll get the trace message for every such operation whether it returns an error or not, making it easy to check if you are in fact trying to erase it twice.) It could also be that something other than the application is deleting the file before you get a chance to.
Another possibility is that there is something strange about the path, perhaps it contains more than one symbolic link or a broken one? I would start with
ls -l to see if the file exists, and perhaps to examine each level in the path to see if there is something strange with hard or soft links. I've see situations where a single physical directory might be reached under multiple paths due to links, and that can lead to all kinds of confusion.
