topic Re: syntax error in SAS Enterprise Guide

syntax error

Rsadiq — Tue, 18 Apr 2017 13:30:13 GMT

Hello

I am getting this error and cant seem to figure out what is going on

Thanks

Rida

WARNING: Apparent symbolic reference THRU_ALL not resolved.
NOTE 137-205: Line generated by the invoked macro "QTRLY_SUMS".
809         PROC APPEND BASE=rptlib.qrtly_sum_totals1 DATA=in_b FORCE; RUN;    PROC SQL;    CREATE TABLE rptlib.qrtly_sum_totals AS
809      !    SELECT     *     ,&thru_all.    FROM rptlib.qrtly_sum_totals1   ;QUIT;
                                                   ______
                                                   22
ERROR 22-322: Syntax error, expecting one of the following: a name, a quoted string, a numeric constant, a datetime constant,

Re: syntax error

art297 — Tue, 18 Apr 2017 13:35:02 GMT

What is the macro variable &thru_all and is it even needed. By using select * you are already selecting all of the dataset's variables.

Art, CEO, AnalystFinder.com

Re: syntax error

RW9 — Tue, 18 Apr 2017 13:42:47 GMT

WARNING: Apparent symbolic reference THRU_ALL not resolved.

The above is telling you that the macro variable THUR_ALL does not exist. Therefore the code:

SELECT * , FROM

Is invalid.

Re: syntax error

LinusH — Tue, 18 Apr 2017 13:43:00 GMT

Well, it could be a constant that should be added to the result.

Either way, it's not assigned at the execution time for this query.

Re: syntax error

Kurt_Bremser — Tue, 18 Apr 2017 14:08:01 GMT

If macro variable thru_all is to be used to add a variable (or several variables) to a dataset, it should contain the comma, and your code should look like

proc sql;
create table rptlib.qrtly_sum_totals as
select * &thru_all.
from rptlib.qrtly_sum_totals1;
quit;

Now you will get no ERROR if &thru_all is empty or undefined. The WARNING for an undefined macro variable will persist, though.

Re: syntax error

Tom — Tue, 18 Apr 2017 14:16:43 GMT

If it is undefined then it will still generate a syntax error. It will just leave the macro reference as it was and the this:

select * &thru_all.

Is not valid syntax.

Re: syntax error

Kurt_Bremser — Tue, 18 Apr 2017 14:17:43 GMT

@Tom wrote:

If it is undefined then it will still generate a syntax error. It will just leave the macro reference as it was and the this:
select * &thru_all.
Is not valid syntax.

Correct. Shame on me.