Date:         Mon, 23 Apr 2001 11:20:54 -0700
Reply-To:     Pamela Mery <pmery@CCSF.CC.CA.US>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Pamela Mery <pmery@CCSF.CC.CA.US>
Subject:      Re: X display error on UNIX (fwd)
Comments: To: sas <sas-l@uga.cc.uga.edu>
Comments: cc: Dan Lewis <dan.lewis@barclaysglobal.com>,
          "Gregg P. Snell" <gsnell@DATASAVANTCONSULTING.COM>,
          Jonathan Goldberg <jonathan@matlock.wustl.edu>,
          "Karsten M. Self" <kmself@ix.netcom.com>,
          Niels Stout <n.stout@HETNET.NL>, "Xu, Meifen" <mxu@amgen.com>
Content-Type: TEXT/PLAIN; charset=US-ASCII

Thanks to Dan, Gregg, Jonathan, Karsten, Niels and Meifen for their help
and suggestions on my import / X display error on UNIX.

After trying a number of things, Gregg had a successful solution: using
the -noterminal option in batch mode, my program ran without error.  ("I
have also found it VERY beneficial (when running in batch on unix) to
include the -noterminal option.  This will prevent certain proc's from
attempting to open an x window during execution.")  BTW, setting the
terminal type to vt100 did *not* work-- many options including -nodms,
-nofsdevice, -noconfig were tried to no effect.  Only -noterminal allowed
the job to run successfully.  (Meifen, I am importing a tab-delimited
file-- it is possible!)


Karsten suggested that there may be some parameters in the global setup
sasv8.cfg that could be changed.  The following items seem suspect.  If I
had the authority, I'd eliminate them to see if my program ran
successfully in their absence.  Unfortunately I'd have to go through the
system admin, thus I am content with the workaround above.  Possible
problem items:

> -dmsexp
> -setjmp


Finally, Jonathan suggested setting up an explicit X session.  I may try
this just for fun:

"About X on the PC:  running in this mode, SAS is executed on the server
(I assume a UNIX machine) and displays on the PC.  To do this, the PC must
supply graphical display services to the UNIX box.  Hence, there are two
servers;  the UNIX box is the SAS server, running SAS, which the PC is the
X windows server, running X display software.

X display software is not native to Windows (although it is available
native on every UNIX of which I am aware).  You need to get 3rd party
software.  That is why I said "If the PC has X server software".

The most common X package for X for Windows is Exceed, from Hummingbird
Communications:

http://www.hummingbird.com/products/nc/exceed/

I've used it with good results.  Here, we use Solstice Client, from
Sun.  It's out of support, but works, and is free.

Since SAS runs on the UNIX machine, you don't need PC SAS to run this
way.  That is the advantage of the setup.  The fact that SAS (or any
program that uses X display services, which is just about any UNIX program
that uses a graphical user interface)  can be told to display on any
machine on the network, without any special coding, is a great strength of
the UNIX software model."


-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
      Pamela M. Mery       Research & Planning          Room C233
City College of San Francisco  50 Phelan Avenue  San Francisco, CA 94112
  E-mail:pmery@ccsf.cc.ca.us  Phone:415.239.3227   Fax:415.239.3010

                       ** BE AN ORGAN DONOR **
                        * sign a donor card *

         For more information lookup http://www.transweb.org
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --