Date: Wed, 21 Nov 2007 10:38:35 -0600
Reply-To: "data _null_," <datanull@GMAIL.COM>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: "data _null_," <datanull@GMAIL.COM>
Subject: Re: Proc Format Error
Content-Type: text/plain; charset=ISO-8859-1
Again you are confusing youself with what you think you know about the
data. Lets take your SMFSTAMP data that you see as something special.
It ain't it is just a string of bits, bytes or characters whatever you
want to call it. It only has meaning if you know how to read it.
The code snippet was related the the statement that SAS does not have
a format/informat that equates to the internal representation it uses
for NUMERIC values. But it does RB8.
On Nov 21, 2007 10:13 AM, Gerhard Hellriegel
> what has this to do with SMFSTAMP? That is for a special datetime-value,
> IBM uses for writing such values in the zOS-RMF/SMF data!
> On Wed, 21 Nov 2007 09:36:31 -0600, data _null_, <datanull@GMAIL.COM>
> >On Nov 21, 2007 12:00 AM, RolandRB <email@example.com> wrote:
> >> might be an informat named SASFLOAT. with a default length of 8. Then
> >> it would be used in a similar way to SMFSTAMP.. SASFLOAT. would then
> >> give you the value of the number if used. But since this is internal
> >> to SAS then SAS is hiding this from you and doing the conversion
> >> internally.
> >It is called RB8.
> >493 data _null_;
> >494 attrib sasfloat length=8;
> >495 call poke(put(99,rb8.),addr(sasfloat),8);
> >496 y = input(peekC(addr(sasfloat)),rb8.);
> >497 put (_all_)(=);
> >498 run;
> >NOTE: Variable sasfloat is uninitialized.
> >sasfloat=99 y=99