Apparent symbolic reference not resolved for globals between programs in a Process Flow

JohnJPS — Wed, 06 Sep 2017 21:13:51 GMT

I've recreated the issue as simply as I can... in Enterprise Guide, I have a very simple process with two programs.

ProgramA:

%global TestDTE;
%let TestDTE = %sysfunc(putn(%sysfunc(TODAY()),yymmdd10.));
run;
%put _GLOBAL_;
run;

ProgramB:

%put _GLOBAL_;
run;
proc sql;
  connect to SQLSVR(dsn='testdsn');
  create table work.jpstemp as
  select * from connection to SQLSVR
(
  SELECT dt1 = %str(%')&TestDTE%str(%');
);
run;

So, just creating a simple global variable in ProgramA, which is linked into ProgramB. ProgramB then wants to consume the variable.

Before ProgramA is finished, I put all globals, which has among other things:

GLOBAL TESTDTE 2017-09-06

But in ProgramB, the first thing I do is put all globals again, and it is no longer there... which leads to the "symbolic reference not resolved" warning in ProgramB's sample SQL statement.

My understanding is that globals should remain for the duration of my EG session, and when running a ProcessFlow, they should remain over the course of the entire process. Is that an incorrect assumption, or can this be fixed up somehow?

Re: Apparent symbolic reference not resolved for globals between programs in a Process Flow

JohnJPS — Wed, 06 Sep 2017 21:43:47 GMT

Kind of embarassing, but I figured it out: the two programs were somehow targeting different workspace servers.

Once both were on the same server, all was well.

topic Apparent symbolic reference not resolved for globals between programs in a Process Flow in SAS Programming

Apparent symbolic reference not resolved for globals between programs in a Process Flow

Re: Apparent symbolic reference not resolved for globals between programs in a Process Flow