RevG (AREV Specific)
At 03 MAR 2000 07:37:22AM Ted Percival wrote:
RevG Application running with NT Server and Win98 clients.
Rev.exe was shut down and there was two Rosfiles still open which caused to hang.
How can Rosfiles run with out Rev.exe, is it due to the speed with NT and Win98.
Thanks in advanced.
At 03 MAR 2000 10:51AM DSig wrote:
Ted,
We have also seen this in OI clients. For example if we connect through pcAnywhere and do some work then exit OI. Then trying to copy (explorer level) etc we get the 'file being used .. '
The only thing we have been able to do to get this back is to reboot server (not a good answer but).
Possibly someone at rti will have a better workaround.
DSig
At 03 MAR 2000 03:38PM CT Savell wrote:
Ted,
I am not sure I understand your question.
If it is simply an intellectual querie asking someone to explain your observation as to how or why your application was able to continue running even after Rev.exe was somehow deleted (or stopped)from the hard drive, I would guess that the parts of the application that were still operating were preloaded in RAM which had not been flushed by the Operating system. Rev.exe is in RAM until you exit.
If on the other hand, you are asking how can you "unlock" files that were left open after a catastophic shutdown of some sort, then let me share that I have seen this happen on both the NT and Novell networks. I believe DSig is correct that you could reboot the network server (at least I think that is what DSig suggested) and that would reset the locks. It has been my experience that simply disconnecting the workstation from the server does not work. The most effective way we have used to release network locks from NT and Novell is to RECREATE-FILE on the files that are locked. This changes the name of the file from the Network operating system's viewpoint and it does not know that the new file name was locked. Of course from your applications viewpoint RECREATE-FILE is just resizing the files and its name from the application's viewpoint has not changed.
At 05 MAR 2000 02:51AM Steve Smith wrote:
On your systems there is significant caching - you are seeing the effect of the server keeping the files open in case of later use (ie. cached)
This is common in REVG - always advise a server restart in the case of a crash or hung session.
Steve
At 06 MAR 2000 10:24AM Warren wrote:
Are you talking about ROS files (e.g. ROSxxxxx.nnn (3 digit extension) )or LINK files (e.g. ROSxxxxx.LNK (LNK extension))?
ROS files do not record lock and should not be used for shared access (unless read-only). They are also cached differently by the Revelation engine (64K chunks vs 2K chunks).
At 09 MAR 2000 05:00PM Charles Schmidling wrote:
That's cute. I thought Rev executed an UNLOCK ALL on the way out the door?
Charles
At 10 MAR 2000 05:28PM Warren wrote:
It does, more or less, but only on a *graceful* exit - not a hang or crash.
At 12 MAR 2000 05:25AM Charles Schmidling wrote:
Well, that's RUDE!!
It could also explain why I have one work station that likes to hang. It generally will return after killing the DOS session. But not always and not well. Then it progressively gets worse. Depends, sometimes, on how well the morning bootup works. Hmmm. Should re-boot the server more often. The client likes to leave it running since its in the front office (different building) and the person using it arrives before and leaves after the front people do.
Since the station generally accesses one main customer during the day (the 0th CASH SALE fellow), it stands to reason that a locking lockup error could occur. Should check my locked record wait state routine, just in case. Oops.
Thanks.
Charles