If you are using the SAS Stored Process Web Application in a release prior to 9.1.3 SP4, then you may be experiencing this problem: SN-V9-017477: Variable name instead of Parameter label appears in Parameters page when executing a Stored Process from a Web client http://support.sas.com/techsup/unotes/SN/017/017477.html Using the workaround listed in this document or upgrading to 9.1.3 SP4 should fix the problem. If you continue to have difficulties, you can open a track with our Technical Support department: http://support.sas.com/ctx/supportform/index.jsp Vince DelGobbo SAS R&D ... View more

Currently you can hide some, but not all of these items by adding input parameters with names that correspond to the items. For example, the input parameter named "_ODSDEST" corresponds to item labeled "Output type". Here is a list of the things you can hide, and the properties of the input parameters you need to add in order to hide them: To hide the "Output type" item: Label: SAS variable name: _ODSDEST Visible: No Type: String Default value: To hide the "ODS style" item: Label: SAS variable name: _ODSSTYLE Visible: No Type: String Default value: To hide the "Graphics device" item: Label: SAS variable name: _GOPT_DEVICE Visible: No Type: String Default value: To hide the "Show SAS Log", "Show execution time", and "Show execution trace" items: Label: SAS variable name: _DEBUG Visible: No Type: String Default value: This must be done for each individual stored process. We hope to have better support for customization in a future release. Vince DelGobbo SAS R&D ... View more

It is still difficult to diagnose what is happening without seeing more code. I suggest that you contact our Technical Support department so they can walk through the process with you. You can open a track online at: http://support.sas.com/ctx/supportform/index.jsp Vince DelGobbo SAS R&D ... View more

You can use the SAS Stored Process Web Application to dynamically create a property page based on the parameter metadata. The documentation is located at: http://support.sas.com/rnd/itech/doc9/dev_guide/stprocess/stpwebapp.html Vince DelGobbo SAS R&D ... View more

When you see this message, are you using the SAS Add-in for Microsoft Office? If so, you may want to post this question in the "Integration with Microsoft® Office" forum at: http://support.sas.com/forums/forum.jspa?forumID=7&start=0 This problem may be fixed in a newer version of the add-in. A possible workaround is to set the maximum number of selections as a constraint. Vince DelGobbo SAS R&D ... View more

I ran a similar request to this server, and SAS reported that it took 1.06 seconds of real time. The problem may be network-related at your site. Vince DelGobbo SAS R&D ... View more

SAS Institute does not have a forum for general SAS questions. If you would like to make suggestions for new forums, please send your comments to suggest@sas.com There is a mailing list called "SAS-L" that is run by SAS customers. It is not affiliated in any way with SAS Institute. You can find out more about SAS-L at: http://www.listserv.uga.edu/archives/sas-l.html Best regards, Vince DelGobbo SAS R&D ... View more

Karen- Could you please repost this question in the "Integration with Microsoft® Office" forum? Someone there will be better suited to answering your question. The link is: http://support.sas.com/forums/forum.jspa?forumID=7&start=0 Another, perhaps better option, is to open a track with our Technical Support department: http://support.sas.com/techsup/contact/submit_emits2.html One quick thought that I have is perhaps you do not have operating system permission to access the directory "C:\Documents and Settings\dbisbik\My Documents\My SAS Files\9.1". Best regards, Vince DelGobbo SAS R&D ... View more

Diagnosing authentication errors can be very difficult. You can try defining a parameter named _DEBUG, set the value to "trace,log" (no quotes) and rerun the stored process to see if that gives you any further information. I suggest that you open a track with our Technical Support department, who can assist you in getting a solution: http://support.sas.com/techsup/contact/submit_emits2.html Vince DelGobbo SAS R&D ... View more

If you wrote code in SAS version 8 to execute stored processes, than you should be able to reuse that code in SAS 9. The link to the SAS version 8 style stored processes is here: http://support.sas.com/rnd/itech/doc9/dev_guide/app/index.html Vince DelGobbo SAS R&D ... View more

I have been told that in SAS 9.2, SAS Data Integration Studio will support Web Services. I do not know exactly what level of support it will have. Given the complexity of this issue, you will probably be better served by opening a track with our Technical Support department: http://support.sas.com/techsup/contact/submit_emits2.html Best regards, Vince DelGobbo SAS R&D ... View more

Can you post a code snippet that illustrates the problem you are having? Thanks. Vince DelGobbo SAS R&D ... View more

I do not know all of the details, but the idea is that in SAS 9.2, we will have the ability to surface dynamic and cascading prompts. By "dynamic", I mean that the values will be automatically populated at run time, possibly from metadata and/or SAS tables, stored processes, etc. "Cascading" means that the selection in one prompt affects, or cascades to, another prompt. A typical example showing both of these features would be a variable selector. First, a "library" prompt is dynamically populated with a list of available SAS libraries. Once you choose a library, a "table" prompt is updated to display the list of tables in the library. Finally, once a table is chosen, a "variable" prompt displays the variables in the given table. It is a work in progress so what I said above may not be exactly correct. Vince DelGobbo SAS R&D ... View more

The preferred way to control the behavior of the STPBEGIN/STPEND macros is by use of input parameters, not by hard coding values with a %LET statement. For example, if you want to control the ODS style that is used, register a parameter named _ODSSTYLE and give it a default value. At run-time, users will be able to specify the value they want to use. If you don't want the user to change the value at run-time, clear the "Modifiable" and "Visible" check boxes for this parameter. A list of parameter names can be found at: http://support.sas.com/rnd/itech/doc9/dev_guide/stprocess/reserved.html Parameters that are specific to the STPBEGIN/STPEND macros will have "%STPBEGIN/%STPEND" in the "Used by" column. Vince DelGobbo SAS R&D ... View more

schering- In SAS 9.2 we plan to have a better solution to dynamic prompting. In the mean time, our Technical Support department can provide you with some sample code that will help with your project. You will need to go to this Web site and open a support track: http://support.sas.com/techsup/contact/submit_emits2.html In the Product field, select "SAS Integration Technologies" and for the Subject field, specify "Need stored process STPDefineParameter macro". This will insure that the track gets routed to the people that can help you. There are a couple of caveats: this is sample code, and it will NOT work in SAS 9.2, as we are making sweeping changes to the parameter model. Yet it may be useful for you now. One way I envision you using this as follows: * Run a SAS job to extract Oracle data into a SAS table. This table contains the constraints for the parameter. * Run the STPDefineParameter macro, passing in the SAS table and any other required parameters (stored process name, parameter name, etc.). This method is useful if your data does not change often. Good luck. Vince DelGobbo SAS R&D ... View more