Date: Thu, 28 Sep 2006 09:20:53 -0400
Reply-To: "data _null_;" <datanull@GMAIL.COM>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: "data _null_;" <datanull@GMAIL.COM>
Subject: Re: Length function doesn't work (Data too long for column ...
truncated)
In-Reply-To: <20060928130118.96718.qmail@web34102.mail.mud.yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
You don't really show enough of data ORIG code to know but it could be
as simple as the formats are too long not the length. Use proc
contents to verify the meta data for ORIG. Consider the following....
2 options ls=64;
3 proc contents data=sashelp.class varnum;
4 run;
NOTE: PROCEDURE CONTENTS used:
real time 0.03 seconds
cpu time 0.03 seconds
NOTE: The PROCEDURE CONTENTS printed page 1.
5 proc print data=sashelp.class;
6 format name $100.;
7 run;
WARNING: Data too long for column "Name";
truncated to 60 characters to fit.
NOTE: There were 19 observations read from the data set
SASHELP.CLASS.
NOTE: The PROCEDURE PRINT printed page 2.
On 9/28/06, Irin later <irinfigvam@yahoo.com> wrote:
> At the very beginning of my code I set the length of the character data fields like that:
> data ORIG;
> 593 length asked_question $ 6;
> 594 length response_to_question $ 6;
> 595 length accepts_calls $ 3;
> 596 length wrong_phone_number $ 6;
>
> However after I run the whole code Print data caused a WARNING message regarding too long data as below:
>
> 656 %macro diag2(dsn,resp);
> 657 proc print data=&dsn (obs=20);
> 658 var shot shotdate questiondate;
> 659 where shot = "&resp";
> 660 title "Printout of &dsn to check shot variable where shot=&resp";
> 661 run;
> 662
> 663 proc print data=&dsn (obs=20);
> 664 var enroll startdate enddate accepts_calls wrong_phone_number;
> 665 where enroll = "&resp";
> 666 title "Printout of &dsn to check enroll variable where enroll=&resp";
> 667 run;
> 668
> 669 %mend;
> 670
> 671 %diag1(flu_single2);
>
>
> WARNING: Data too long for column "accepts_calls"; truncated to 93 characters to fit.
> WARNING: Data too long for column "wrong_phone_number"; truncated to 93 characters to fit.
> NOTE: There were 20 observations read from the data set WORK.FLU_SINGLE2.
> WHERE enroll='Y';
> NOTE: PROCEDURE PRINT used:
> real time 0.01 seconds
> cpu time 0.01 seconds
>
>
> I do not understand why LENGTH function, which I set at the very beginning, does not work for these fields. Is it because of the macro? Why? How can I fix it ?
>
> Thank you in advance,
>
> Irin
>
>
>
>
> ---------------------------------
> Yahoo! Messenger with Voice. Make PC-to-Phone Calls to the US (and 30+ countries) for 2¢/min or less.
>