Thanks for giving it a try & sorry for the bad first experience. Studio makes use of PROC STP to run the stored process so when you have a stored process that has syntax PROC STP can't handle, it will fail. Some of the sample stored processes have syntax in the SAS code that was written for the stored process server instead - for example, some samples were written to be output to a browser or have hooks that are recognized by the STP Web App and other clients. The PROC STP environment doesn’t know about those hooks and so the stored process will fail. Here's a list the stored process testing folks made of the common samples and their status:
Macro Variable Properties – works
Multiple Output Formats – works
Frequency Analysis – works
Cholesterol by Sex and Age – works
Shoe Sales By Region – fails because replay is not supported. However if you remove the href references then the code works fine.
Year to date budget – fails because no access to preassigned library
Shoe Sales Graphics – fails, it doesn’t handle STREAMCONTENTS
Hello World – fails because it does not produce ODSDOC output. Editing the proc stp code to handle _webout allows this to work.
European Demographic Data – fails, no access to preassigned library
European Demographic Data Detail – fails, no access to preassigned library
If you're game to keep trying, we're still looking for what functionality you commonly use in stored processes that you'd want to see working in Studio. We won't be able to completely recreate this wheel, but we want to get in as much commonly used functionality as we can before this can be marked production.
And to answser your earlier question, there's no other experimental functionality hiding out there (so far).
... View more