topic Re: %SYSLPUT in a macro in SAS Programming

%SYSLPUT in a macro

Selcuk — Wed, 17 Oct 2012 14:58:03 GMT

I try to connect remote session via rsubmit and I need to pass a parameter to remote session using %syslput. But I have to do it in a macro.

So I have read a problem note in support SAS (http://support.sas.com/kb/47/072.html) , it recommends to use %nrstr expression. But when I use

%nrstr I get a message like

ERROR 180-322: Statement is not valid or it is used out of proper order.

macro >>>

%macro master_test(papa);

%put ########### Construction type is &papa ###########;

libname consdata '.....\CONSTRUCTION_DATA';

options autosignon=yes sascmd='sas -nosyntaxcheck -autoexec "C:\......\autoexec.sas"';

%NRSTR(%syslput _global_/like='papa' remote=EXTRCTN);

rsubmit process=EXTRCTN wait=yes persist=no;

options autosignon=yes notes sascmd='sas -nosyntaxcheck -autoexec "C:\........\autoexec_for_MASTER.sas"';

%let e_construction_type=&papa;

%NRSTR(%syslput _global_/like='e_construction_type' remote=EUSD);

rsubmit process=EUSD wait=no persist=no ;

data a;

a=45;

run;

endrsubmit;

waitfor _all_ EUSD;

endrsubmit;

%mend;

Best Regards

Re: %SYSLPUT in a macro

Quentin — Wed, 17 Oct 2012 17:25:44 GMT

Hi,

I haven't used SAS/Connect in many years, so these are mostly guesses.

If you take the code out of the macro, does it work? (I'm hoping the answer is no)

I noticed a line in the docs for %syslput:

"To use %SYSLPUT, you must have initiated a link between a local SAS session or client and a remote SAS session or server using the SIGNON command or SIGNON statement. For more information, see the documentation for SAS/CONNECT software."

I see you have the autosignon option, which is honored by the rsubmit statement. Maybe %syslput can't honor the autosignon, so it doesn't know there is a remote session to write to.

--Q.

Re: %SYSLPUT in a macro

Selcuk — Wed, 17 Oct 2012 17:46:32 GMT

Unfortunately it works out of the macro block

Re: %SYSLPUT in a macro

Quentin — Wed, 17 Oct 2012 18:06:56 GMT

Another wild guess would be to %unqoute it:

 %unquote(%NRSTR(%syslput _global_/like='papa' remote=EXTRCTN));

Re: %SYSLPUT in a macro

AhmedAl_Attar — Wed, 17 Oct 2012 18:19:33 GMT

Hi,

Please double check and look-up examples from either the on-line help, or the SAS/Connect User Guide.

You can use %SYSLPUT on it's own. You don't need to wrap it inside %NRSTR!

I have always used it like this

%syslput <remote macro variable name> = [some value | &<local macro variable name>] /remote=<Remote host Name>;

Hope this helps,

Ahmed

Re: %SYSLPUT in a macro

Tom — Wed, 17 Oct 2012 20:01:40 GMT

Where did you define the macro variable as GLOBAL? The first reference I see to e_construction_type is inside the macro definition.

Try this sample program.

%macro test;

%local mvar;

%let mvar=local value;

%syslput _global_ /like='mvar' ;

%mend test;

%let mvar=global value;

%test;

rsubmit;

%put mvar="&mvar";

endrsubmit;

Re: %SYSLPUT in a macro

Selcuk — Thu, 18 Oct 2012 06:57:38 GMT

Hi Quentin,

thanx for your reply , I hoped that your recommendation would be useful but it didn't... Below the code and you can see the error log on the bottom.

%macro master_test(papa);

options autosignon=yes sascmd='sas -nosyntaxcheck -autoexec "C:\....\autoexec_for_MASTER.sas"';

%unquote(%NRSTR(%syslput _global_/like='papa' remote=EXTRCTN));

rsubmit process=EXTRCTN wait=yes persist=no;

options autosignon=yes notes sascmd='sas -nosyntaxcheck -autoexec "C:\....\autoexec_for_MASTER.sas"';

%let e_construction_type=&papa;

%unquote(%NRSTR(%syslput _global_/like='e_construction_type' remote=EUSD));

rsubmit process=EUSD wait=no persist=no;

data a;

a=&e_construction_type;

run;

endrsubmit;

waitfor _all_ EUSD;

endrsubmit;

%mend;

NOTE: Remote signon to EXTRCTN commencing (SAS Release 9.03.01M1P110211).

NOTE: Unable to open SASUSER.PROFILE. WORK.PROFILE will be opened instead.

NOTE: All profile changes will be lost at the end of the session.

NOTE: SAS (r) Proprietary Software 9.3 (TS1M1)

Licensed to ############., Site ########.

NOTE: This session is executing on the X64_S08R2 platform.

NOTE: Updated analytical products:

SAS/STAT 9.3_M1

NOTE: SAS initialization used:

real time 0.09 seconds

cpu time 0.10 seconds

NOTE: AUTOEXEC processing beginning; file is C:\..........................\autoexec_for_MASTER.sas.

NOTE: PROCEDURE PRINTTO used (Total process time):

real time 0.00 seconds

cpu time 0.00 seconds

NOTE: AUTOEXEC processing completed.

NOTE: Remote signon to EXTRCTN complete.

NOTE: Remote submit to EXTRCTN commencing.

1 options autosignon=yes notes sascmd='sas -nosyntaxcheck -autoexec "C:\.................\autoexec_for_MASTER.sas"';

2 %unquote(%syslput _global_/like='e_construction_type' remote=EUSD);

ERROR: Unrecognized option to the %SYSLPUT statement.

3 rsubmit process=EUSD wait=no persist=no;

4 data a;

5 a=&e_construction_type;

WARNING: Apparent symbolic reference E_CONSTRUCTION_TYPE not resolved.

6 run;

7 endrsubmit;

8 waitfor _all_ EUSD;

NOTE: Remote submit to EXTRCTN complete.

NOTE: Remote signoff from EXTRCTN commencing.

NOTE: Remote signon to EUSD commencing (SAS Release 9.03.01M1P110211).

NOTE: Unable to open SASUSER.PROFILE. WORK.PROFILE will be opened instead.

NOTE: All profile changes will be lost at the end of the session.

NOTE: SAS (r) Proprietary Software 9.3 (TS1M1)

Licensed to #########, Site ###########.

NOTE: This session is executing on the X64_S08R2 platform.

NOTE: Updated analytical products:

SAS/STAT 9.3_M1

NOTE: SAS initialization used:

real time 0.07 seconds

cpu time 0.07 seconds

NOTE: AUTOEXEC processing beginning; file is C:\................\autoexec_for_MASTER.sas.

NOTE: PROCEDURE PRINTTO used (Total process time):

real time 0.00 seconds

cpu time 0.00 seconds

NOTE: AUTOEXEC processing completed.

NOTE: Remote signon to EUSD complete.

NOTE: Background remote submit to EUSD in progress.

NOTE: Remote submit to EUSD commencing.

1 data a;

2 a=&e_construction_type;

WARNING: Apparent symbolic reference E_CONSTRUCTION_TYPE not resolved.

ERROR 22-322: Syntax error, expecting one of the following: a name, a quoted string, a numeric constant, a datetime constant, a missing value, INPUT, PUT.

3 run;

NOTE: The SAS System stopped processing this step because of errors.

WARNING: The data set WORK.A may be incomplete. When this step was stopped there were 0 observations and 2 variables.

NOTE: DATA statement used (Total process time):

real time 0.01 seconds

cpu time 0.00 seconds

NOTE: Remote submit to EUSD complete.

NOTE: Remote signoff from EUSD commencing.

NOTE: SAS Institute Inc., SAS Campus Drive, Cary, NC USA 27513-2414

NOTE: The SAS System used:

real time 0.41 seconds

cpu time 0.21 seconds

NOTE: Remote signoff from EUSD complete.

NOTE: SAS Institute Inc., SAS Campus Drive, Cary, NC USA 27513-2414

NOTE: The SAS System used:

real time 1.00 seconds

cpu time 0.26 seconds

NOTE: Remote signoff from EXTRCTN complete.

Re: %SYSLPUT in a macro

Selcuk — Thu, 18 Oct 2012 07:00:04 GMT

Hi Ahmed ,

problem isn't %syslput , it works fine , but if you use it in a macro block you will encounter this problem.

Check this out >>> http://support.sas.com/kb/47/072.html

Best Regards

Re: %SYSLPUT in a macro

Selcuk — Thu, 18 Oct 2012 07:03:27 GMT

Hi Tom ,

I have to use %syslput in macro block , like below.

%macro test;

%let mvar=5;

%syslput _global_ /like='mvar' ;

rsubmit;

%put mvar="&mvar";

endrsubmit;

%mend test;

%test;

Best Regards

Re: %SYSLPUT in a macro

RichardinOz — Thu, 18 Oct 2012 07:26:46 GMT

It looks to me like you have a 'race condition', ie statements are being executed out of order with respect to which remote session you wish to connect to:

NOTE: Remote submit to EXTRCTN commencing.

1 options autosignon=yes notes sascmd='sas -nosyntaxcheck -autoexec "C:\.................\autoexec_for_MASTER.sas"';

2 %unquote(%syslput _global_/like='e_construction_type' remote=EUSD);

ERROR: Unrecognized option to the %SYSLPUT statement.

System has connected to EXTRCTN but not yet to EUSD hence the option remote=EUSD is not recognised.

You may need to rearrange the macro to have explicit signons to each remote before using %syslput.

Re: %SYSLPUT in a macro

Selcuk — Thu, 18 Oct 2012 07:40:21 GMT

Hi ,

I think that problem isn't that. Because same code works fine when it is not contained by %macro %mend block.

Another point is within the macro block SAS start to read lines as a macro but when it see the %SYSLPUT expression it starts to execute the code immediately.

But still if you can give me a sample using explicit signon I try with pleasure

Best Regards.

Re: %SYSLPUT in a macro

RichardinOz — Thu, 18 Oct 2012 10:23:34 GMT

It seems clear to me from the log that the connection to EXTRCTN happens relatively quickly but the

connection to EUSD takes longer. The first %syslput statement appears to have executed successfully.

Meanwhile the second %sylput statement (with remote=EUSD) appears to have been executed locally before the connection was complete. I think you need some statement to force the connection before the %syslput is executed.

I don't have access to a SAS environment with multiple remote sessions so this is my best guess: place dummy rsubmit statements before %syslput commands.

%macro master_test(papa);

options autosignon=yes sascmd='sas -nosyntaxcheck -autoexec "C:\....\autoexec_for_MASTER.sas"';

rsubmit process=EXTRCTN wait=yes ;

endrsubmit ;

%unquote(%NRSTR(%syslput _global_/like='papa' remote=EXTRCTN));

options autosignon=yes notes sascmd='sas -nosyntaxcheck -autoexec "C:\....\autoexec_for_MASTER.sas"';

%let e_construction_type=&papa;

rsubmit process=EUSD wait=yes ;

endrsubmit ;

%unquote(%NRSTR(%syslput _global_/like='e_construction_type' remote=EUSD));

rsubmit process=EUSD wait=no persist=no;

data a;

a=&e_construction_type;

run;

endrsubmit;

waitfor _all_ EUSD;

endrsubmit;

%mend;

Re: %SYSLPUT in a macro

Tom — Thu, 18 Oct 2012 11:15:15 GMT

Still looks like you are trying to use SYSLPUT to copy the value of GLOBAL macro variable. The only definition of MVAR is within the macro TEST so it will not by in the GLOBAL symbol table. Try adding a %GLOBAL MVAR; statement before the %LET statement in your test macro.

Re: %SYSLPUT in a macro

Selcuk — Thu, 18 Oct 2012 11:38:30 GMT

When I use %global get the error message below

ERROR: Attempt to %GLOBAL a name (PAPA) which exists in a local environment.

Re: %SYSLPUT in a macro

Selcuk — Thu, 18 Oct 2012 11:43:07 GMT

Actualy my problem is that I cant mask %syslput expression from normal execution. I have to execute %syslput expression in macro execution period. The note about this issue in SAS support says to use %NRSTR , but it doesnt work.

Re: %SYSLPUT in a macro

Quentin — Thu, 18 Oct 2012 14:42:45 GMT

I think Tom is on the right track. I somehow overlooked that you were trying to push &PAPA to the remote session.

&Papa is a local macro variable, because it is a parameter to %master_test. Which is why SAS complains when you tried to declare it as global.

When you code:

%NRSTR(%syslput _global_/like='papa' remote=EXTRCTN);

You are having to look for global macro var named PAPA, which doesnt exist. So I would try:

%NRSTR(%syslput _local_/like='papa' remote=EXTRCTN);

&e_construction type is also local, so would try making the change to _local_ on both %syslput statements.

HTH

Re: %SYSLPUT in a macro

Tom — Thu, 18 Oct 2012 16:23:43 GMT

In my testing it looks like it is the RSUBMIT and ENDRSUBMIT statements that SAS 9.3 is processing out of order.

It is executing the RSUBMIT statement while it is compiling the macro.

Here is the code.

signoff;

%let mvar=Before Compile ;

%macro test;

%syslput _global_ / like="mvar" ;

rsubmit;

%put mvar=|&mvar|;

%put mvar=|%nrstr(&mvar)|;

endrsubmit;

%mend test;

Here is the resulting LOG. Notice that even the line numbers for the lines of the macro code are counting wrong.

166 signoff;

NOTE: Remote signoff from PAL commencing.

NOTE: SAS Institute Inc., SAS Campus Drive, Cary, NC USA 27513-2414

NOTE: The SAS System used:

real time 1:45.26

cpu time 0.21 seconds

NOTE: Remote signoff from PAL complete.

167 %let mvar=Before Compile ;

168 %macro test;

169 %syslput _global_ / like="mvar" ;

170 rsubmit;

ERROR: A link must be established by executing the SIGNON command before you can communicate with PAL.

ERROR: Remote submit to PAL canceled.

171 %mend test;

172

Re: %SYSLPUT in a macro

Quentin — Thu, 18 Oct 2012 16:40:42 GMT

Tom-

I think what you are seeing is the original problem that OP noted and linked to the ts note.

It's the %syslput that is trying to communicate with the remote session when the macro compiles.

If you wrap that in %nrstr() as in his first post, that error goes away. At least in my quick test.

I'm still thinking changing to _local_ will help. But I've been wrong before. And several times in this thread...

---Q.

Re: %SYSLPUT in a macro

Tom — Thu, 18 Oct 2012 16:53:59 GMT

It looks likes this new format of the %SYSLPUT command is causing the macro compiler to try and execute the RSUBMIT command while it is compiling the macro.

285 %let mvar=Before Compile ;

286 %macro test;

287 %syslput _global_ / like='mvar' remote=fred ;

288 rsubmit remote=pal;

ERROR: A link must be established by executing the SIGNON command before you can communicate with

PAL.

ERROR: Remote submit to PAL canceled.

289 %mend test;

290

291 %let mvar=After compile;

292 %test;

ERROR: A link must be established by executing the SIGNON command before you can communicate with

FRED.

The solution is to use the OLD style of %SYSLPUT. You might need to test to see if it will automatically start the remote session. But if not then just add the rsubmit code suggested by someone above to trigger the auto connect. Or explicitly connect before calling the macro.

%let mvar=Before Compile ;

**** Define the macro **** ;

%macro test;

%syslput mvar=%superq(mvar) /remote=pal ;

rsubmit remote=pal;

%put mvar=|&mvar|;

endrsubmit;

%mend test;

**** connect to remote ****;

%rsignon(pal);

%let mvar=After compile;

%test;

Re: %SYSLPUT in a macro

Quentin — Thu, 25 Oct 2012 16:44:53 GMT

Hi Selcuk,

Wondering if you arrived at a satisfactory solution?

--Q.