Suppose Arev is located on multiple servers on a WAN. The WAN is set up in such a way that some servers appear local to each other. Files on these servers can be accessed through the NLM, which is installed on all servers.

However, now suppose you need to access files on a nonlocal server. Because of the way the network is set up, the NLM does not perform any I/O on the remote server. However, if REVPARAM is adjusted appropriately, it is still possible to update the file remotely.

The thing is, though, if you do it this way, the NLM on the remote server has its own idea of what it thinks the status of the file is, and if you update it without going through the NLM you get phantom GFEs or something.

So my question is, if a support person needs to perform file maintenance on a remote server like this, how can it be done without adversely affecting the file? This is the situation I'm in, and what I do is either have the remote user execute what needs to be done, or I do the updating myself and have them restart the server (usually easier than stopping and starting the NLM).

If there's a better alternative, I'd like to use that instead. I seem to recall there possibly being a trick like having the remote user access X files not the file I updated. Then when the NLM is asked about the file I updated, it's no longer in cache so will be read from disk.

Victor

View this thread on the forum...