topic Re: Strange behaviour of proc SQL + Proc CORR in SAS Procedures

Strange behaviour of proc SQL + Proc CORR

SPR — Thu, 08 Oct 2020 18:57:47 GMT

This simple program does not produce Pearson dataset:

data a;
a=1; b=3; output;
a=4; b=5; output;
run;

proc SQL noprint; select MAX(A) into :a trimmed from a; %put &=a;

ODS output PearsonCorr=Pearson;
proc CORR data=a;
var a;
with b;
run;

WARNING: Output 'PearsonCorr' was not created. Make sure that the output object name, label, or path is spelled correctly. Also,
verify that the appropriate procedure options are used to produce the requested output object. For example, verify that
the NOPRINT option is not used.

The reason for this is absence of quit; in proc SQL code.

Using

proc SQL noprint; select MAX(A) into :a trimmed from a; quit; %put &=a;

produces the expected output:

NOTE: The data set WORK.PEARSON has 1 observations and 3 variables.

I've noticed that some seasoned programmers do not put quit; in this type proc SQL code. This trick works fine in most cases but not every time. Or may be I'm wrong?

Re: Strange behaviour of proc SQL + Proc CORR

Reeza — Thu, 08 Oct 2020 19:02:15 GMT

Boundaries, where code blocks start/stop, are defined by QUIT, RUN, DATA and PROC. ODS is not a boundary statement.

The issue in this case is you do not explicitly terminate the prior procedure so the ODS OUTPUT statement is mapped to the SQL procedure not the PROC CORR.

If you move the ODS OUTPUT to after the PROC it's also fine because the PROC acts as a boundary. Basically, its an order of operations thing - you need to ensure the boundary is set before your ODS statements.

@SPR wrote:

This simple program does not produce Pearson dataset:

data a;
a=1; b=3; output;
a=4; b=5; output;
run;

proc SQL noprint; select MAX(A) into :a trimmed from a; %put &=a;

ODS output PearsonCorr=Pearson;
proc CORR data=a;
var a;
with b;
run;

WARNING: Output 'PearsonCorr' was not created. Make sure that the output object name, label, or path is spelled correctly. Also,
verify that the appropriate procedure options are used to produce the requested output object. For example, verify that
the NOPRINT option is not used.

The reason for this is absence of quit; in proc SQL code.

Using

proc SQL noprint; select MAX(A) into :a trimmed from a; quit; %put &=a;

produces the expected output:

NOTE: The data set WORK.PEARSON has 1 observations and 3 variables.

I've noticed that some seasoned programmers do not put quit; in this type proc SQL code. This trick works fine in most cases but not every time. Or may be I'm wrong?

Re: Strange behaviour of proc SQL + Proc CORR

SPR — Thu, 08 Oct 2020 19:07:22 GMT

I moved ODS output PearsonCorr=Pearson; inside the proc CORR and the program works fine without quit; Thanks.

Re: Strange behaviour of proc SQL + Proc CORR

RichardDeVen — Sat, 10 Oct 2020 14:09:05 GMT

Regarding PROC boundaries and ODS OUTPUT statement, the same concept is in play with other statements such as TITLE and FOOTNOTE.