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

Conference star::wizards

Title:	"ASK THE WIZARDS"

Moderator:	QUARK::LIONEL

Created:	Mon Oct 30 1995
Last Modified:	Mon May 12 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	1857
Total number of notes:	3728

1577.0. "Open: overriding file interlocking?" by STAR::JKEENAN () Tue Feb 11 1997 08:53

Date: Wed, 22 Jan 1997 13:39:14 -0500
Message-Id: <[email protected]>
From: "VMS001::WWW"@vms001.das-x.dec.com (22-Jan-1997 1339)
To: [email protected], [email protected], [email protected]
Subject: Ask the Wizard: '[email protected]'

Remote Host: mach1.gs.com
Browser Type: Mozilla/3.0 (X11; I; SunOS 4.1.3_U1 sun4m)  via proxy gateway  CERN-HTTPD/3.0 libwww/2.17
Remote Info: <null>
Name: Alan M Buckwalter
Email Address: [email protected]
CPU Architecture: VAX
Version: v 6.1
Questions: 

I am working on an application that open's an
index file with a generic "open()" C system call.
The file is locked by another process.

At present, I am getting the following message:

"%rms-e-flk, file currently locked by another user."

The "help" page claims that I can specify optional
file parameters to the fab/rab, but I am not sure if
this is what I wish to do.

Do you know of a working syntax of the open() command
to override file interlocking ?

	i.e.:	open(filename,O_RDONLY, ...)

Thanks,

Alan

T.R Title User Personal
Name Date Lines

1577.1 Modify Process Holding Lock XDELTA::HOFFMAN Steve, OpenVMS Engineering Tue Feb 11 1997 15:14 14

T.R	Title	User	Personal Name	Date	Lines
1577.1	Modify Process Holding Lock	XDELTA::HOFFMAN	Steve, OpenVMS Engineering	`Tue Feb 11 1997 15:14`	14
	This error indicates that another process has opened the file without allowing concurrent access of the type requested. Overriding this denial and this interlock is not something that should be attempted lightly. Look first at the application holding the lock, and update it to allow concurrent file sharing. Low-level overrides are available, but these involve direct access to the XQP -- see the I/O User's Reference Manual -- and these can result in the return of inconsistent or corrupt data to the caller. (That's why the locks are there in the first place...) Also see the BACKUP/IGNORE=INTERLOCK command.

   This error indicates that another process has opened the file without
   allowing concurrent access of the type requested.  Overriding this
   denial and this interlock is not something that should be attempted
   lightly.  Look first at the application holding the lock, and update
   it to allow concurrent file sharing.

   Low-level overrides are available, but these involve direct access
   to the XQP -- see the I/O User's Reference Manual -- and these can
   result in the return of inconsistent or corrupt data to the caller.
   (That's why the locks are there in the first place...)

   Also see the BACKUP/IGNORE=INTERLOCK command.