Yes, please post all the ODS statements that you are using.   What changed on the server and/or SAS?  Is the server Windows or UNIX?  What is the version of SAS?   Vince DelGobbo SAS R&D ... View more

Hi Charlie,   I am seeing the same error - SAS completed with non-zero SYSCC '3,000'.  SYSMSG: ''.   If you troubleshooted this error, please help me with the troubleshooting steps. ... View more

Quentin This is a way I found after looking through lots of info on it through the internet. I use the session headers to return a dataset from a permanent library. The dataset is created from another SP that is run before this one: The template is used to keep quotes out of the file. You can run this SP through a browser with a url like: http://yourSPserver:8080/SASStoredProcess/do?_program=%2FShared+Data%2FYourFolder%2FExportQCResults Charlie ... View more

When I changed the sp execution options to only run on the workspace server it will return the package to the web browser. I think this may be the way to go. all you have to do is click the items on the left and they open in their respective program Does anybody know if there's a way to get rid of that header and replace it with your won? ... View more

Glad that modifying the tagset worked.  Thank's for posting the code.  SAS-L is a great resource. ... View more

Hi:   if you used ODS PATH (PREPEND) to WRITE your template to the COMMON.TEMPLAT item store and if your libref COMMON is in a location known to the Stored Process Server and Workspace server (an important IF -- but the name COMMON implies that your SAS Admin has done something nice for you). And, if (another important IF) the servers all have an ODS PATH that points to COMMON, then the act of putting your override -before- %STPBEGIN is enough to override the default style that is set in     %STPBEGIN. For example, in SAS 9.3, the default style for PDF is STYLES.PRINTER -- if you used %let _odsstyle=journal; %let _odsdest=pdf; %stpbegin; in your stored process, then SAS and ODS would know that you meant to override the default destination to PDF; and the style for PDF is usually STYLES.PRINTER, except you also want to override that style with STYLES.JOURNAL. Now, STYLES.JOURNAL is a SAS-supplied template. It will be found in SASHELP.TMPLMST item store -- so there is no need for the ODS PATH to change in order to use the JOURNAL style, because the SASHELP item stores is ALWAYS known to SAS. But, if you have a user defined style (such as yours) and IF you have put it in the right location (which it seems you have) and IF the servers all have a pointer to that location (I can't answer this question for you), then your style in the %LET will override whatever style would normally be set by default in %STPBEGIN macro call. You could add code to your stored process to reveal the current PATH in the log: ODS PATH SHOW; and then you'd know for sure whether COMMON was being used. As I said before, this method of specifying a style for a stored process (which you showed in your original post) ods html style=wivisp_SASstyle; is highly unusual and would not work if you had something like this (especially where the %STPBEGIN was added by EG BEFORE the ODS HTML statement): %stpbegin; ods html style=wivisp_SASstyle; In the above scenario, %STPBEGIN would set the style and once set by %STPBEGIN, any attempt to change it is ignored by the destination for a stored process. The reserved macro variables, like _ODSSTYLE are the preferred way to modify default settings and those reserved macro variables are outlined in the link I posted. So, this is the preferred method: %let _odsstyle= wivisp_SASstyle; %stpbegin; but SAS and ODS will look through ALL the template stores in the ODS PATH search list until they find the style you've listed. If they find the style, they use the style. If they don't find the style, then they use the default for the destination. The only gotcha is that a client application like Web Report Studio might still NOT use your style because styles for WRS are stored in a special configuration file on the web server level or tier. I'd recommend that you have your SAS Admin open a track with Tech Support or that you open a track with Tech Support. If changes to the configuration files need to be made so the style is available to everyone, your Admin person may need to be the one to change the files. cynthia ... View more

http://support.sas.com/rnd/itech/doc9/dev_guide/websrvcs/sample.html ... View more

It sounds like you want to have a display name and an actual value for each item in the list. You cannot do this in the query builder with project parameters, but it is supported when you create a stored process. In our next release, this is supported with the new project prompts. Chris ... View more

Charlie, two remarks -read sas documentation before asking a trivial question see a solution WITH gpath= ods listing close; ods html body = 'C:\Temp\Body.html' gpath="c:\temp" Contents = 'C:\Temp\Contents.html' Page = 'C:\Temp\Page.html' Frame = 'C:\Temp\Frame.html' Style = Analysis; proc gslide; title 'test of place of gif'; run; quit; ods html close; ods listing; -you are referring to a program without showing any lines or resume nor the setted sasuser,saswork and current folder adresses and your question has as subject this matter! Sas tech support can help on it but i don't think this forum, which purpose is more general ods difficulties (not peculiar) and the same for sas basic questions. Cylthia may correct me if necessary. Andre (Paris) ... View more