About snoopy369

snoopy369 · ‎10-24-2013

I don't know that "below this one" means, perhaps my math education is lacking. I only know of using 'diagonal' to mean the primary diagonal, either top left to bottom right or top right to bottom left. If you want something else, please explain.

snoopy369 · ‎10-24-2013

Even 16 digits is not safe. 2^53 (around 4x10^15) is the maximum storable number with full precision; so some Visa numbers may be storable, but no Mastercard numbers (5x10^15). This of course is often relevant with credit card numbers simply because they are right at that point of precision loss.

snoopy369 · ‎10-24-2013

Depending on your operating system, SAS can only handle around 15 digits of precision with a numeric (in Windows, out of 64 bits for an 8 byte number, 1 is the sign and 11 are the exponent, meaning 52 bits are available for the mantissa (the precise digits) - around 4x10^15. Any number over 4x10^15 will begin losing precision. See SAS(R) 9.2 Language Reference: Concepts, Second Edition for more information.

snoopy369 · ‎10-23-2013

You're in the land of Oracle issues, then, or at least beyond my knowledge of passthrough. I don't know if you can even set a variable in passthrough; that's PL/SQL, and I don't know what happens there. You might try setting up a stored procedure in Oracle to do these things, and call it through passthrough?

snoopy369 · ‎10-23-2013

SQL Join is probably your best bet - you could do this in a data step merge also, if you set things up ahead of time with a variable for 'desired lag date'. data have; input group $ date :anydtdte. numobs desiredlag; datalines; M1XM 01/2008 2 . M1XM 01/2009 221 2 M1XM 02/2009 452 2 M1XM 03/2009 132 2 M1XM 05/2009 45 2 M1XM 01/2010 2 221 M3GL 01/2008 4 . M3GL 01/2009 15 4 M3GL 02/2009 45 4 M3GL 03/2009 13 4 M3GL 05/2009 12 4 M3GL 08/2009 1265 4 M3GL 10/2009 985 4 M3GL 12/2009 451 4 M3GL 01/2010 352 15 M3GL 02/2010 41 45 M3GL 03/2010 7 13 M3GL 04/2010 45 . M3GL 05/2010 62 12 ;;;; run; proc sql; create table want as select H.*, L.numobs as lyobs from have H left join have L on (H.group=L.group) and ((H.date = intnx('YEAR',l.date,1,'s')) or (year(H.date)=2009 and year(L.date)=2008)) order by H.group, H.date; quit;

snoopy369 · ‎10-23-2013

Is the option throwing the error or is the second statement? I think you will have trouble with the single quotes around a macro variable - you either need to have &1 contain its own single quotes, or use something like %bquote('&1') to force it to resolve.

snoopy369 · ‎10-23-2013

Similarly to Art's solution, but horizontal - using a temporary (and automatically retained) array to store the values and then copy back to the PDV in the last row. data have; input var1 var2 var3 var4 var5; datalines; 1 . . . . . 2 . . . . . 3. . . . . . 4 . . . . . 5 ; data want; set have end=eof; array all _all_; array temps [9999] _temporary_; temps[_n_]=all[_n_]; if eof then do; do _t = 1 to dim(all); all[_t]=temps[_t]; end; output; end; run;

snoopy369 · ‎10-23-2013

Thanks DanH, figured it was something like that but couldn't find the place to set the option!

snoopy369 · ‎10-22-2013

I have the following code, with a vbarparm and a scatterplot. If I remove the scatterplot, I get a nice graph with no extra lines; just the border around the graph. If I uncomment the scatterplot, that works, except now I have an extra line - presumably some padding between pre-existing lines. The bars now come from an origin line that is some distance above the box around the graph. Is there any way to remove that line and/or padding? I'm not entirely sure why it exists in the first place. I do want the bars to originate from the bottom of the box line, not to originate from a nonexistent x axis line. The general concept here is that I'm placing stat test results over the bars, and since I'm using groupdisplay=cluster I cannot use datalabel; so scatter with a position of 105 seemed most reasonable as a solution. I'd be happy to consider other solutions if there is a better way to do this. Thanks! data mydata; length stub $15; input installation $ stub $ prop ; top=105; statresult=ifc(installation='Facility','†#*',' '); datalines; Facility Favorable 65 Facility Neutral 25 Facility Unfavorable 10 Region Favorable 75 Region Neutral 15 Region Unfavorable 10 Nation Favorable 55 Nation Neutral 25 Nation Unfavorable 20 ;;;; run; proc template; define statgraph mybarplot; begingraph /; layout overlay / xaxisopts=( display=( tickvalues ) TickValueAttrs=( Size=8pt Family="Arial/Bold") type=discrete discreteopts=( TickValueFitPolicy=SplitRotate sortOrder=data ) ) y2axisopts=(labelFitPolicy=Split) yaxisopts=( display=none labelFitPolicy=Split type=auto ) x2axisopts=(display=none) y2axisopts=(labelFitPolicy=Split); BarChartParm X=installation Y=prop / primary=true Group=stub DataLabelAttrs=( Color=CX000000 Family="ARIAL" Size=8 Weight=bold ) Display=( Fill ) barwidth=0.4 LegendLabel="Range" NAME="Facility" groupdisplay=stack grouporder=ascending dataskin=pressed ; scatterplot x=installation y=top / xaxis=X primary=false markercharacter= statresult; DiscreteLegend "Facility" / Location=Outside valign=bottom Title=" "; endlayout; endgraph; end; run; proc sgrender data=mydata template=mybarplot; run;

snoopy369 · ‎10-21-2013

It somewhat depends on how you're importing it (which DBMS you're using), but most of the time the MIXED=YES option is helpful for what you're asking. If not, post your full import code (with filename anonymized if needed) so you can get the best help possible.

snoopy369 · ‎10-21-2013

Data step read gives you more control than PROC IMPORT; so if PROC IMPORT guesses wrong, or doesn't give you the result you need in terms of formats/informats, you should use data step read. I typically only use PROC IMPORT as a helper (to give me a starting point) in my production code, as I worry PROC IMPORT may yield inconsistent results; but if you're okay with that possibility (if this is a one-time run, for example, or minor inconsistencies with length of text variables and such aren't important) and you're not doing complicated things with formats, you can just use PROC IMPORT.

snoopy369 · ‎10-17-2013

Can you access that in windows explorer? IE, I might have a NAS store in: //mycompanysnas/sasfiles/myfolder/projectname/ that I could just open in Windows Explorer. If I can do that (on the machine running SAS, whether that's your local server/installation or you have a windows or whatever server running SAS that you use EG to connect to), then you can just write the libname that way: libname servlib "//mycompanysnas/sasfiles/myfolder/projectname/"; Then you can use it as a normal library - proc copy to your heart's content. If you can't access it directly, you'll want to provide more information - are you running this locally or on a SAS Server; does this other server also have a SAS server running; are you using SAS CONNECT, Enterprise Guide, etc.?

snoopy369 · ‎10-16-2013

Sounds to me like it's not comma separated, but semicolon separated. proc import file=whatever out=whatever dbms=dlm dlm=';' replace; getnames=yes; run; (using same options as your code, just dbms=dlm and dlm=';' ) Also, do you have ACCESS to PC FILES licensed? PROC IMPORT can read in an SPSS file. (proc import file="whatever.sav" out=whatever dbms=SPSS replace; run;)

snoopy369 · ‎10-16-2013

select(input(tab1.mndate,MMDDYY10.) - input(tab2.mndate,MMDDYY10.)) ... This assumes that is the correct informat; you may need a different one, or even a datetime, in which case you would need datepart(input... ) - datepart(input...) if you want days not seconds.

snoopy369 · ‎10-15-2013

akilees wrote: Thank you! Here is the code for reading the variables. Right, I should specify the length, but I don't know how long I should do, so I just estimate the longest possible value? data have; infile '' lrecl=32767 firstobs=2 dlm='|'; input level1 $ level2_code $ level2 $; run; lrecl is only defining the length of the total record. You still need to define your character variables' length. For example: data have; infile a lrecl=32767 firstobs=2 dlm='|'; input level1 :$15. level2_code :$3. level2 :$15.; run; (note the colons) Or data have; infile a lrecl=32767 firstobs=2 dlm='|'; informat level1 level2 $15. level2_code $3.; input level1 $ level2_code $ level2 $; run; Or use length or format similarly. Length is somewhat better if you're just defining lengths and don't have informats for your variables (all plain characters); informat is somewhat more common if you do have some informats (date variables etc.) and matches what you see from PROC IMPORT. One trick you can use is to PROC IMPORT, see what the proc import decides for lengths, and borrow that (look at your log).

Online Status	Offline
Date Last Visited	‎10-10-2025 01:59 PM

Re: What is the state of SASGF 2022?

Re: Installing add-on package

Re: Help with ods output statement

Re: drill down from visual SAS Visual analytics

Applying control-based filters to subset of data

Re: EG 7.1 code lost during update

Re: Is there a way to use FIRST and LAST options within an IF THEN sta...

Re: Conexão SAS com Python para executar uma rotina

Re: How to transpose many columns to one

Re: Using a SAS Dataset instead of an External file in this interestin...

Re: Help with ods output statement

Re: What is the state of SASGF 2022?

Re: Editing the legend in a map

Editing the legend in a map

Make SAS Studio Log Window Honor the Alt Key

Re: Finding a value in all datasets in all variables

Re: Installing add-on package

Re: proc sgpanel x-axis with multiple scales

Re: Help with ods output statement

Re: Viya 3.5 on Ubuntu 18?

Git and SAS®: A Match Made in (SAS®) Studio

Re: Diagonal as horizontal

Re: Last two digits changed when converting character value into numer...

Re: Last two digits changed when converting character value into numer...

Re: Passing Oracle option from SAS SQL pass through facility.

Re: Lagged variables for DiD analysis

Re: Passing Oracle option from SAS SQL pass through facility.

Re: Diagonal as horizontal

Re: GTL - Overlaying SCATTER over VBARPARM gives extra axis line

GTL - Overlaying SCATTER over VBARPARM gives extra axis line

Re: Import Excel and Make a Column with Dates a Character Column

Re: pipe delimited file

Re: Copy or move a table between libraries

Re: Problems when importing a file into SAS

Re: char dates

Re: pipe delimited file

SAS Global Forum 2018

SAS Global Forum