There are a couple of options with getting SAS Stored Processes to access Metadata Libraries. 1. Pre-Assignment of Libraries or Connecting as a Single (and therefore Shared) SAS User Account The pre-assignment of libraries means that when the Object Spawner is initiated, the libraries are made available to the end
Within SAS 9.2 you can now create shared prompts to use across information maps and stored processes. To get to the Shared Prompt capability from SAS Management Console: Move to Folders Tab Create Stored Process enter 'dummy' data for STP screens until you arrive at the Parameter Entry Screen. On
(SAS 9.2 Implementations) When saving SAS Stored Processes, the 'sassrv' internal user account is used to write the physical .sas files on the server. Security of these files (to reduce the users from overwritting other's .sas stored processes) can be accomplished via the Resource Management plug-in for SAS Management Console.
Once you move to production, you really dont need all of that STP code in the system right? Here are two quick statements you can use to reduce the amount of logging done. options obs=max nosyntaxcheck; %let SYSCC=0; April 2008 UPDATE: Received a question concerning what is impacted by this
SAS Management Console Plug-in BI Manager "The "Stored Process Manager" has been replaced by the "BI Manager" in the SAS Management Console when running SAS 9.1.3 SP4 and later. The "BI Manager" contains all of the functionality (and more) that was present in the "Stored Process Manager." So, the "Stored
Earlier in the year, I attempted to convert to a SAS Stored Process a SAS IntrNet program that used statements such as: data _null_; set datatable; put 'html code here' variable item; run; However, it doesn't work when simply removing the SAS IntrNet headers (such as options, and ods html
Well, I had a few users this week who wanted to access a print out of one record in the database. Fortunetly, they all know the primary key - so the query was really simple. However, to make it extremely easy for users, I didn't want to link to another
Running a stored process (or STP) is a SWEET thing! All of my users are using the limited number I have made available, and I'm sure many new STPs will be written as soon as the users realize how easily they can be created. When first writing an STP for
I have been attending a quality conference this week & found a gentleman who wrote 20,000 lines of VB code to allow users to generate graphs through an Excel GUI interface. After the presentation on his Visual Basic analytic system, I approached him to obtain the detail of his 8
So you modified the SAS EG character formatted constraints to resolve automatically with surrounding single-quotes. (Seen below from Stored Process Wizard and Management Console screens.) Of course, the pain now is trying to pass dynamic parameters through the %stpbegin & %stpend statements.
