BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
THALLA_REDDY
Obsidian | Level 7

Hi Team,

I have created a stored process in my SAS Enterprise Guide 8.3 and saved it under Shared Data Folder. I have created some prompts in the Stored process for getting some inputs when running the PROJECT. Unfortunately the Stored Process is taking the Inputs from the programmer but those macro variables are not getting resolved in the other objects like a program. Is that something I am missing with the stored process creation to get these macro variables created by Stored process to be used in entire PROJECT Process Flow ?

 

thanks in advance,

Thalla

1 ACCEPTED SOLUTION

Accepted Solutions
Kurt_Bremser
Super User

A stored process is executed in a completely different context than your other project nodes. A stored process is executed in a stored process server instance, which runs on a generic userid (sassrv), and the environment there is cleaned up immediately after the STP has finished. Your Enterprise guide can only access macro variables defined in your workspace server, which runs on your userid and is persistent for the EG session (unless you terminate it yourself).

You can attach a user prompt to a code node, set macro variables from the prompt values in that code, and use those macro variables in conditions for the next nodes.

View solution in original post

1 REPLY 1
Kurt_Bremser
Super User

A stored process is executed in a completely different context than your other project nodes. A stored process is executed in a stored process server instance, which runs on a generic userid (sassrv), and the environment there is cleaned up immediately after the STP has finished. Your Enterprise guide can only access macro variables defined in your workspace server, which runs on your userid and is persistent for the EG session (unless you terminate it yourself).

You can attach a user prompt to a code node, set macro variables from the prompt values in that code, and use those macro variables in conditions for the next nodes.

hackathon24-white-horiz.png

The 2025 SAS Hackathon Kicks Off on June 11!

Watch the live Hackathon Kickoff to get all the essential information about the SAS Hackathon—including how to join, how to participate, and expert tips for success.

YouTube LinkedIn

Creating Custom Steps in SAS Studio

Check out this tutorial series to learn how to build your own steps in SAS Studio.

Find more tutorials on the SAS Users YouTube channel.

SAS Training: Just a Click Away

 Ready to level-up your skills? Choose your own adventure.

Browse our catalog!

Discussion stats
  • 1 reply
  • 742 views
  • 0 likes
  • 2 in conversation