When you say the service is throwing a “No such file or directory error” error, do you mean that an actual exception is being thrown or is the “error” being returned in the directory listing?
I ask because I have used the WmPublic/pub.client.ftp services in a similar fashion before and I noticed that for some operating systems (ex. VMS), when a file was not a present, the directory listing (ie. dirlist) would come back null, while for some other operating systems (ex. Unix), a message would actually be returned in the first element of dirlist that read “: No such file or directory.” Because of this behavior, I had to incorporate this message into my logic when checking whether files existed or not. Example:
BRANCH (Evaluate Labels = True)
– %dirlist% != $null && %dirlist% != “: No such file or directory”
---- Process File
You may want to try that.
Now, as for your try-catch question, as the other member pointed out, if you’re catching the error, then no excpetions should be thrown and hence the error should not show up in the log. I guess, however, a couple of possibilities (that I can think of) could cause this type of behavior:
(1) Many people tend to include as the last step of their catch block an EXIT and signal FAILURE step so the error gets propagated and logged to the monitor. If you have this step in your catch block, you may want to think about removing or putting some conditions around it.
(2) It could be that the service that is being invoked in the catch block and that is throwing the error has its logging turned on. In that case, you may want to turn off logging for that service.
Hope this helps.