Providing software solutions since 1976

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

• 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

The order of Library assignment differs between modes of execution of SAS^®, potentially generating different results from the same code running in different environments.

For a SAS server started by the SAS Object Spawner, such as a SAS Workspace Server or SAS^®Stored Process Server, the order of Library assignment is:

1. Libraries marked as pre–assigned in metadata (assuming the METAAUTORESOURCES system option is set for the session)
2. Libraries defined by a LIBNAME statement in an autoexec file

For SAS sessions not started by the SAS Object Spawner, such as a SAS Batch Server, SAS^® Connect Server, or scheduled SAS jobs (all known as MVA SAS sessions), the order of execution is reversed:

1. Libraries defined by a LIBNAME statement in an autoexec file
2. Libraries marked as pre-assigned in metadata (assuming the METAAUTORESOURCES system option is set for the session)

Unexpected behavior is most common in MVA sessions when a SAS autoexec contains steps dependent on the successful assignment of a pre–assigned Library. Because the SAS autoexec executes prior to the Library pre–assignment, the step might fail. A typical error message is:

For the most consistent behavior across execution modes, use LIBNAME statements in an autoexec file or within the program code to assign Libraries required for the program.

Operating System and Release Information