Date: Mon, 14 May 2007 01:34:53 -0700
Reply-To: celiacai@GMAIL.COM
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: celiacai@GMAIL.COM
Organization: http://groups.google.com
Subject: Re: dealing with library name?
In-Reply-To: <02AD6C867A7EB549A03ABCF3EC14739F041527B8@DC105WEXMSV04.ebus.root.internal>
Content-Type: text/plain; charset="iso-8859-1"
Thanks Dave,
But the problem remains...
Btw, when I used two dots the text color ("in_ds..c" changed to blue),
so I guess there's something wrong with the two dots...
586 %let out_ds = C;
587 %let in_ds = D;
588
589 proc sql;
590 create table &out_ds as
591 select * from A, B, &in_ds
592 where A.cuip6=B.cusip6
593 and B.cusip6=&in_ds..cusip6
22: LINE and COLUMN cannot be determined.
NOTE 242-205: NOSPOOL is on. Rerunning with OPTION SPOOL may allow
recovery of the LINE and
COLUMN where the error has occurred.
ERROR 22-322: Syntax error, expecting one of the following: ;, !, !!,
&, *, **, +, -, /, <, <=,
<>, =, >, >=, AND, EQ, EQT, EXCEPT, GE, GET, GROUP, GT,
GTT, HAVING, INTERSECT,
LE, LET, LT, LTT, NE, NET, NOT, OR, ORDER, OUTER, UNION,
^, ^=, |, ||, ~, ~=.
594 and repo1.date_announced=final.date_announced;
76: LINE and COLUMN cannot be determined.
NOTE: NOSPOOL is on. Rerunning with OPTION SPOOL may allow recovery of
the LINE and COLUMN
where the error has occurred.
ERROR 76-322: Syntax error, statement will be ignored.
595 quit;
NOTE: The SAS System stopped processing this step because of errors.
NOTE: PROCEDURE SQL used (Total process time):
real time 0.00 seconds
cpu time 0.00 seconds
On May 14, 5:54 pm, David.Bi...@DISABILITY.QLD.GOV.AU (David Birch)
wrote:
> Celia, I think your code should be:
>
> %let out_ds = test;
> %let in_ds = final;
>
> proc sql;
> create table &out_ds as
> select * from A, B, &in_ds
> where A.cusip6=B.cusip6
> and B.cusip6=&in_ds..cusip6
> and A.date=B.date;
> quit;
>
> Your original expression was testing whether A.cusip6 was equal to 1 or
> 0 (whether B.cusip6 was equal to &in_ds..cusip6)! The error message is
> confusing - that's because the SQL parser was confused.
>
> HTH,
>
> Dave
>
>
>
> -----Original Message-----
> From: SAS(r) Discussion [mailto:S...@LISTSERV.UGA.EDU] On Behalf Of
>
> celia...@GMAIL.COM
> Sent: Monday, 14 May 2007 4:37 PM
> To: S...@LISTSERV.UGA.EDU
> Subject: Re: dealing with library name?
>
> following Florio, the log looks like this....
>
> 308 %let out_ds = test;
> 309 %let in_ds = fianl;
> 310
> 311 proc sql;
> 312 create table &out_ds as
> 313 select * from A, B, &in_ds
> 314 where A.cusip6=B.cusip6=&in_ds..cusip6
> 22: LINE and COLUMN cannot be determined.
> NOTE 242-205: NOSPOOL is on. Rerunning with OPTION SPOOL may allow
> recovery of the LINE and
> COLUMN where the error has occurred.
> ERROR 22-322: Syntax error, expecting one of the following: ;, !, !!,
> &, *, **, +, -, /, <, <=,
> <>, =, >, >=, AND, EQ, EQT, EXCEPT, GE, GET, GROUP, GT,
> GTT, HAVING, INTERSECT,
> LE, LET, LT, LTT, NE, NET, NOT, OR, ORDER, OUTER, UNION,
> ^, ^=, |, ||, ~, ~=.
> 315 and A.date=B.date;
> 76: LINE and COLUMN cannot be determined.
> NOTE: NOSPOOL is on. Rerunning with OPTION SPOOL may allow recovery of
> the LINE and COLUMN
> where the error has occurred.
> ERROR 76-322: Syntax error, statement will be ignored.
> 316 quit;
> NOTE: The SAS System stopped processing this step because of errors.
> NOTE: PROCEDURE SQL used (Total process time):
> real time 0.00 seconds
> cpu time 0.00 seconds
>
> On May 14, 4:00 pm, celia...@gmail.com wrote:
> > Hi,
>
> > When I use dataset variables in sql, how can I avoid the library name
> > problem shown below?
>
> > 173 %let out_ds = test;
> > 174 %let in_ds = final;
> > 175
> > 176 proc sql;
> > 177 create table &out_ds as
> > 178 select * from A, B, &in_ds
> > 179 where A.cusip6=B.cusip6=&in_ds.cusip6
> > 180 and A.date=B.date;
> > ERROR: The following columns were not found in the contributing
> > tables: finalcusip6.
> > 181 quit;
>
> ********************************* DISCLAIMER *********************************
> The information contained in the above e-mail message or messages (which includes any attachments) is confidential and may be legally privileged. It is intended only for the use of the person or entity to which it is addressed. If you are not the addressee any form of disclosure, copying, modification, distribution or any action taken or omitted in reliance on the information is unauthorised. Opinions contained in the message(s) do not necessarily reflect the opinions of the Queensland Government and its authorities. If you received this communication in error, please notify the sender immediately and delete it from your computer system network.- Hide quoted text -
>
> - Show quoted text -
| 
