Prev: Oracle Clinical: table RXC_DCI_BOOK_PAGES
Next: Macro variable and do loop
From: Clark An on 22 Feb 2010 11:09
Thank you.
My problem is the variable names,not the values.
So any ideas,or an example code?
From: xlr82sas on 22 Feb 2010 13:41
On Feb 22, 8:04 am, kuh...(a)126.COM (Clark An) wrote:
> Thank you.
> How's the performance of sas/r pls?

Hi

My initial indications are that the performance of R for in memory
problems is competitive with SAS. However, you do pay a price for
initiating R and the export conversions. The Java interface I am
working on is much more poweful and should be very competitive. It use
memory pointers so SAS and R communicate in memory, no ODBC, export
and init R issues.

If SAS had a silient read/wrire ODBC that would be another better
way to go. I just cannot understand why we need to bring up another
SAS session for ODBC communications, and that session has to be closed
manually. I would like to know why SAS removed and stopped working on
the Universal ODBC driver.

I was thinking that a drop down to SCL would be interesting. I have
a mechanism to work around the required GUI interface.

R is a means of enriching SAS not replacing it. R has issues with
'too big fit in memory', large datasets, documentation and support.
Also I think the graphics capabilities are not as good as 9.2 SVG, SG
and ODS graphics. Even though R supports LaTex I still believe SAS ods
destinations of PDF and RTF along with templates fit the FDA
requirements for TLGs better than R.

A little help from SAS would go a long way, ie better Java object and
silent ODBC.

Regards

From: xlr82sas on 22 Feb 2010 22:37
On Feb 22, 10:41 am, xlr82sas <xlr82...(a)aol.com> wrote:
> On Feb 22, 8:04 am, kuh...(a)126.COM (Clark An) wrote:
>
> > Thank you.
> > How's the performance of sas/r pls?
>
> Hi
>
>   My initial indications are that the performance of R for in memory
> problems is competitive with SAS. However, you do pay a price for
> initiating R and the export conversions. The Java interface I am
> working on is much more poweful and should be very competitive. It use
> memory pointers so SAS and R communicate in memory, no ODBC, export
> and init R issues.
>
>   If SAS had a silient read/wrire ODBC that would be another better
> way to go. I just cannot understand why we need to bring up another
> SAS session for ODBC communications, and that session has to be closed
> manually. I would like to know why SAS removed and stopped working on
> the Universal ODBC driver.
>
>   I was thinking that a drop down to SCL would be interesting. I have
> a mechanism to work around the required GUI interface.
>
>   R is a means of enriching SAS not replacing it. R has issues with
> 'too big fit in memory', large datasets, documentation and support.
> Also I think the graphics capabilities are not as good as 9.2 SVG, SG
> and ODS graphics. Even though R supports LaTex I still believe SAS ods
> destinations of PDF and RTF along with templates fit the FDA
> requirements for TLGs better than R.
>
>  A little help from SAS would go a long way, ie better Java object and
> silent ODBC.
>
> Regards

Here is the IML soution:


proc iml;
x=shape({0} ,1,120,0);
n=shape({' '},1,120,'x0000');
print n;
idx=0;
do i = 1 to 2;
do j = 1 to 3;
do k = 1 to 4;
do l = 1 to 5;
idx=idx+1;
x[1,idx]=1000*i+100*j+10*k+l;
n[1,idx]=cats('x',char(i,1,0),char(j,1,0),char(k,
1,0),char(l,1,0));
end;
end;
end;
end;
create mat2345 from x[colname=n];
append from x;
close mat2345;
quit;
run;

proc contents;
run;

Alphabetic List of Variables and Attributes

# Variable Type Len

1 X1111 Num 8
2 X1112 Num 8
3 X1113 Num 8

I will see if I can post the SCL solution.
From: Clark An on 23 Feb 2010 00:57
Thank you very much.
From: Clark An on 23 Feb 2010 04:07
I get a problem....

in the do loop data step....

array(n)=lag&n.(x);

any ideas?Thank you very much!
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5
Prev: Oracle Clinical: table RXC_DCI_BOOK_PAGES
Next: Macro variable and do loop