topic Re: PC error for sas view sashelp.vextfl in SAS Programming

PC error for sas view sashelp.vextfl

GeorgeSAS — Wed, 20 Dec 2017 18:48:29 GMT

Hello all;

I use PC SAS.

The sas view: sashelp.vextfl has problem on my pc,it shows me error when i trying to open or use it:

ERROR: Invalid Operation.
ERROR: Termination due to Floating Point Exception

Please help.

Thanks!

Re: PC error for sas view sashelp.vextfl

novinosrin — Wed, 20 Dec 2017 18:55:03 GMT

I tried opening it after:

data w;/*I opened this dataset to view the contents*/
set sashelp.vextfl ;
run;

EDIT: Sorry ignore, mine works fine.

Re: PC error for sas view sashelp.vextfl

ballardw — Wed, 20 Dec 2017 18:57:39 GMT

Please show the code of what you attempted.

That specific item is one of the system VIEWS, not a data set, and you really should be attempting to anything other than extract or view data.

This specific one keeps track of defined external files such as you would assign with a FILENAME statement.

Re: PC error for sas view sashelp.vextfl

GeorgeSAS — Wed, 20 Dec 2017 19:00:30 GMT

I just simply double click it or code like this :

data w;/*I opened this dataset to view the contents*/
set sashelp.vextfl ;
run;

same error happend:

ERROR: Invalid Operation.
ERROR: Termination due to Floating Point Exception

Thanks!

Re: PC error for sas view sashelp.vextfl

SASKiwi — Wed, 20 Dec 2017 19:00:58 GMT

If it is just your PC and not others in your organisation I would try re-installing SAS to see if that fixes it.

Re: PC error for sas view sashelp.vextfl

ChrisHemedinger — Wed, 20 Dec 2017 19:08:08 GMT

Try a PROC PRINT to see if there are some funky characters in there.

data w;/*I opened this dataset to view the contents*/
set sashelp.vextfl ;
run;
proc print data=w; run;

Re: PC error for sas view sashelp.vextfl

novinosrin — Wed, 20 Dec 2017 19:15:41 GMT

Did that, and attached here is the screen shot of proc print results

Re: PC error for sas view sashelp.vextfl

GeorgeSAS — Wed, 20 Dec 2017 19:19:44 GMT

I just realize although there was error but the dataset w was created successfully.

But if I just double click the sas view sashelp.vextfl.

It can't be opened and comes with those errors too.

To Chris,

The w dataset and its print has no problem.

also this can print it too, but has error in log:

proc sql;
select * from
sashelp.vextfl;
quit;

Thanks

Re: PC error for sas view sashelp.vextfl

GeorgeSAS — Wed, 20 Dec 2017 19:21:37 GMT

my result looks like that.

Thanks!

Re: PC error for sas view sashelp.vextfl

GeorgeSAS — Wed, 20 Dec 2017 19:22:50 GMT

1.looks the print and refer to it will get right result but come with error message.
2.double click not work to open the view

Re: PC error for sas view sashelp.vextfl

ChrisHemedinger — Wed, 20 Dec 2017 19:31:18 GMT

Try the workaround in this SAS Note.

   proc sql;
     create view work.extfiles as
     select fileref, xpath, xengine, level, directory, 'exists'n, temporary
     from dictionary.extfiles;
   quit;

Re: PC error for sas view sashelp.vextfl

ballardw — Wed, 20 Dec 2017 19:41:37 GMT

@GeorgeSAS wrote:
1.looks the print and refer to it will get right result but come with error message.
2.double click not work to open the view

Which version of SAS are you running?

And another approach would be try the SAS command box with vt sashelp.vextfl, which theoretically should be the same a clicking on the dataset/view but sometimes one never knows.

Does this also happen after restarting SAS?

Re: PC error for sas view sashelp.vextfl

GeorgeSAS — Wed, 20 Dec 2017 20:56:24 GMT

Here is the result of this:

   data _null_;
file "c:\temp\output.txt";
set extfiles;
put _all_ ; 
run;

fileref=#LN00004 xpath=TERMINAL xengine=TERMINAL level=0 directory=no exists=no temporary=yes _ERROR_=0 _N_=1
fileref=#LN00006 xpath=C:\Users\ABC123456\Documents xengine=DISK level=0 directory=yes exists=yes temporary=yes _ERROR_=0 _N_=2
fileref=#LN00008 xpath=C:\Users\ABC123456\Desktop xengine=DISK level=0 directory=yes exists=yes temporary=yes _ERROR_=0 _N_=3
fileref=#LN00014 xpath=c:\temp\extfiles.txt xengine=DISK level=0 directory=no exists=yes temporary=yes _ERROR_=0 _N_=4
fileref=_CMD xpath=net use xengine=PIPE level=0 directory=no exists=no temporary=no _ERROR_=0 _N_=5
fileref=#LN00001 xpath=C:\Program Files\SASHome\SASFoundation\9.3\core\sasmsg xengine=DISK level=1 directory=yes exists=yes temporary=yes _ERROR_=0 _N_=6
fileref=#LN00001 xpath=C:\Program Files\SASHome\SASFoundation\9.3\accelmva\sasmsg xengine=DISK level=2 directory=yes exists=yes temporary=yes _ERROR_=0 _N_=7
fileref=#LN00001 xpath=C:\Program Files\SASHome\SASFoundation\9.3\access\sasmsg xengine=DISK level=3 directory=yes exists=yes temporary=yes _ERROR_=0 _N_=8
fileref=#LN00001 xpath=C:\Program Files\SASHome\SASFoundation\9.3\af\sasmsg xengine=DISK level=4 directory=yes exists=yes temporary=yes _ERROR_=0 _N_=9
fileref=#LN00001 xpath=C:\Program Files\SASHome\SASFoundation\9.3\dmscore\sasmsg xengine=DISK level=5 directory=yes exists=yes temporary=yes _ERROR_=0 _N_=10
fileref=#LN00001 xpath=C:\Program Files\SASHome\SASFoundation\9.3\ets\sasmsg xengine=DISK level=6 directory=yes exists=yes temporary=yes _ERROR_=0 _N_=11
fileref=#LN00001 xpath=C:\Program Files\SASHome\SASFoundation\9.3\etscomp\sasmsg xengine=DISK level=7 directory=yes exists=yes temporary=yes _ERROR_=0 _N_=12
fileref=#LN00001 xpath=C:\Program Files\SASHome\SASFoundation\9.3\graph\sasmsg xengine=DISK level=8 directory=yes exists=yes temporary=yes _ERROR_=0 _N_=13
fileref=#LN00001 xpath=C:\Program Files\SASHome\SASFoundation\9.3\iml\sasmsg xengine=DISK level=9 directory=yes exists=yes temporary=yes _ERROR_=0 _N_=14
fileref=#LN00001 xpath=C:\Program Files\SASHome\SASFoundation\9.3\insight\sasmsg xengine=DISK level=10 directory=yes exists=yes temporary=yes _ERROR_=0 _N_=15
fileref=#LN00001 xpath=C:\Program Files\SASHome\SASFoundation\9.3\lab\sasmsg xengine=DISK level=11 directory=yes exists=yes temporary=yes _ERROR_=0 _N_=16
fileref=#LN00001 xpath=C:\Program Files\SASHome\SASFoundation\9.3\or\sasmsg xengine=DISK level=12 directory=yes exists=yes temporary=yes _ERROR_=0 _N_=17
fileref=#LN00001 xpath=C:\Program Files\SASHome\SASFoundation\9.3\qc\sasmsg xengine=DISK level=13 directory=yes exists=yes temporary=yes _ERROR_=0 _N_=18
fileref=#LN00001 xpath=C:\Program Files\SASHome\SASFoundation\9.3\spdsclient\sasmsg xengine=DISK level=14 directory=yes exists=yes temporary=yes _ERROR_=0 _N_=19
fileref=#LN00001 xpath=C:\Program Files\SASHome\SASFoundation\9.3\stat\sasmsg xengine=DISK level=15 directory=yes exists=yes temporary=yes _ERROR_=0 _N_=20
fileref=#LN00002 xpath=C:\Program Files\SASHome\SASFoundation\9.3\connect\saslink xengine=DISK level=0 directory=yes exists=yes temporary=yes _ERROR_=0 _N_=21
fileref=SASAUTOS xpath=C:\Program Files\SASHome\SASFoundation\9.3\core\sasmacro xengine=DISK level=1 directory=yes exists=yes temporary=no _ERROR_=0 _N_=22
fileref=SASAUTOS xpath=C:\Program Files\SASHome\SASFoundation\9.3\accelmva\sasmacro xengine=DISK level=2 directory=yes exists=yes temporary=no _ERROR_=0 _N_=23
fileref=SASAUTOS xpath=C:\Program Files\SASHome\SASFoundation\9.3\assist\sasmacro xengine=DISK level=3 directory=yes exists=yes temporary=no _ERROR_=0 _N_=24
fileref=SASAUTOS xpath=C:\Program Files\SASHome\SASFoundation\9.3\dmscore\sasmacro xengine=DISK level=4 directory=yes exists=yes temporary=no _ERROR_=0 _N_=25
fileref=SASAUTOS xpath=C:\Program Files\SASHome\SASFoundation\9.3\eis\sasmacro xengine=DISK level=5 directory=yes exists=yes temporary=no _ERROR_=0 _N_=26
fileref=SASAUTOS xpath=C:\Program Files\SASHome\SASFoundation\9.3\ets\sasmacro xengine=DISK level=6 directory=yes exists=yes temporary=no _ERROR_=0 _N_=27
fileref=SASAUTOS xpath=C:\Program Files\SASHome\SASFoundation\9.3\graph\sasmacro xengine=DISK level=7 directory=yes exists=yes temporary=no _ERROR_=0 _N_=28
fileref=SASAUTOS xpath=C:\Program Files\SASHome\SASFoundation\9.3\iml\sasmacro xengine=DISK level=8 directory=yes exists=yes temporary=no _ERROR_=0 _N_=29
fileref=SASAUTOS xpath=C:\Program Files\SASHome\SASFoundation\9.3\or\sasmacro xengine=DISK level=9 directory=yes exists=yes temporary=no _ERROR_=0 _N_=30
fileref=SASAUTOS xpath=C:\Program Files\SASHome\SASFoundation\9.3\qc\sasmacro xengine=DISK level=10 directory=yes exists=yes temporary=no _ERROR_=0 _N_=31
fileref=SASAUTOS xpath=C:\Program Files\SASHome\SASFoundation\9.3\stat\sasmacro xengine=DISK level=11 directory=yes exists=yes temporary=no _ERROR_=0 _N_=32

Re: PC error for sas view sashelp.vextfl

GeorgeSAS — Wed, 20 Dec 2017 21:15:52 GMT

PC SAS 9.3 (will be upgraded to 9.4 soon)

I tried vt sashelp.vextfl get same thing, same error log and can't open it.but thank you for teach me the magic method.

it happens after not only I restart SAS but also restart my computer

error log:

ERROR: Invalid Operation.
ERROR: Termination due to Floating Point Exception

Thanks!

Re: PC error for sas view sashelp.vextfl

GeorgeSAS — Thu, 21 Dec 2017 00:00:50 GMT

Hello Chris,

I reduce the program error range from you code: I found the error happen only when I select modate column.

if I don't select modate column will be ok.

proc sql;
create view work.extfiles2 as
select fileref, xpath, xengine, filesize,/*modate*/ level, directory, 'exists'n, temporary
from dictionary.extfiles;
quit

By the way, May I ask what is the usage of 'exists'n here? it will not work if i use the original column name exists.

Thank you!

Re: PC error for sas view sashelp.vextfl

DaveBirch — Thu, 21 Dec 2017 07:11:10 GMT

So it looks like modate is the offending variable. My guess is that the operating system or file system is passing some value like 00/00/00 to SAS. Further, I'd guess that is either the TERMINAL or the PIPE that is the offending external file. Try seeing whether WHERE XENGINE NOT IN('TERMINAL','PIPE') gets rid of the problem. You may need decide which variables/rows you really need.

Re: PC error for sas view sashelp.vextfl

GeorgeSAS — Thu, 21 Dec 2017 23:39:36 GMT

I think maybe this caused by our system is upgrading to use SAS grid. the value(modate) can't be browsed(double clicked) or assigned dynamically.

And Chris,May I ask what is the "select 'exists'n from dictionary.extfiles" used in proc sql to create view/table? why i can't use

"select exists from dictionary.extfiles"??

is that for markup the reserved keywords?

 proc sql;
     create table test111 as
     select 'exists'n as a ,exists as b
     from dictionary.extfiles;
   quit;

Thanks!

Re: PC error for sas view sashelp.vextfl

Tom — Fri, 22 Dec 2017 00:34:32 GMT

@GeorgeSAS wrote:

I think maybe this caused by our system is upgrading to use SAS grid. the value(modate) can't be browsed(double clicked) or assigned dynamically.

And Chris,May I ask what is the "select 'exists'n from dictionary.extfiles" used in proc sql to create view/table? why i can't use

"select exists from dictionary.extfiles"??

is that for markup the reserved keywords?
 proc sql;
     create table test111 as
     select 'exists'n as a ,exists as b
     from dictionary.extfiles;
   quit;
Thanks!

PROC SQL cannot figure out that you want to use EXISTS as the name of a variable and not as the SQL keyword EXISTS. By formatting your query using a name literal helps SAS understand that you mean a variable name. You can also use the DQUOTE=ANSI option on the PROC SQL statement to have SAS consider strings in double quotes as representing variable names, as is done in a number of other SQL implementations.

proc sql dquote=ansi;
  create table test111 as
     select "exists"
     from dictionary.extfiles
  ;
quit;

Re: PC error for sas view sashelp.vextfl

GeorgeSAS — Fri, 22 Dec 2017 18:24:26 GMT

I doubt about this line of the output :

fileref=_CMD xpath=net use xengine=PIPE level=0 directory=no exists=no temporary=no _ERROR_=0 _N_=5

(because if I keep modate variable,the output will be truncated just before this row, also its content looks strange than others).

Thanks!