Providing software solutions since 1976

• Log in
• Create profile
• Welcome
  [Log out]
• Edit profile
• My SAS

• Print  |
• Feedback  |
• Share

  • E-mail
  

  E-mail This Page

  Your Name:*
  Your E-mail:*
  Recipient E-mail:*
  Send a copy to me
  Personal Message:
  
  

  * indicates a required field

ERROR: The file is already locked by another user.

The trace messages revealed that the "file is already locked" message results when two or more SAS processes attempt to create a new metadata file with the same temporary name in the same SPDE library.

Explanation

When SPDE creates a new metadata file, it first creates it with a temporary, or preliminary name. If the temporary name is already in use and cannot be opened, the number being used as the file name is incremented, and SPDE tries again. Once an available file name is found, the new data set is created. When the metadata file has been populated and is closed, the file is renamed to its permanent name.

The trace messages around the error show the source of the trouble as being contention around a temporary metadata file name. The message reporting that the file is already locked by another user indicates that a file with that name already exists in the directory, and that it is open and in use.

This is a case in which improved error reporting by the IO sub-system in version 9.2 has had the unfortunate side effect of adding confusion to an otherwise successful process. This issue didn't occur in 9.1 because the IO sub-system did not report all errors encountered. It now does a better job of reporting problems. However, it is now reporting an error in a situation that in fact, is not an error, but an anticipated occurrence. When SPDE can't get access to a given temporary file name, it just changes the name and tries again, and continues doing so until it finds a name it can use.

Impact of messages

The "file is already locked" errors are harmless. The engine is attempting to open a new file, but has anticipated that the file name may already be in use, and has made provisions to keep trying if that occurs. This is a case in which failing to open a file is an acceptable outcome, and the engine simply works around the problem. The trouble is that the IO sub-system does NOT know that the failed open is acceptable, and reports an error.

Workaround

NONE, messages are not indicating an error.

Please note: SAS 9.3 and the Hotfix on SAS 9.2, reduce the frequency of the messages, but do not completely eliminate them.

Operating System and Release Information

A fix for this issue for Base SAS 9.21_M3 is available at: