Prev: update a column based on a column in another table
Next: Unstacking Data
From: Alan Churchill on 25 Feb 2010 21:08
In order to support formats, you need support for the actual format, not
just writing/reading a string. Hence, if hex16. Is needed, a routine for
supporting an input or output of hex16 has to be created.

Alan

Alan Churchill
Savian
www.savian.net
Office: (719) 687-5954
Cell: (719) 310-4870


-----Original Message-----
From: SAS(r) Discussion [mailto:SAS-L(a)LISTSERV.UGA.EDU] On Behalf Of
xlr82sas
Sent: Thursday, February 25, 2010 1:15 PM
To: SAS-L(a)LISTSERV.UGA.EDU
Subject: Re: dsread - Windows command-line utility for SAS7BDAT files

On Feb 25, 10:43 am, xlr82sas <xlr82...(a)aol.com> wrote:
> On Feb 25, 6:45 am, ChrisBLong <ch...(a)oview.co.uk> wrote:
>
> > Hi,
>
> > Readers of this group may be interested in dsread, available
athttp://www.oview.co.uk/dsread
>
> > It's a command-line utility that understands the SAS7BDAT file
> > format. It lets you examine the structure of datasets conveniently
> > from the command-line, and converts SAS7BDAT data into valid CSV
> > format for import into other software.
>
> > All comments and suggestions gratefully received,
>
> > Chris.
>
> Hi Chris,
>
> Congratulations for reading SAS datasets. WPS has powerfull
> capabilities. Thanks!!! Competition is great.
>
> Even though you only create csv's, I see this as a great product
> because you do not need SAS and with pipes users can programtically
> get at SAS data from other languages. Also CSVs are also very amenable
> to EXCEL.
>
>
===========================================================================�
===================================================
>
> Just some thoughts:
>
> Any chance you could create a lossless output format, like SAS
> export datasets, but allow for longer names and
> character values greater than 200 bytes. This would open up SAS
> datasets to other languages. The format would have to be open.
>
> This could be a really big deal, if instead of a csv, you created R
> dataframes, if called from R. An even bigger deal would be if you
> created a SAS dataset from an R dataframe.
>
> XML would be another nice output.
>
> A silient ODBC would also be great.
>
> I bet you can use pipes whith yow command line interface.

My apologies.

I assumed your site was somehow affiliated with WPS.
It looks like it may not be.

Which makes what you have done all the more remarkable.

I was hoping you honored formats because I wanted to associate hex16
with the numeric columns so I could create a lossless csv, but it did
not work.
From: Patrick Lupien on 26 Feb 2010 02:06
Hi Chris,

Nice and usefull utility

Is there any chance of it being able to read Unix format SAS7BDAT as well?.
That would make it even more usefull.

Patrick Lupien
Modeling & Simulation
Novartis Pharma AG
Phone: +41 61 3240859
Fax: +41 61 3241246
Email : patrick.lupien(a)novartis.com
From: ChrisBLong on 26 Feb 2010 06:03
Thanks, Patrick. There seems to be some demand for a tool like this
which makes the effort that Alan and I put in to figuring out the file
format all the more rewarding.

The Unix version of SAS7BDAT is exactly the same, but different. The
format consists of all the same elements, but lots of elements are
different sizes between formats - for example, the file header is 1Kb
on Windows but 8Kb on Unix - so in theory the conversion is
straightforward.

I started porting my Windows code over to my Linux system yesterday
but as it uses several Win32 API functions (for date handling, file
system searching, etc) so it's not going to be as easy I'd first
hoped. The Windows version runs ok under Wine so perhaps my first
step will be to have the Windows code read both Windows and Unix
SAS7BDATs, rather than also creating a native Unix executable. I will
report progress via my website, though....

Cheers,

Chris.

On 26 Feb, 07:06, patrick.lup...(a)NOVARTIS.COM (Patrick Lupien) wrote:
> Hi Chris,
>
> Nice and usefull utility
>
> Is there any chance of it being able to read Unix format SAS7BDAT as well?.
> That would make it even more usefull.
>
> Patrick Lupien
> Modeling & Simulation
> Novartis Pharma AG
> Phone: +41 61 3240859
> Fax: +41 61 3241246
> Email : patrick.lup...(a)novartis.com

From: ChrisBLong on 26 Feb 2010 06:05
This is a very easy feature to add... I'll add a 'lossless' option to
force all numerics to be output as if they had the appropriate HEXn.
format applied.

On 25 Feb, 20:15, xlr82sas <xlr82...(a)aol.com> wrote:

> I was hoping you honored formats because I wanted to associate hex16
> with the numeric columns so I could create a lossless csv, but it did
> not work.

From: Tom Abernathy on 26 Feb 2010 11:20
Other issue to watch for in the sas7bdat format is the 32bit vs 64bit
issue. Even SAS's own tool (SAS System Viewer 9.1) has trouble with
this. It cannot read 64bit files from SAS 9.2 on Unix even though it
can read the 32bit files from Unix and the 32bit and 64bit files from
Windows.


On Feb 26, 6:05 am, ChrisBLong <ch...(a)oview.co.uk> wrote:
> This is a very easy feature to add... I'll add a 'lossless' option to
> force all numerics to be output as if they had the appropriate HEXn.
> format applied.
>
> On 25 Feb, 20:15, xlr82sas <xlr82...(a)aol.com> wrote:
>
>
>
> > I was hoping you honored formats because I wanted to associate hex16
> > with the numeric columns so I could create a lossless csv, but it did
> > not work.- Hide quoted text -
>
> - Show quoted text -

First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4
Prev: update a column based on a column in another table
Next: Unstacking Data