@ChrisHemedinger, ah, of course, the log files.     I suspect the problem arises from the fact that I had a prior version of SEG (4.3) on my machine in SASHome.  When I installed SEG 7.1, I noticed that the installation went into SASHome2.  I'm imagining that there is some dll that is not being accessed because it's in a different SAShome, although that's just a guess.  Your suspicion that EG is having trouble writing out preferences of some type may be well founded.     Thanks, and I'll post an update here when I have further information (and hopfully report that I have a solution).   Jim ... View more

Unfortunately, the problem hasn't gone away, at least not entirely.  I'm still getting "Object reference not set to an instance of an object" when I close SEG 7.1 after having worked on a project.  Everything else appears to be functional.  A minor nuisance at this point (unless I lose more work), but if anyone had a suggestion as to how to debug the problem, I would be most obliged.   Jim ... View more

Well, I haven't completely tested this yet, but I applied the hot fixes and upgrades for SEG 7.12, and... I've stopped getting the "Object reference not set to an instance of an object" errors that I was getting.  If so, best and most timely upgrade ever.  I should be able to confirm tomorrow.   Jim ... View more

Excellent.  Glad it worked.   Jim   ... View more

Here's a sample of one of the macros I've written.  I won't claim that it's pretty, but it works.  You can comment out a lot of the "PUT" statements that write to the log.  Sometimes I use them; sometimes I don't depending on whether I'm doing test or prod work.   /*-------------------------------------------------------------------------------------------------*/ /* Macro: Check_SYSERR /* Author: Jim Barbour /* Date: 19 January 2016 /* Run Time: Under 1 minute. /* Remarks: This macro checks macro variable SYSERR and sets global macro variable ReturnCode to 8 /* and aborts the run if SYSERR is non-zero. /* /* ReturnCode values are as follows: /* ReturnCode = 00 -- No errors or warnings. /* ReturnCode = 02 -- Note (less than an error or warning). /* ReturnCode = 04 -- Warning (less than an error). /* ReturnCode = 08 -- Error. /*-------------------------------------------------------------------------------------------------*/ %MACRO Check_SYSERR / STORE; ; RUN; QUIT; %IF &Control_Value = CANCEL %THEN %DO; %LET ReturnCode = 8; %END; %ELSE %DO; %PUT NOTE- ; %PUT NOTE: Check_SYSERR; %*PUT NOTE- ReturnCode = &ReturnCode; %PUT NOTE- SYSERR = &SYSERR; %PUT NOTE- SYSFILRC = &SYSFILRC; %PUT NOTE- SYSLIBRC = &SYSLIBRC; %IF &SYSERR ^= 0 %THEN %DO; %LET ReturnCode = 8; %PUT NOTE- ; %PUT WARNING: Cancelling run due to high error code; %ABORT CANCEL; /* ABORT CANCEL is not supported in SAS Enterprise Guide 4.3 and prior. */ %LET Control_Value = CANCEL; %END; %END; %MEND Check_SYSERR; /* Sample code: %LET Control_Value = ; %LET ReturnCode = 0; and %INCLUDE "/home/barbourj/macros/Check_SYSERR.sas"; %Check_SYSERR; */ The ReturnCode and Control_Value variables are something that I use to pass values between programs in SAS EG; you probably can omit them.   The %INCLUDE example is not needed if you use the / STORE option and create a compiled macro.   Jim ... View more

What version of SAS EG are you running?  If you're running 5.1 or later, I find that issuing an ABORT CANCEL command works really well any time an error is detected.  If you're running 4.3 or earlier, don't use the ABORT CANCEL; it will hang your SAS EG session, and you'll have to kill the session.   What I typically do is write a little macro and then execute that macro after I do a step.  The macro checks &SYSERR, &SYSFILERC, &SQLRC, &SQLXRC, or &SYSLIBRC as appropriate.  If an error is detected, I issue %ABORT CANCEL in my macro, and all subsequent steps in that program are cancelled.   Jim ... View more

Ah.  I see what you're saying.  I didn't pay attention to the way in which the macro was being invoked.  Hmm.  Yeah, that doesn't seem quite right...  I'll have to play with that a bit more on my 9.4 at home this evening if I get a chance.   Jim ... View more

The result that @data_null__ got doesn't surprise me.  My results, if you look at the below log snippet, were identical. NOTE: Entering macro. x=GlobalValue I wouild think the "work around" if you want to call it that, would be simply to code the following inside the Macro, yes? %LOCAL x; Jim ... View more

OK, here's the code I think you mean.  There aren't any time stamps displayed at least in my view of communities.sas.com.     OPTIONS noSYMBOLGEN noSOURCE noSOURCE2; %macro TestDoSubl; %local rc; %PUT NOTE: Entering macro. x=&x; %put _user_; %PUT NOTE- ; %PUT NOTE- ; %LET x=DynamicValue; %put NOTE: Before Dosubl 1: x=&x; %put _user_; %put; data _null_; rc=dosubl(""); run; %put NOTE: After Dosubl 1: x=&x; %put _user_; %PUT NOTE- ; %PUT NOTE- ; %LET x=NewDynamicValue; %put NOTE: Before Dosubl 2: x=&x; %put _user_; %PUT NOTE- ; data _null_; rc=dosubl(""); run; %put NOTE: After Dosubl 2: x=&x; %put _user_; %PUT NOTE- ; %PUT NOTE- ; %put NOTE: Before Dosubl 3: x=&x; %put _user_; data _null_; rc=dosubl(""); run; %put NOTE: After Dosubl 3: x=&x; %put _user_; %PUT NOTE- ; %PUT NOTE- ; %mend TestDoSubl; %PUT NOTE- ; %PUT NOTE- ; %PUT NOTE: __________________________________________________________________________________________________; %let x=GlobalValue; %PUT NOTE: Before TestDoSubl macro. x=&x; %PUT NOTE- &=SYSVLONG4; DATA _NULL_; rc=DOSUBL('%TestDoSubl;'); RUN; %PUT NOTE: After TestDoSubl macro. x=&x; %PUT NOTE: __________________________________________________________________________________________________; %PUT NOTE- ; %PUT NOTE- ; I've modified the code slightly because SAS web studio is freaking verbose.  The big ______________ lines help separate out all the background noise that SAS web studio puts into the log.     And here's the output.  Everything is as I would expect.  In other words, I think that they have in fact fixed the bugs that were in 9.3 M2. NOTE: __________________________________________________________________________________________________ NOTE: Before TestDoSubl macro. x=GlobalValue SYSVLONG4=9.04.01M3P06242015 NOTE: Entering macro. x=GlobalValue TESTDOSUBL RC GLOBAL GRAPHINIT GLOBAL GRAPHTERM GLOBAL OLDPREFS /folders/myfolders/.wepreferences GLOBAL OLDSNIPPETS /folders/myfolders/.mysnippets GLOBAL OLDTASKS /folders/myfolders/.mytasks GLOBAL RETURNCODE 0 GLOBAL STUDIODIR /folders/myfolders/.sasstudio GLOBAL STUDIODIRNAME .sasstudio GLOBAL STUDIOPARENTDIR /folders/myfolders GLOBAL USERDIR /folders/myfolders GLOBAL X GlobalValue GLOBAL _BASEURL http:192.168.142.128SASStudio GLOBAL _CLIENTAPP SAS Studio GLOBAL _CLIENTAPPVERSION 3.4 GLOBAL _EXECENV SASStudio GLOBAL _SASPROGRAMFILE foldersmyfoldersSAS_CodeDOSUBL_Test_Program3.sas GLOBAL _SASWSTEMP_ foldersmyfolders.imagesaf7d42bf86784eacbcd1746bb34e87c0 GLOBAL _SASWS_ foldersmyfolders NOTE: Before Dosubl 1: x=DynamicValue TESTDOSUBL RC GLOBAL GRAPHINIT GLOBAL GRAPHTERM GLOBAL OLDPREFS /folders/myfolders/.wepreferences GLOBAL OLDSNIPPETS /folders/myfolders/.mysnippets GLOBAL OLDTASKS /folders/myfolders/.mytasks GLOBAL RETURNCODE 0 GLOBAL STUDIODIR /folders/myfolders/.sasstudio GLOBAL STUDIODIRNAME .sasstudio GLOBAL STUDIOPARENTDIR /folders/myfolders GLOBAL USERDIR /folders/myfolders GLOBAL X DynamicValue GLOBAL _BASEURL http:192.168.142.128SASStudio GLOBAL _CLIENTAPP SAS Studio GLOBAL _CLIENTAPPVERSION 3.4 GLOBAL _EXECENV SASStudio GLOBAL _SASPROGRAMFILE foldersmyfoldersSAS_CodeDOSUBL_Test_Program3.sas GLOBAL _SASWSTEMP_ foldersmyfolders.imagesaf7d42bf86784eacbcd1746bb34e87c0 GLOBAL _SASWS_ foldersmyfolders NOTE: DATA statement used (Total process time): real time 0.02 seconds cpu time 0.01 seconds NOTE: After Dosubl 1: x=DynamicValue TESTDOSUBL RC GLOBAL GRAPHINIT GLOBAL GRAPHTERM GLOBAL OLDPREFS /folders/myfolders/.wepreferences GLOBAL OLDSNIPPETS /folders/myfolders/.mysnippets GLOBAL OLDTASKS /folders/myfolders/.mytasks GLOBAL RETURNCODE 0 GLOBAL STUDIODIR /folders/myfolders/.sasstudio GLOBAL STUDIODIRNAME .sasstudio GLOBAL STUDIOPARENTDIR /folders/myfolders GLOBAL USERDIR /folders/myfolders GLOBAL X DynamicValue GLOBAL _BASEURL http:192.168.142.128SASStudio GLOBAL _CLIENTAPP SAS Studio GLOBAL _CLIENTAPPVERSION 3.4 GLOBAL _EXECENV SASStudio GLOBAL _SASPROGRAMFILE foldersmyfoldersSAS_CodeDOSUBL_Test_Program3.sas GLOBAL _SASWSTEMP_ foldersmyfolders.imagesaf7d42bf86784eacbcd1746bb34e87c0 GLOBAL _SASWS_ foldersmyfolders NOTE: Before Dosubl 2: x=NewDynamicValue TESTDOSUBL RC GLOBAL GRAPHINIT GLOBAL GRAPHTERM GLOBAL OLDPREFS /folders/myfolders/.wepreferences GLOBAL OLDSNIPPETS /folders/myfolders/.mysnippets GLOBAL OLDTASKS /folders/myfolders/.mytasks GLOBAL RETURNCODE 0 GLOBAL STUDIODIR /folders/myfolders/.sasstudio GLOBAL STUDIODIRNAME .sasstudio GLOBAL STUDIOPARENTDIR /folders/myfolders GLOBAL USERDIR /folders/myfolders GLOBAL X NewDynamicValue GLOBAL _BASEURL http:192.168.142.128SASStudio GLOBAL _CLIENTAPP SAS Studio GLOBAL _CLIENTAPPVERSION 3.4 GLOBAL _EXECENV SASStudio GLOBAL _SASPROGRAMFILE foldersmyfoldersSAS_CodeDOSUBL_Test_Program3.sas GLOBAL _SASWSTEMP_ foldersmyfolders.imagesaf7d42bf86784eacbcd1746bb34e87c0 GLOBAL _SASWS_ foldersmyfolders NOTE: DATA statement used (Total process time): real time 0.02 seconds cpu time 0.02 seconds NOTE: After Dosubl 2: x=NewDynamicValue TESTDOSUBL RC GLOBAL GRAPHINIT GLOBAL GRAPHTERM GLOBAL OLDPREFS /folders/myfolders/.wepreferences GLOBAL OLDSNIPPETS /folders/myfolders/.mysnippets GLOBAL OLDTASKS /folders/myfolders/.mytasks GLOBAL RETURNCODE 0 GLOBAL STUDIODIR /folders/myfolders/.sasstudio GLOBAL STUDIODIRNAME .sasstudio GLOBAL STUDIOPARENTDIR /folders/myfolders GLOBAL USERDIR /folders/myfolders GLOBAL X NewDynamicValue GLOBAL _BASEURL http:192.168.142.128SASStudio GLOBAL _CLIENTAPP SAS Studio GLOBAL _CLIENTAPPVERSION 3.4 GLOBAL _EXECENV SASStudio GLOBAL _SASPROGRAMFILE foldersmyfoldersSAS_CodeDOSUBL_Test_Program3.sas GLOBAL _SASWSTEMP_ foldersmyfolders.imagesaf7d42bf86784eacbcd1746bb34e87c0 GLOBAL _SASWS_ foldersmyfolders NOTE: Before Dosubl 3: x=NewDynamicValue TESTDOSUBL RC GLOBAL GRAPHINIT GLOBAL GRAPHTERM GLOBAL OLDPREFS /folders/myfolders/.wepreferences GLOBAL OLDSNIPPETS /folders/myfolders/.mysnippets GLOBAL OLDTASKS /folders/myfolders/.mytasks GLOBAL RETURNCODE 0 GLOBAL STUDIODIR /folders/myfolders/.sasstudio GLOBAL STUDIODIRNAME .sasstudio GLOBAL STUDIOPARENTDIR /folders/myfolders GLOBAL USERDIR /folders/myfolders GLOBAL X NewDynamicValue GLOBAL _BASEURL http:192.168.142.128SASStudio GLOBAL _CLIENTAPP SAS Studio GLOBAL _CLIENTAPPVERSION 3.4 GLOBAL _EXECENV SASStudio GLOBAL _SASPROGRAMFILE foldersmyfoldersSAS_CodeDOSUBL_Test_Program3.sas GLOBAL _SASWSTEMP_ foldersmyfolders.imagesaf7d42bf86784eacbcd1746bb34e87c0 GLOBAL _SASWS_ foldersmyfolders NOTE: DATA statement used (Total process time): real time 0.01 seconds cpu time 0.01 seconds NOTE: After Dosubl 3: x=NewDynamicValue TESTDOSUBL RC GLOBAL GRAPHINIT GLOBAL GRAPHTERM GLOBAL OLDPREFS /folders/myfolders/.wepreferences GLOBAL OLDSNIPPETS /folders/myfolders/.mysnippets GLOBAL OLDTASKS /folders/myfolders/.mytasks GLOBAL RETURNCODE 0 GLOBAL STUDIODIR /folders/myfolders/.sasstudio GLOBAL STUDIODIRNAME .sasstudio GLOBAL STUDIOPARENTDIR /folders/myfolders GLOBAL USERDIR /folders/myfolders GLOBAL X NewDynamicValue GLOBAL _BASEURL http:192.168.142.128SASStudio GLOBAL _CLIENTAPP SAS Studio GLOBAL _CLIENTAPPVERSION 3.4 GLOBAL _EXECENV SASStudio GLOBAL _SASPROGRAMFILE foldersmyfoldersSAS_CodeDOSUBL_Test_Program3.sas GLOBAL _SASWSTEMP_ foldersmyfolders.imagesaf7d42bf86784eacbcd1746bb34e87c0 GLOBAL _SASWS_ foldersmyfolders NOTE: DATA statement used (Total process time): real time 0.20 seconds cpu time 0.09 seconds NOTE: After TestDoSubl macro. x=NewDynamicValue NOTE: _________________________________________________________________________________________________ Jim ... View more

I just ran my code at home where I'm running SAS 9.4 M3.  Everything works fine. Everything also worked fine with SAS 9.3 M1 on my PC at work.  It's only on my work AIX machine running SAS 9.3 M2 that I'm seeing the problem.   It seems pretty clear this is a bug, perhaps limited only to SAS 9.3 M2. NOTE: Starting primary execution. The value of Debug=* SYSVLONG4=9.04.01M3P06242015 NOTE: The value of Debug before invoking macro, Debug=* NOTE: The value of Debug before the 1st Data step= NOTE: Executing 1st Debug Logic NOTE: Executing 1st Regular Logic NOTE: The value of Debug inside the 1st Data step= NOTE: DATA statement used (Total process time): real time 0.03 seconds cpu time 0.03 seconds NOTE: The value of Debug after the 1st Data step= NOTE: The value of Debug before the 2nd Data step=* NOTE: Executing 2nd Regular Logic NOTE: The value of Debug inside the 2nd Data step=* NOTE: DATA statement used (Total process time): real time 0.05 seconds cpu time 0.02 seconds NOTE: The value of Debug after the 2nd Data step=* NOTE: The value of Debug before the 3rd Data step=* NOTE: Executing 3rd Regular Logic NOTE: The value of Debug inside the 3rd Data step=* NOTE: DATA statement used (Total process time): real time 0.01 seconds cpu time 0.01 seconds NOTE: The value of Debug after the 3rd Data step=* NOTE: The value of Debug after invoking macro, Debug=* NOTE: DATA statement used (Total process time): real time 0.18 seconds cpu time 0.08 seconds NOTE: Ending primary execution. The value of Debug=* NOTE: __________________________________________________________________________________________________   For production work, I think I'd probably stay away from DOSUBL on SAS 9.3 and only use DOSUBL with SAS 9.4. 9.4 M3 is clearly working.  I don't know about earlier versions of 9.4 though.   Jim ... View more