When you launch a SAS^® process in a UNIX environment, the following message might appear:

   UNABLE TO OPEN/READ MESSAGE FILE USING THE -MSG PATHS

One cause of this message is malfunctioning UNIX file locking.

You can test to determine whether UNIX file locking is causing problems by invoking SAS with the FILELOCKS option set to a value of NONE:

   sas -filelocks none

Set -FILELOCKS NONE only as a test.
If you update a SAS data set while the setting is in effect, data corruption can occur.

If setting -FILELOCKS NONE enables you to invoke a SAS session without errors, ask your UNIX system administrator to recycle the daemons rpc.statd, rpc.lockd, and nlockmgr on both the host and on the NFS client.

Operating System and Release Information

Product Family	Product	System	SAS Release
			Reported	Fixed*
SAS System	SAS Foundation	Linux for x64	9.2 TS2M0
		Linux	9.2 TS2M0
		HP-UX IPF	9.2 TS2M0
		64-bit Enabled Solaris	9.2 TS2M0
		64-bit Enabled HP-UX	9.2 TS2M0
		64-bit Enabled AIX	9.2 TS2M0
		Solaris for x64	9.2 TS2M0

* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.

---

If UNIX-level file locking has degraded, an error occurs when you launch a SAS® process.

Type:	Usage Note
Priority:	medium

Date Modified:	2012-04-19 13:26:12
Date Created:	2011-12-03 08:50:24