| Date: | Thu, 14 Jan 1999 03:57:18 -0500 |
| Reply-To: | Undetermined origin c/o LISTSERV administrator
<owner-LISTSERV@VTVM1.CC.VT.EDU> |
| Sender: | "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU> |
|
| From: | Undetermined origin c/o LISTSERV administrator
<owner-LISTSERV@VTVM1.CC.VT.EDU> |
|---|
finch-post-10.mail.demon.net([194.217.242.38];helo=post.mail.demon.net) by
AKH-Wien.AC.AT with
TCP
Received: from [194.222.186.226] (helo=crawfordsoftware.demon.co.uk) by
post.mail.demon.net with smtp (Exim 2.10 #1) id 100iR5-0007f7-00 for
SAS-L@AKH-WIEN.AC.AT; Thu, 14 Jan 1999 08:47:27 +0000
MIME-Version: 1.0
X-Mailer: Turnpike (32) Version 3.05 <uUq1LwAYB2QUgi8fmhIjRFrCnM>
Message-ID: <UZ4tiDA+3an2Ewao@crawfordsoftware.demon.co.uk>
Newsgroups: bit.listserv.sas-l
Date: Thu, 14 Jan 1999 08:42:38 +0000
Reply-To: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK>
Sender: "SAS(r) Discussion" <SAS-L@AKH-WIEN.AC.AT>
From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK>
Subject: Re: Proc Logistic output problem
X-LSVRepTo:
X-LSVopts: NOACK
X-LSVvia: SAS-L@AKH-WIEN.AC.AT
X-LSVTag: Message-ID: <UZ4tiDA+3an2Ewao@crawfordsoftware.demon.co.uk>
X-LSVTag: Date: Thu, 14 Jan 1999 08:42:38 +0000
X-LSVTag: To: SAS-L@AKH-WIEN.AC.AT
X-LSVTag: From: Peter Crawford <Peter@crawfordsoftware.demon.co.uk>
X-LSVTag: Subject: Re: Proc Logistic output problem
X-LSVTag: In-Reply-To: <916276616.214511.0@vm121.akh-wien.ac.at>
X-LSVTag: MIME-Version: 1.0
X-LSVTag: X-Mailer: Turnpike (32) Version 3.05 <uUq1LwAYB2QUgi8fmhIjRFrCnM>
To: $PEER$ <SAS-L@VTVM1.CC.VT.EDU>
In-Reply-To: <916276616.214511.0@vm121.akh-wien.ac.at>
To respect & preserve embedded / leading blanks use informat $charN.
When you read variable width data, it may be safer to use the infile
option TRUNCOVER than MISSOVER
In article <916276616.214511.0@vm121.akh-wien.ac.at>, Lanning, Chris
<clanning@AMGEN.COM> writes
>Hello all,
>
>Here is my problem. Proc Logistic gives some very nice diagnostic output
(snip)
>number with the patient number. For some reason every time I read from the
>'lst' file using INFILE ... PAD; SAS removes the leading blanks even though
>I am specifying the start (using the @1) and an informat (using $11.).
>Please see code below.
>
(snip)
>*** Read in the logistic.lst;
>data temp3;
> infile 'c:\mydocu~1\logistic.lst' pad missover;
> input @1 num1 $11. *** Should include leading blanks, shouldn't
>it?;
> @12 char1 $157.;
>
> obnum = _n_; *** Keep track of original order of output so I can
>reconstruct;
>
(snip)
>
>Any help would be greatly appreciated as my wife will not like my bald head
>(I pulled out all my hair working on this little problem).
>
>Sincerely,
>Chris Lanning
I'm sure there ought to be comment about baldheaded middleaged SAS-ers
but it might be a bit too close for comfort
regards
--
Peter Crawford
|