FILELOCKS

FILELOCKS

Specifies whether file locking is on or off and what action should be taken if a file cannot be locked

Default: FAIL

Valid in: SAS invocation, SASV8_OPTIONS environment variable, configuration file

UNIX specifics: all

Syntax
Details
See Also

Syntax

-FILELOCKS NONE | FAIL | CONTINUE

Details

When file locking is in effect, the SAS System prevents these situations:

two SAS sessions simultaneously opening the same SAS file for update or output.
two SAS sessions accidentally using the same work subdirectory if they are sharing the same work directory.

You can use the following arguments with the FILELOCKS option:

NONE: turns file locking off. SAS files are not protected from shared update access.
FAIL: turns file locking on. If a file cannot be locked, an attempt to open it fails.
CONTINUE: turns file locking on. If a file is already locked by someone else, an attempt to open it fails. If the file cannot be locked for some other reason, the file is opened and a warning message is sent to the log.

For file locking to work on some hosts, you must have the host's "file locking service" running. This usually involves having a lock daemon (such as lockd) and a stat daemon (such as statd) running. You may also need to execute other commands. For specifics, refer to the man pages or system administration instructions for your host.

In addition, if you are working with NFS-mounted files, the "file locking service" must be running both on your local host and on the remote host.

See Also

WORKINIT

Chapter Contents
Previous
Next
Top of Page

Default:	FAIL
Valid in:	SAS invocation, SASV8_OPTIONS environment variable, configuration file
UNIX specifics:	all