Thanks for that! What I found out (offline) is that the actual path limit is 256 chars, so we think that there was something else going one for #2 for our folks with the question. I have heard from a few folks off-line on #1 and the answer is really that the stored processes are not meant to replace whatever existing batch processes you have in place to update files and/or create tables. In Web Report Studio, you CAN schedule a report to update however, and WRS report CAN contain stored processes. But the bottom line is not to think you need to replace all of your existing batch processes with stored processes. cynthia ... View more

If you are dead-set against formats, you could try this for the parameter definition: Prompt: Please select a country SAS Variable Name: COUNTRY Display as: Resolves to: United States US:United States Italy IT:Italy Ireland EI:Ireland Instead of using COUNTRY directly in your SAS code, use these variables: %let RETURN_VALUE = %scan(&COUNTRY, 1, :); %let DISPLAY_VALUE = %scan(&COUNTRY, 2, :); It's not very elegant, but it should work. Vince SAS R&D ... View more

If the 'master document' remains the same across different runs you could create the tables in separate files and then create that master with MS Word and insert the files as links. The master document (or copies of it) can then be edited, but the tables cannot. If needed it should also be possible to create such a master with SAS and ODS, but that would require you insert the links to the files as raw RTF. A look in such a document created with Word and saved as RTF would give a fairly good idea of that RTF should look like. ... View more

From my experience one must unprotect the document in order for the AMO results to be surfaced. I protect the section returned from AMO but must unprotect the entire document to allow another stored process to complete. ... View more

Tim- It was good seeing you at HASUG. With regard to reusable prompts, what we mean is that you can define a prompt and, well, reuse it in any of your stored process definitions. For example, suppose you always want to restrict users to a few ODS styles. You can define an "ODS Style" prompt, enter the few valid styles and save it. Whenever you make a stored process, you can simply include, or "reuse" this prompt, instead of having to define it from scratch in each stored process. Your question regarding Enterprise Guide seems to be a question of maintaining "state". I don't know whether or not that is possible with EG, but in streaming stored processes, you can do it via SAS sessions. In EG you can try to maintain state by writing the information to permanent SAS table or flat file, but there might be better ways. I suggest you pose the question in the Enterprise Guide forum, if you have not already done so: http://support.sas.com/forums/forum.jspa?forumID=10&start=0 Vince SAS R&D ... View more