There is some sweet new functionality in 9.3 stored processes. One of them I particularly like is the additional option to store the SAS code within the metadata rather than in a separate .sas file. This is extremely beneficial when allowing the stored process to run on multiple application servers. It also could be useful for production environments where the code can be completely locked by the metadata and is not dependent on file system access and security levels.

Within the Execution tab (for existing stored processes) or the Execution screen (available through the create new stored process wizard),  select 'Store source code in metadata' and click the 'Edit Source Code' button to open a program editor screen to include your stored process code. (I have highlighted these options in the screen capture.)

However in development mode, I would recommend that you continue to use the .sas file and the source code repository. Why? Like most metadata it takes a refresh for any changes to be viewed. In stored processes it's no different. As I was developing some of my first 9.3 stored processes using this functionality last week, I noticed that refreshing the web browser was just not enough to pick up the source code modifications. I needed to move back to the list of stored processes and choose the stored process again. For single stored processes with limited prompting, this is simple. But for complex stored processes used in web development or with multiple prompts (and no defaults) - going back through the execution screen could take extra development time.