ewgrashorn Tracker

Re: SAS Studio: Turn off matching parentheses

ewgrashorn — Wed, 20 Sep 2017 18:48:59 GMT

Thanks a lot for the reply, Samantha, and for listening to SAS Studio users.

-eric

SAS Studio: Turn off matching parentheses

ewgrashorn — Thu, 14 Sep 2017 15:41:45 GMT

Dear SAS Users,

The version of SAS Studio that I use was recently upgraded to 3.6 (full details below) and it includes a very annoying 'feature' that automatically generates a close parenthesis every time I type an open parenthesis. I cannot figure out how to turn it off. I have already turned off 'hint' and 'autocomplete' (which are also very annoying) but cannot figure out how to remove this feature. Please advise.

Thanks,

Eric

Release: 3.6 (Basic Edition)

Supported browsers:

Microsoft Internet Explorer 11
Mozilla Firefox 21+
Google Chrome 27+
Apple Safari 6.0+ (on Apple OS X)

Build date: Apr 20, 2017 3:45:50 PM
SAS Mid-tier release: Apr 18, 2017 2:38:00 PM
Java Version: 1.7.0_111
SAS release: 9.04.01M4P11092016
SAS platform: Linux LIN X64 2.6.32-696.3.2.el6.x86_64
Site name: ########
Site number: #######

Copyright © 2012-2017, SAS Institute Inc., Cary, NC, USA.

Re: ODS LISTING: WARNING: No output destinations active.

ewgrashorn — Fri, 26 Feb 2016 19:25:54 GMT

So, it turns out Reeza's solution was mostly correct. I do a lot of remote submits to an external server, so I had to do both:

ods listing;

ods results;

*AND*

rsubmit;

ods listing;

ods results;

to gt the proc means statement to run.

proc means data=sashelp.class;

run;

I wish SAS hadn't changed the ODS output settings in 9.4, they've caused me nothing but trouble.

Re: ODS LISTING: WARNING: No output destinations active.

ewgrashorn — Fri, 26 Feb 2016 13:47:03 GMT

Nope, SAS Release 9.04.01M3P062415 on WS32_7PRO

Re: ODS LISTING: WARNING: No output destinations active.

ewgrashorn — Thu, 25 Feb 2016 18:43:08 GMT

1590 ods listing;
1591 ods results;
1592 proc means data=sashelp.class;
1593 run;

WARNING: No output destinations active.

NOTE: There were 19 observations read from the data set SASHELP.CLASS.
NOTE: The PROCEDURE MEANS printed page 27.
NOTE: PROCEDURE MEANS used (Total process time):

ODS LISTING: WARNING: No output destinations active.

ewgrashorn — Thu, 25 Feb 2016 18:24:48 GMT

Dear SAS Community,

I am trying to get my output to print to the listing window instead of HTML. I am using SAS 9.4 and I have set my preferences to revert back to the SAS 9.2 way of display (under Tools/Preferences uncheck "Create HTML", uncheck "Use ODS Graphics" and check "Create Listing". Whenever I run a proc I get the "WARNING: No output destinations active." and no output anywhere.

When I run

ODS LISTING;
ODS LISTING SHOW;
Proc Means data=sashelp.class;run;

I get this output:

1587 ODS LISTING;
1588 ODS LISTING SHOW;
Current LISTING select list is set to default value (ALL).
Current OVERALL select list is: ALL
1589 Proc Means data=sashelp.class;run;

WARNING: No output destinations active.

How can I open output destinations? I thought "PROC LISTING;" was supposed to do that.

Thanks,
Eric

Re: Opening ODS listing after Closing: ODS LISTING; doesn't work

ewgrashorn — Mon, 22 Feb 2016 15:28:02 GMT

I must have done ODS NORESULTS somehow. ODS RESULTS fixed it. I don't know why I couldn't find this solution elsewhere. Thanks so much for the solution, Reeza!

Re: Opening ODS listing after Closing: ODS LISTING; doesn't work

ewgrashorn — Mon, 22 Feb 2016 15:16:13 GMT

Sorry, I should have clarified that in this session I set my preferences to revert back to the SAS 9.2 way of display (under Tools/Preferences uncheck "Create HTML", uncheck "Use ODS Graphics" and check "Create Listing". The only reason I was mucking about with all of this is I was trying to get all output to always show up in the Output window (instead of sometimes showing up in the Results Viewer.) I must have screwed things up beyond where I can fix them. One note is that nothing shows up in the Results Window (not Results Viewer, but the Results Window or Panel or whatever it is called) whenever I run a proc. The log indicates that the proc has run, but like I said, no output shows up.

Opening ODS listing after Closing: ODS LISTING; doesn't work

ewgrashorn — Fri, 19 Feb 2016 21:31:56 GMT

Hi SAS Community,

I am using SAS 9.4 and I (accidentially) closed ODS LISTING by doing "ODS _ALL_ CLOSE;" and now I can't get my output back. I have done "ODS LISTING;" and it doesn't fix it; all proc statements run but nothing shows up in the results pane and nothing appears in the output window. When I do "ods listing show;" I get this output:

2307 ods listing show;
Current LISTING select list is set to default value (ALL).
Current OVERALL select list is: NONE

Can anyone else help me?

Thanks,
Eric

Re: ERROR: Teradata row not delivered (trget): Numeric overflow occurred during computation.

ewgrashorn — Thu, 19 Mar 2015 17:44:19 GMT

But as this is a known issue, apparently, and SAS thinks that they solved it by introducing the mode=teradata. They didn't. I'm getting the error that they claim that they solved. And I stand by my assertion that "during computation" is cryptic because I wasn't doing *ANY* computations, all I was doing was pulling variables out of the database.

Re: ERROR: Teradata row not delivered (trget): Numeric overflow occurred during computation.

ewgrashorn — Thu, 19 Mar 2015 17:03:30 GMT

No Other Tom, that's the reason I posted the issue in the first place. No calculations are taking place, which makes it an especially confusing error code to have thrown. The issue must be as TomKari describes.

Re: ERROR: Teradata row not delivered (trget): Numeric overflow occurred during computation.

ewgrashorn — Thu, 19 Mar 2015 17:01:26 GMT

Yes Tom, that's the only possible answer. But doesn't it mean that there's something wrong with SAS's implementation of Teradata if the logic executes under Teradata SQL Assistant but throws such a cryptic error under SAS? And as this link inidicates:31658 - A numeric-overflow error occurs during computation with SAS/ACCESS® Interface to Teradata there are known issues with SAS's implementation. Is there any way to contact SAS development and ask them to fix this?

Re: ERROR: Teradata row not delivered (trget): Numeric overflow occurred during computation.

ewgrashorn — Thu, 19 Mar 2015 16:57:51 GMT

Hi Linus, that's a good suggestion. Unfortunately it didn't provide any further information.

ERROR: Teradata row not delivered (trget): Numeric overflow occurred during computation.

ewgrashorn — Thu, 19 Mar 2015 15:21:17 GMT

Hi SAS,

I am trying to execute a PROC SQL query to a teradata database where I only pull data (I perform no computations) but I get this error:

ERROR: Teradata row not delivered (trget): Numeric overflow occurred during computation.

I am aware of this tip:

http://support.sas.com/kb/31/658.html

But as you can see from my code snippet below, I am using teradata mode. The query works in Teradata SQL assistant. How can I get it to work in SAS?

Thanks,
Eric

proc sql;

connect to teradata (user=USERNAME password=PASSWORD

database=DATABASE server=SERVER mode=teradata connection=global);

create table alldata as select * from connection to teradata

(SELECT distinct var1, var2...

);

disconnect from teradata;

quit;

Re: Interrupt a SAS job submitted remotely

ewgrashorn — Tue, 27 Jan 2015 17:15:13 GMT

I was under the impression that it was impossible to interrupt remote processing until the process was complete, but it turns out its not true. Screen shots of the interrupt procedure are reproduced below. Note that this merely asks the remote server to stop processing "when it is convenient". It is likely that if you are doing a sql join of two large tables that it will never be "convenient" for the server to interrupt the process and you will still fill up your hard drive, but it never hurts to try.

-eric

you will see this output in the log:

NOTE: Input to SAS/CONNECT attention handler = a

ERROR: Remote submit to REMOTEID aborted by user.

Re: Need to save excel with password

ewgrashorn — Wed, 04 Dec 2013 13:34:45 GMT

Thanks Tom, that's a useful reference for the SaveAs method, but I'm more interested in the documentation of the method described in the original post, save.as In case anyone actually cares about this (which I doubt, since further searching suggests that dde has been deprecated in favor of ODS), I was able to figure out (via trial and error, which seems to be the most useful way to figure out how to use SAS) how to get save.as to work in my situation: I was having issues opening the spreadsheet created in Excel 2007 format (.xlsx), but the spreadsheet opened just fine when created in Excel 2003 format (.xls). If you find yourself coming to this post because of similar issues in opening a spreadsheet created via the save.as method, you might find this useful.

Re: Need to save excel with password

ewgrashorn — Tue, 03 Dec 2013 18:48:29 GMT

bump; I too would like to know what the options for the save.as command are (or how to find them)