This sample shows you how to prepare an existing stored process for use with an information map. Preparation requires these three main steps:
After you complete these steps, the stored process is ready to be associated with an information map.
Note: This sample was written using SAS Management Console 9.1.3 and SAS Information Map Studio 3.1. For a sample for use with version 4.2, see Sample 39432.
Note: For a sample that explains how to create a stored process by using SAS Enterprise Guide, and then associating that stored process with an information map, see Sample 26175
Note: To perform the steps in this sample, you must have the ability to perform tasks in SAS® Management Console.
As the input table for the stored process, this sample uses the SASHELP.CLASS table. If you want to follow along with the sample, copy and save the code shown below. For this example, the stored process is named stpclass.sas
. Make note of the physical location. You will need it later when you register the stored process in metadata.
Note: As part of preparing the stored process, you will make temporary modifications to the code.
*ProcessBody;
%stpbegin;
%let workpath=%sysfunc(pathname(work));
|
Note: The *PROCESSBODY, %STPBEGIN, and %STPEND statements are required in order to create a stored process that can be used in SAS® Web Report Studio.
Note: If you do not specify a workspace server, then the stored process will not be available to select in SAS Information Map Studio.
c:/storedprocesses
). stpclass.sas
.In order to associate a stored process with an information map, the stored process must have an associated table. That table must exist so that you can register its structure in metadata (discussed later). There are several ways to create this table. For this sample, you can submit the following code, which will output a table with one observation. You can submit the code in an interactive Base SAS session or in a SAS Enterprise Guide code node.
libname biout "c:\temp";
data biout.class;
set sashelp.class (obs=1);
run;
|
The structure of the table that is used in the stored process (in this sample, BIOUT.CLASS) must be registered in metadata. Structural information includes column names, formats, informats, lengths, and data types. At this point, the sample table has one observation.
Tip: In order to register the table, only the table structure is needed, so, technically, the table could be empty.
BIOUT
as the name of the library. (The table must be called BIOUT because that is the name of the library used in the sample stored process.) BIOUT
as the libref and enter the path where you saved the table. In this sample, the table was saved to c:\temp
. Now, you are ready to associate the stored process with the information map.
stpclass
.
Note: If your stored process is not in the list, then view its Execution properties in SAS Management Console and verify that you selected to run the stored process on a SAS Workspace Server.
If the test results include all of the rows in the CLASS table (and not just one observation), then the stored process has executed successfully.
If the test results include all of the rows in the CLASS table (and not just one observation), then the stored process has executed successfully.
For more information about SAS stored processes, see the SAS 9.1.3 Integration Technologies: Developer's Guide.
For more information about using stored processes with SAS Web Report Studio, see "Making Stored Processes Available to SAS Web Report Studio" on page 124 in the SAS® 9.1.3 Intelligence Platform Web Application Administration Guide.
For more information about SAS Information Map Studio, see the SAS Information Map Studio documentation page.
For more information about SAS Management Console, see the SAS Management Console documentation page.
These sample files and code examples are provided by SAS Institute Inc. "as is" without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. Recipients acknowledge and agree that SAS Institute shall not be liable for any damages whatsoever arising out of their use of this material. In addition, SAS Institute will provide no support for the materials contained herein.
These sample files and code examples are provided by SAS Institute Inc. "as is" without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. Recipients acknowledge and agree that SAS Institute shall not be liable for any damages whatsoever arising out of their use of this material. In addition, SAS Institute will provide no support for the materials contained herein.
Type: | Sample |
Topic: | Data Management ==> Data Sources ==> Information map Query and Reporting ==> Interactive Querying Query and Reporting |
Date Modified: | 2008-11-20 14:35:41 |
Date Created: | 2008-11-17 22:56:06 |
Product Family | Product | Host | Product Release | SAS Release | ||
Starting | Ending | Starting | Ending | |||
SAS System | SAS Information Map Studio | Microsoft® Windows® for x64 | 3.1 | 9.1 TS1M3 SP4 | ||
Microsoft Windows 2000 Advanced Server | 3.1 | 9.1 TS1M3 SP4 | ||||
Microsoft Windows 2000 Datacenter Server | 3.1 | 9.1 TS1M3 SP4 | ||||
Microsoft Windows 2000 Server | 3.1 | 9.1 TS1M3 SP4 | ||||
Microsoft Windows 2000 Professional | 3.1 | 9.1 TS1M3 SP4 | ||||
Microsoft Windows Server 2003 Datacenter Edition | 3.1 | 9.1 TS1M3 SP4 | ||||
Microsoft Windows Server 2003 Enterprise Edition | 3.1 | 9.1 TS1M3 SP4 | ||||
Microsoft Windows Server 2003 Standard Edition | 3.1 | 9.1 TS1M3 SP4 | ||||
Microsoft Windows XP Professional | 3.1 | 9.1 TS1M3 SP4 | ||||
Windows Vista | 3.1 | 9.1 TS1M3 SP4 |