Blogs

Blogs

Editing .sas source code repository from 9.3 SAS Management Console

2
By

As I have previously mentioned, SAS 9.3 has some sweet new functionality for stored processes. The topic of the prior post was on storing .sas code for the stored process directly within the metadata and how to edit/access that raw code. Did you know that the 'Edit Source Code' button will also work for .sas files stored out on the physical server?

Seen below, I have a stored process called 'Web Upload' with a .sas file located in c:\sas\stps93\Excel Import Process.sas. I could open this file in SAS or any text editor but if I need to make a super quick modification I could simply select this one button.

I would think using this functionality is useful for quick modifications. But this is also a much more user friendly mechanism for organizations that do not use Enterprise Guide to open remote .sas files on a server and need to FTP the file back and forth to make changes.

Important Note: The file system security is not bypassed using this functionality. On my local install I was asked to authenticate to the server because the account I was logged into SAS Management Console with (internal administrator sasadm@saspw) did not have file level access.

Tags business intelligence Management Console Stored Processes
Share

About Author

Angela Hall

Senior Technical Architect

Angela offers tips on using the SAS Business Intelligence solutions. She manages a team of SAS Fraud Framework implementers within the SAS Solutions On-Demand organization. Angela also has co-written two books, 'Building BI using SAS, Content Development Examples' & 'The 50 Keys to Learning SAS Stored Processes'.

2 Comments

  1. Jennifer Parks on

    I'm glad these features are in SAS Mgt Console but is there a way to prevent DI Studio Users from managing (ie. creating/deleting) source repository definitions in the metadata but still preserve their ability to create new stored processes and associate them with existing repositories?

  2. Don Henderson on

    Angela, I was also quite pleased to see this addition. And presumably it does not have the problem that EG does where EG will prepend/append code to stored process source files that were not initially created with EG and thus do not include the EG auto-generated prepend/append code. I know that there is an option to turn that off, but it is very easy to forget to set that if you are just trying to browse.

Back to Top