From: Kenneth M. Lin on
Did you know that in many types of Unix windows PROC EXPORT would hang and
the program must be terminated manually. I know that you can
you -noterminal option but surely SAS could easily rewrite PROC EXPORT so
this is unnecessary.

From: data _null_; on
On Mar 24, 11:51 pm, "Kenneth M. Lin" <kenneth_m_...(a)sbcglobal.net>
wrote:
> Did you know that in many types of Unix windows PROC EXPORT would hang and
> the program must be terminated manually.  I know that you can
> you -noterminal option but surely SAS could easily rewrite PROC EXPORT so
> this is unnecessary.

These usage notes relate to your complaint. It appears that SI does
not agree.

http://support.sas.com/kb/3/610.html
http://support.sas.com/kb/19/411.html
From: Kenneth M. Lin on


"data _null_;" <datanull(a)gmail.com> wrote in message
news:f7576cef-1d78-494f-87a8-c2e32b5ec44f(a)f12g2000prn.googlegroups.com...
> On Mar 24, 11:51 pm, "Kenneth M. Lin" <kenneth_m_...(a)sbcglobal.net>
> wrote:
>> Did you know that in many types of Unix windows PROC EXPORT would hang
>> and
>> the program must be terminated manually. I know that you can
>> you -noterminal option but surely SAS could easily rewrite PROC EXPORT so
>> this is unnecessary.
>
> These usage notes relate to your complaint. It appears that SI does
> not agree.
>
> http://support.sas.com/kb/3/610.html
> http://support.sas.com/kb/19/411.html

"These procedures were originally designed to be run only in interactive
mode, and therefore expect a calling terminal. The error occurs when they
are run in batch mode because the procedures attempt to display the SAS
Session Manager icon, which requires a valid X display. "

So you are saying that SAS, with thousands of employees, cannot change
something that was "originally" designed to be run only in interactive mode?
It took me a while to figure out what was causing the problem because SAS
just locks up and won't issue any error message.

 | 
Pages: 1
Prev: why....
Next: Log File with Color in Server