[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference noted::hackers_v1

Title:	-={ H A C K E R S }=-
Notice:	Write locked - see NOTED::HACKERS
Moderator:	DIEHRD::MORRIS

Created:	Thu Feb 20 1986
Last Modified:	Mon Aug 03 1992
Last Successful Update:	Fri Jun 06 1997
Number of topics:	680
Total number of notes:	5456

503.0. "-< File Currently Locked >-" by PLDVAX::GUNDAVARAM (My name is Bond, James Bond....) Fri Jun 19 1987 15:33

	Hello:


	Sometimes, I can't delete my files, when I try to
	delete them, it says, "FILE CURENTLY LOCKED BY ANOTHER USER",
	so when it says that, I then do a: $ Show Devices/Files,
	and then it says:

--------------------------------------------------------------------------------

	Username	PID		Filename

	no privilege	0000000		no privilege for attempted operation
	no privilege	0000000		no privilege for attempted operation
	GUNDAVARAM	2130EF0		DISK$2:[GUNDAVARA]VT340.TXT

--------------------------------------------------------------------------------

	Then, I check to see if I was logged on to some other node
	on the cluster and then I didn't properly $ CLOSE it that
	time, but NO, I was logged on to any other node.

	SO, WHAT DO I DO NOW TO DELETE THE FILE?



							Thanks,

							-=- TMS -=-

T.R	Title	User	Personal Name	Date	Lines
503.1	Oops!!!!!	PLDVAX::GUNDAVARAM	My name is Bond, James Bond....	`Fri Jun 19 1987 15:37`	19
	-------------------------------------------------------------------------------- < Note 503.0 by PLDVAX::GUNDAVARAM "My name is Bond, James Bond...." > -< File Currently Locked >- -------------------------------------------------------------------------------- > time, but NO, I was logged on to any other node. That's supposed to be: time, but NO, I was't logged on to any other node. Thanks, -=- TMS -=-
503.2		VAXWRK::NEEDLE	Jeff Needle	`Fri Jun 19 1987 15:53`	6
	Did you issue an OPEN command? If so, what was the logical name that you assigned to the file when you opened it? You must use the CLOSE command. If you can't remember, try doing a SHOW LOGICAL/PROCESS to jog your memory. That should do it. Jeff.
503.3		VIDEO::LEICHTERJ	Jerry Leichter	`Sat Jun 20 1987 11:21`	11
	Note that: $ OPEN FOO ... $ DEASSIGN FOO does NOT close the file that was opened as FOO - but DOES render it completely inaccessible. The only way to close it that I know of is to log the process out. (Well, not strictly true...if you knew the internal file number for the PPF that FOO pointed to, you could, from a program, create a new logical to point to it...non-trivial.) -- Jerry
503.5		VAXWRK::NEEDLE	Jeff Needle	`Mon Jun 22 1987 01:13`	8
	My suggestion was to use the CLOSE command, not to DEASSIGN the logical. In case the logical assigned at the time of the OPEN was forgotten, a SHOW LOGICAL will potentially serve as a reminder. At that time, a CLOSE can be issued. I did not mean to infer that a DEASSIGN should be issued. Of course, logging the process out will also free up the file. j.
503.6	STOP/ID=NNN	CLOSUS::DCHAVEZ	Dale C. - CXO3 Colo Spgs	`Wed Jun 24 1987 14:48`	7
	RE:< Note 503.0 by PLDVAX::GUNDAVARAM "My name is Bond, James Bond...." > One workaround I use is to log back into the same node that has the locked file and $ STOP/ID=2130EF0 (or whatever your PID is). Dale