Usage Note 13619: Pre-assigning SAS libraries for the Stored Process Server
When running the Stored Process Server, you can pre-assign SAS libraries
so they do not need to be redefined in your individual Stored Processes
(SAS programs).
The approach that is used to pre-assign a SAS library that is
"metadata-based" (a "metadata-based" library uses the SAS Metadata
Libname Engine) is different from the approach that is used for a SAS
library that is not metadata-based. If you need to control access to
specific SAS data sets within your SAS library, then you will need to
use a "metadata-based" SAS library. The "Authorization" permissions
that you specify for a SAS library in the SAS Management Console (under
"Data Library Manager") are enforced only for SAS libraries that are
metadata-based.
If you want to pre-assign a SAS library that is not metadata-based, then
the following four steps will need to be completed.
1.) In the SAS Management Console under "Data Library
Manager", define your SAS library. Click the
right mouse button and select "Properties."
Select the "Options" tab on the "Properties" window
and then select "Advanced Options." Then, check
the "Library is pre-assigned" box.
2.) In the SAS Management Console under "Server Manager",
select your Stored Process Server (for example,
"SASMain - Stored Process Server"). Click the right
mouse button and select "Properties." Select the
"Options" tab on the "Properties" window. On the
"Object Server Parameters:" line specify:
METAAUTOINIT
3.) Restart your SAS Object Spawner.
4.) Now, when you run a Stored Process (SAS program), it
should be able to reference the pre-assigned SAS
library without issuing an additional LIBNAME
statement.
If you want to pre-assign a metadata-based SAS library, then the
following six steps will need to be completed.
1.) In the SAS Management Console under "Data Library
Manager", define your SAS Library. Click the
right mouse button and select "Properties."
Select the "Options" tab on the "Properties" window
and then select "Advanced Options." Then, check
the "Library is pre-assigned" box.
2.) If you do not already have a SAS AUTOEXEC file that
is used by your Stored Process Server, then
you will need to create one. For example,
you could create a file called "autoexec_stp.sas"
and save it in your root directory for your
Stored Process Server. For example, you might
save it in the following directory:
C:\SAS\project_name\Lev1\SASMain\StoredProcessServer
3.) In your SAS AUTOEXEC file, add a LIBNAME statement to
allocate your SAS library that you want to pre-assign.
For example:
/* LIBNAME for a metadata-based SAS library */
libname testmeta meta library=testmeta
metarepository="Default";
4.) Modify your SAS Configuration file (for example,
"sasv9_StorProcSrv.cfg") for your Stored Process
Server. Add a "-autoexec" line that references
your SAS AUTOEXEC file that you created in the above
step. For example:
-autoexec "c:\path_to_your_autoexec\autoexec_stp.sas"
5.) Restart your SAS Object Spawner.
6.) Now, when you run a Stored Process (SAS program), it
should be able to reference the pre-assigned SAS
library without issuing an additional LIBNAME
statement.
The above discussion applies to SAS 9.1.3. Prior to SAS 9.1.3, the
pre-assignment of SAS libraries was performed differently.
For more information, see:
http://support.sas.com/rnd/itech/notes/preassignedlibrefs.html
If you have problems accessing a pre-assigned SAS library in
your stored process, then as a test specify the LIBNAME statement
at the top of your SAS code for your stored process. Then, run
the stored process and check your SAS log for error messages.
See SAS Note #017720 for more troubleshooting suggestions.
Operating System and Release Information
SAS System | SAS Integration Technologies | Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.1 TS1M3 | |
Microsoft Windows NT Workstation | 9.1 TS1M3 | |
Microsoft Windows Server 2003 Standard Edition | 9.1 TS1M3 | |
Microsoft Windows Server 2003 Datacenter Edition | 9.1 TS1M3 | |
Microsoft Windows Server 2003 Enterprise Edition | 9.1 TS1M3 | |
Microsoft Windows 2000 Professional | 9.1 TS1M3 | |
Microsoft Windows 2000 Server | 9.1 TS1M3 | |
64-bit Enabled Solaris | 9.1 TS1M3 | |
Microsoft Windows 2000 Advanced Server | 9.1 TS1M3 | |
z/OS | 9.1 TS1M3 | |
Linux | 9.1 TS1M3 | |
64-bit Enabled HP-UX | 9.1 TS1M3 | |
Linux on Itanium | 9.1 TS1M3 | |
HP-UX IPF | 9.1 TS1M3 | |
Microsoft Windows XP Professional | 9.1 TS1M3 | |
Microsoft Windows 2000 Datacenter Server | 9.1 TS1M3 | |
OpenVMS Alpha | 9.1 TS1M3 | |
64-bit Enabled AIX | 9.1 TS1M3 | |
Tru64 UNIX | 9.1 TS1M3 | |
*
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.
Type: | Usage Note |
Priority: | |
Topic: | System Administration ==> Servers ==> Integration Technologies
|
Date Modified: | 2006-05-17 16:45:03 |
Date Created: | 2004-10-14 12:31:19 |