I am trying to write a text file to another server with an outbound thread. I would like to not have to map a drive letter, has anyone ever done this with using the path like:
\server namec$directoryfile
This will be writing seperate text files throughout the day.
I’m just going to add my 2 cents. While what you propose will work, it may not work for long. It’s been our experience that UNC paths for file I/O lead to a panic sooner rather than later. I also can’t recommend a drive letter mapped network drive. Same problem
What we’ve seen is that if the network location is unavailable or even just slow, Cloverleaf doesn’t like it. This is with 5.4.1 (and earlier releases) on Windoze Server.)
Our solution is to always do file I/O on a local drive. We’ve used various non-Cloverleaf mechanisms to transfer files between the local drives and network drives. That used to be VB scripts run from the Windows scheduler, a utility called Opalis, and most recently Informatica PowerCenter.
.
.