Date:         Wed, 27 Jan 2010 16:41:51 -0800
Reply-To:     Tom Abernathy <tom.abernathy@GMAIL.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Tom Abernathy <tom.abernathy@GMAIL.COM>
Organization: http://groups.google.com
Subject:      Re: How to read a large odd looking file
Comments: To: sas-l@uga.edu
Content-Type: text/plain; charset=ISO-8859-1

Art -
  I looked at this a little for Elvira earlier this week. It looks
like the first 2 bytes are the record length and the third is a record
type.  Try running this program against the whole file.

data records;
  infile tmpfile1 recfm=n;
  length len 4 rec $1 hex $400 string $200 ;
  input len ib2.;
  input string $varying200. len;
  rec=substr(string,1,1);
  string=substr(string,2);
  hex=putc(string,'$hex'||compress(put((len-1)*2,3.)));
run;
proc freq ;
  tables rec*len / list;
run;
proc print data=records (obs=100);
  var len rec hex;
run;

In the subset you sent I see 16 records. 5 H, 8 R, 1 S and 2 T. Each
record type seems to have a consistent length.
The T value looks like an integer. Not sure what S is. The H and R
appear like they sub structures.  Notice the pattern of where the
spaces ('20'x) and nulls ('00'x) are located.


Obs    len    rec    hex

  1      5     T     00005471
  2      6     S     23767F7F4F
  3      5     T     0000587F
  4     18     R     221807004120202020205420000000644E
  5     18     R     221807004120202020205420000000644E
  6     18     R     222749404141202020205420000000644E
  7     17     H     22367F7F412020202020542020202020
  8     18     R     22367F7F41412D2020205420000000644E
  9     17     H     22367F7F412020202020542020202020
 10     18     R     22457F7F4141432020205420000000644E
 11     17     H     22457F7F414120202020542020202020
 12     18     R     22457F7F4141434320204720000000644E
 13     17     H     22457F7F41412D202020542020202020
 14     18     R     22457F7F4141492020205420000000644E
 15     17     H     22457F7F414143202020542020202020
 16     18     R     22457F7F41414D45202047202020202020

- Tom

On Jan 27, 1:41 pm, art...@NETSCAPE.NET (Arthur Tabachneck) wrote:
> Dan,
>
> Yes it is that same file.
>
> Art
> ---------
> On Wed, 27 Jan 2010 10:32:43 -0800, Nordlund, Dan (DSHS/RDA)
>
>
>
>
>
> <Nord...@DSHS.WA.GOV> wrote:
> >> -----Original Message-----
> >> From: SAS(r) Discussion [mailto:SA...@LISTSERV.UGA.EDU] On Behalf Of
> >> Arthur Tabachneck
> >> Sent: Wednesday, January 27, 2010 10:26 AM
> >> To: SA...@LISTSERV.UGA.EDU
> >> Subject: Re: How to read a large odd looking file
>
> >> What I posted was indeed a hex viewer filedump as I didn't think the
> list
> >> would appreciate my posting the actual 8gig of characters.  These were
> >> simply the first 272 characters.
> >> On Wed, 27 Jan 2010 13:12:48 -0500, Proc Me <procme@CONCEPT-
> >> DELIVERY.COM>
> >> wrote:
>
> >Art,
>
> >Is this the "binary" data file that we were discussing a few days ago on
>
> the list?  If not, do you have  any additional information about the
> supposed structure of the dataset?
>
>
>
>
>
> >Dan
>
> >Daniel J. Nordlund
> >Washington State Department of Social and Health Services
> >Planning, Performance, and Accountability
> >Research and Data Analysis Division
> >Olympia, WA  98504-5204- Hide quoted text -
>
> - Show quoted text -- Hide quoted text -
>
> - Show quoted text -