We have processes to transmit files between various computers. On occasion, we'll receive an error message that the file cannot be moved because a file with that name exists in the destination. The only problem is, there is no file with that name in the destination directory. If we change the filename or the destination, it works fine so the only other moving part is 24x7. Is there something we can add to the jobs to force 24x7 to release the file when done or is this a known bug?

How is the "file move" operation implemented? Is this a JAL or VB script? If nto, what else?

: We have processes to transmit files between various computers. On occasion,
: we'll receive an error message that the file cannot be moved because a
: file with that name exists in the destination. The only problem is, there
: is no file with that name in the destination directory. If we change the
: filename or the destination, it works fine so the only other moving part
: is 24x7. Is there something we can add to the jobs to force 24x7 to
: release the file when done or is this a known bug?

: How is the "file move" operation implemented? Is this a JAL or VB
: script? If nto, what else?

It uses the JAL filemove command.

FileMove internally calls the same function that Windows Explorer calls when you drag-and-drop files or do Cut and Paste.

If you suspect that FileMove is the cause of this problem try using DOS move command instead

If you now have FileMove "source.file", "destination.file"

try replacing it with the following

Dim pid, number
RunAndWait "cmd /c move source.file target.file", "", 0, pid

If this does not fix the problem then it is not the FileMove that causes it.

windows something else

: It uses the JAL filemove command.