Date:         Thu, 16 Dec 2004 10:13:19 -0800
Reply-To:     cassell.david@EPAMAIL.EPA.GOV
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         "David L. Cassell" <cassell.david@EPAMAIL.EPA.GOV>
Subject:      Re: Proc Import on Unix
In-Reply-To:  <f3ed116f04121606446463821c@mail.gmail.com>
Content-type: text/plain; charset=US-ASCII

bruce johnson <chimanbj@GMAIL.COM> wrote:
> I'm running a job that requires the use of proc import.  I'm running
> on a Unix-based system (SAS 8.2).  The problem is that when I run the
> job in batch, it tries to start an X-Window session and crashes when
> I'm using an emulator that is text based (NetTerm) and cannot start an
> X-Window session.  I can run this job on another emulator that can
> start an X-window session.
>
> I tried running this job with a -nodms option, but the X-window
> session still began.  Is there a way to get around this?  The file I'm
> trying to convert has 87 columns, but no column headers, so Proc
> Import is the optimal tool for this conversion.

There's nothing wrong with using PROC IMPORT.  The problem isn't really
the
proc, anyway.  It's your command line for running SAS in batch.  -nodms
only stops SAS from making the Display Manager active.  You need to use
-noterminal, which will tell SAS not to try to attach a terminal.  It
will
also keep requestor windows from displaying.

Now you're no longer the Terminal Man.  :-)

David
--
David Cassell, CSC
Cassell.David@epa.gov
Senior computing specialist
mathematical statistician