Check to make sure you don’t have 2 threads trying to save to the same filename. (Or both inbound and outbound messages on the same thread trying to save to the same filename.) The SMAT file gets locked by whoever gets there first.
This can also happen if you stop a thread, view the SMAT file, and then start the thread with the SMAT utility still running. The SMAT utility still has the file locked and the thread can’t open it for writing. Another gotcha of this scenario is that when the SMAT utility is closed, the files are still not opened by the thread until it is cycled, so you lose any messages that would have been saved.
For this reason, it’s always a good idea to stop your thread, copy the SMAT files to another location, then open the copies instead of the originals in the SMAT utility.
Author
Replies
Viewing 1 reply thread
The forum ‘Cloverleaf’ is closed to new topics and replies.