cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
biringstad
‎02-01-2018
  • 18 Posts
  • 0 Likes Given
  • 0 Solutions
  • 0 Likes Received

Re: Saving matrices as sas datasets when using macro and do loop (SAS ...

by Calcite | Level 5 in SAS/IML Software and Matrix Computations
‎12-14-2016 03:32 PM
‎12-14-2016 03:32 PM
Thank you for the quick reply! It made things much clearer. I solved the problem by changing the placement for END / QUIT and PROC IML. I decided to only look at one year (since not all 14 are of interest and I have limited time at the moment to discover new fancy comands), and thus also not to use a macro. The code is below, if interested.   Thank you again!   data tmpi; set iiodat.WIO; if year = 2000; run; data va; set iiodat.WVA(keep = ctr sec year tva tout); if year = 2000; run; data invgo; set invout; if year = 2000; run; data fd0; set iiodat.WFD; if year = 2000; run; data fd0; set fd0(drop=year); run; data texpfd; set iiodat.texpfgd; if year = 2000; run; data texpfd; set texpfd(drop=year); run; data texpi; set iiodat.texpint; if year = 2000; if sec = "TOT" then delete; run; data texpi; set texpi(drop=year); run; proc iml; use  tmpi(drop=year); read all var _all_ into IO; use va(keep=tout); read all var _all_ into GO; use va(keep=tva); read all var _all_ into VA; use invgo(keep = invgo); read all var _all_ into invgo; use fd0; read all var _all_ into fd0; use texpi(drop = texpi); read all var _all_ into expi; use texpfd(drop = texpfd domdmd); read all var _all_ into expf; use texpfd(keep = domdmd); read all var _all_ into dfd; use texpfd(keep = texpfd); read all var _all_ into texpf; use texpi(keep = texpi); read all var _all_ into texpi;   texp = expi + expf; A = IO#t(invgo); av = VA#(invgo); I2464 = I(2464); /*Leontief inverse*/ tcof = inv(i2464-a); store a av tcof fd0 dfd;   /* Create datasets from matrices */ create F from fd0; append from fd0; create av from av; append from av; create B from tcof; append from tcof; quit; ... View more

Saving matrices as sas datasets when using macro and do loop (SAS Univ...

by Calcite | Level 5 in SAS/IML Software and Matrix Computations
‎12-14-2016 09:31 AM
‎12-14-2016 09:31 AM
I construct 3 matrices of interest (av, fd0 and tcof / denoted V, F and B later) from 3 sas datasets (WIO, WFD and WVA) through using a macro and do loop below. I want to transform V, F and B to sas datasats in the end of the loop (highlighted in bold in the code below), but I am not able to do this. Any suggestions on what I can do to fix this?   The only error message I get in the log is: WARNING: The quoted string currently being processed has become more than 262 bytes long. You might have unbalanced quotation marks.   Also: when I try to print the matrices after running the code below (using: proc print data = F; run;) nothing happens.   Code:   %Macro trade; %do j = 2000 %to 2014; data tmpi; set iiodat.WIO; if year = &j; run;   data va; set iiodat.WVA(keep = ctr sec year tva tout); if year = &j; run;   data invgo; set invout; if year = &j; run;   data fd0(drop = year); set iiodat.WFD; if year = &j; run;   data texpfd(drop=year); set iiodat.texpfgd; if year = &j; run;   data texpi(drop = year); set iiodat.texpint; if year = &j; if sec = "TOT" then delete; run;   proc iml; use tmpi(drop=year); read all var _all_ into IO; use va(keep=tout); read all var _all_ into GO; use va(keep=tva); read all var _all_ into VA; use invgo(keep = invgo); read all var _all_ into invgo; use fd0; read all var _all_ into fd0; use texpi(drop = texpi); read all var _all_ into expi; use texpfd(drop = texpfd domdmd); read all var _all_ into expf; use texpfd(keep = domdmd); read all var _all_ into dfd; use texpfd(keep = texpfd); read all var _all_ into texpf; use texpi(keep = texpi); read all var _all_ into texpi; end;   A = IO#t(invgo); av = VA#(invgo); I2464 =I(2464);   /* lieontif inverse */ tcof = inv(i2464-a);   store a av tcof fd0;   /* I denote fd0 = F, av = V and tcof= B */ proc iml; create F from fd0; append from fd0; close F; create V from av; append from av; close V; create B from tcof; append from tcof; close B; end;   data F&i; run; data V&i; run; data B&i; run; %end; %mend trade; %trade;         Log:   1 OPTIONS NONOTES NOSTIMER NOSOURCE NOSYNTAXCHECK; 2 TITLE; 3 FOOTNOTE; 4 OPTIONS LOCALE=nb DFLANG=LOCALE; WARNING: The quoted string currently being processed has become more than 262 bytes long. You might have unbalanced quotation marks. 5 DATA _NULL_; 6 RUN; 7 OPTIONS VALIDVARNAME=V7; 8 FILENAME _HTMLOUT TEMP; 9 FILENAME _RTFOUT TEMP ENCODING='UTF-8'; 10 FILENAME _PDFOUT TEMP; 11 FILENAME _GSFNAME TEMP; 12 FILENAME _DATAOUT TEMP; 13 %LET SYSCC=0; 14 %LET _CLIENTAPP=SAS Studio; 15 %LET _CLIENTAPPVERSION=3.5; 61 &GRAPHTERM; ;*';*";*/;RUN;QUIT; ______________ 49 NOTE 49-169: The meaning of an identifier after a quoted string might change in a future SAS release. Inserting white space between a quoted string and the succeeding identifier is recommended.   16 %LET _SASPROGRAMFILE = %BQUOTE(/folders/myfolders/sasprogram4.sas); 17 %LET _BASEURL = %BQUOTE(http://localhost:10080/SASStudio/); 18 %LET _EXECENV=SASStudio; 19 DATA _NULL_; 20 CALL 20 ! SYMPUT("GRAPHINIT" _ 49 20 ! ,""); 21 CALL 21 ! SYMPUT("GRAPHTERM" _ 49 21 ! ,""); NOTE 49-169: The meaning of an identifier after a quoted string might change in a future SAS release. Inserting white space between a quoted string and the succeeding identifier is recommended.   22 RC=TSLVL('GEOCODE','N'); 23 _ERROR_=0; 24 IF (RC^=' ') THEN DO; 25 CALL SYMPUT("GRAPHINIT","GOPTIONS RESET=ALL GSFNAME=_GSFNAME;"); ___ ________________ 49 49 26 CALL SYMPUT("GRAPHTERM","GOPTIONS NOACCESSIBLE;"); ___ ___________________________________ 49 49 NOTE 49-169: The meaning of an identifier after a quoted string might change in a future SAS release. Inserting white space between a quoted string and the succeeding identifier is recommended.   27 END; 28 RUN; 29 DATA _NULL_; 30 RC=SYSPROD("PRODNUM002" _ 49 30 ! ); NOTE 49-169: The meaning of an identifier after a quoted string might change in a future SAS release. Inserting white space between a quoted string and the succeeding identifier is recommended.   31 IF (RC^=1) THEN DO; 32 CALL 32 ! SYMPUT("GRAPHINIT" _ 49 32 ! ,""); NOTE 49-169: The meaning of an identifier after a quoted string might change in a future SAS release. Inserting white space between a quoted string and the succeeding identifier is recommended.   33 CALL SYMPUT("GRAPHTERM",""); 34 END; 35 RUN; 36 %LET _DATAOUT_MIME_TYPE=; 37 %LET _DATAOUT_NAME=; 38 %LET _DATAOUT_TABLE=; 39 %LET _DATAOUT_URL=; 40 %SYMDEL _DATAOUT_MIME_TYPE _DATAOUT_NAME _DATAOUT_URL _DATAOUT_TABLE; 41 %LET _SASWS_ = %BQUOTE(/folders/myfolders); 42 %LET _SASWSTEMP_=%BQUOTE(/folders/myfolders/.images/8f8d00a9-0c97-4413-b01c-af46324a0b01) 42 ! ; WARNING: The quoted string currently being processed has become more than 262 bytes long. You might have unbalanced quotation marks. 43 ODS LISTING CLOSE; 44 OPTIONS PRINTERPATH=PDF; 45 ODS AUTONAVIGATE OFF; 46 ODS GRAPHICS ON; 47 ODS HTML5 (ID=WEB) DEVICE=PNG GPATH="&_SASWSTEMP_" ENCODING=utf8 FILE=_HTMLOUT 47 ! (TITLE='Results: sasprogram4.sas') STYLE=Htmlblue OPTIONS(BITMAP_MODE='INLINE' 47 ! SVG_MODE='INLINE' CSS_PREFIX='.ods_8f8d00a9-0c97-4413-b01c-af46324a0b01' 47 ! BODY_ID='div_8f8d00a9-0c97-4413-b01c-af46324a0b01' ); 48 ODS RTF (ID=WEB) STYLE=Rtf FILE=_RTFOUT sasdate; WARNING: The quoted string currently being processed has become more than 262 bytes long. You might have unbalanced quotation marks. 49 ODS PDF (ID=WEB) STYLE=Pearl FILE=_PDFOUT; 50 &GRAPHINIT; 51 OPTIONS FIRSTOBS=1; 52 OPTIONS OBS=MAX; 53 OPTIONS DTRESET DATE NUMBER NOTES; 54 OPTIONS NOTES STIMER SOURCE NOSYNTAXCHECK; 55 56 libname IIOdat '/folders/myfolders'; 57 58 options pagesize = 400; 59 options linesize = 100; 60 options missing = '.'; 61 62 PROC IMPORT DATAFILE="/folders/myfolders/mapfile.xlsx" 63 OUT=ctrlabel 64 DBMS=xlsx 65 REPLACE; 66 Getnames=YES; 67 sheet=ctr; 68 69 proc sort; by ctr; 70 RUN; 71 72 73 /* avoid division by zero in matrix computation */ 74 75 data invout; set iiodat.wva(keep = ctr sec year tout); 76 if tout > 0 then invgo = 1/tout; 77 else invgo = 0; 78 run; 79 80 data yearlabel(keep = ctr sec); set iiodat.wva; WARNING: The quoted string currently being processed has become more than 262 bytes long. You might have unbalanced quotation marks. 81 if year = 2000; 82 run; 83 84 /* Macro to decompose each country's gross exports at sector level */ 85 86 %Macro trade; 87 %do j = 2000 %to 2014; 88 89 data tmpi; set iiodat.WIO; 90 if year = &j; 91 run; 92 93 data va; set iiodat.WVA(keep = ctr sec year tva tout); 94 if year = &j; 95 run; 96 97 data invgo; set invout; 98 if year = &j; 99 run; 100 101 data fd0(drop = year); set iiodat.WFD; 102 if year = &j; 103 run; 104 105 data texpfd(drop=year); set iiodat.texpfgd; 106 if year = &j; 107 run; 108 109 data texpi(drop = year); set iiodat.texpint; 110 if year = &j; 111 if sec = "TOT" then delete; 112 run; 113 114 proc iml; 115 use tmpi(drop=year); 116 read all var _all_ into IO; 117 use va(keep=tout); 118 read all var _all_ into GO; 119 use va(keep=tva); 120 read all var _all_ into VA; 121 use invgo(keep = invgo); 122 read all var _all_ into invgo; 123 use fd0; 124 read all var _all_ into fd0; 125 use texpi(drop = texpi); WARNING: The quoted string currently being processed has become more than 262 bytes long. You might have unbalanced quotation marks. 126 read all var _all_ into expi; 127 use texpfd(drop = texpfd domdmd); 128 read all var _all_ into expf; 129 use texpfd(keep = domdmd); 130 read all var _all_ into dfd; 131 use texpfd(keep = texpfd); 132 read all var _all_ into texpf; 133 use texpi(keep = texpi); 134 read all var _all_ into texpi; 135 end; 136 137 texp = expi + expf; 138 139 A = IO#t(invgo); 140 av = VA#(invgo); 141 I2464 =I(2464); 142 143 /* lieontif inverse */ 144 tcof = inv(i2464-a); 145 146 store a av tcof fd0; 147 148 proc iml; 149 create F from fd0; 150 append from fd0; 151 close F; 152 create V from av; 153 append from av; 154 close V; 155 create B from tcof; 156 append from tcof; 157 close B; 158 end; 159 160 data F&i; 161 run; 162 163 data V&i; 164 run; 165 166 data B&i; 167 run; 168 169 %end; 170 %mend trade; 171 %trade; 172 173 OPTIONS NONOTES NOSTIMER NOSOURCE NOSYNTAXCHECK; 174 ODS HTML CLOSE; 175 &GRAPHTERM; ;*';*";*/;RUN;QUIT; 176 QUIT;RUN; 177 ODS HTML5 (ID=WEB) CLOSE; 178 179 ODS RTF (ID=WEB) CLOSE; 180 ODS PDF (ID=WEB) CLOSE; 181 FILENAME _GSFNAME; 182 DATA _NULL_; 183 RUN; 184 OPTIONS NOTES STIMER SOURCE SYNTAXCHECK; ... View more

Re: Multiple lengths were specified for the variable XX by input data ...

by Calcite | Level 5 in SAS Programming
‎11-30-2016 09:58 AM
‎11-30-2016 09:58 AM
Thank you for the advises. I ended up changing the code for how I imported the csv files in the beginning of the programme, where I specified the length of the character and numeric variables - It seems like that solved the truncation problem. Thus, in stead of using 'PROC IMPORT' to import multiple csv files, I used the INPUT statement to import the files. ... View more

Re: proc import csv file and missing values

by Calcite | Level 5 in SAS Procedures
‎11-30-2016 09:53 AM
‎11-30-2016 09:53 AM
Thanks a lot for the help! Now the programme (finally!) works. I ended up not typing in the names, but using the var2-var2464 names, as I found it that was sufficient. ... View more

Re: proc import csv file and missing values

by Calcite | Level 5 in SAS Procedures
‎11-28-2016 03:28 PM
‎11-28-2016 03:28 PM
Good to know, thank you!   If I have a row (say row 1) with names for all the numeric variables (var3-var2466), and I would like to include these when I import the data from the csv files, how could I include that in the code?   The names are like this: AUS, AUS_1, AUS_2, AUS_3, AUS_4, AUT, AUT_1, AUT_2, AUT_3, AUT_4 and up to ZOW, ZOW_1, ZOW_2, ZOW_3, ZOW_4. So there are 5 variables for each of 44 countries, summing to 220. ... View more

Re: proc import csv file and missing values

by Calcite | Level 5 in SAS Procedures
‎11-28-2016 01:14 PM
‎11-28-2016 01:14 PM
Yes, I do have 8 digits after comma on all the variables, could that cause a problem? The maximum length seem to have changed after including the LRECL alternative in the code. The minimum length is the same for each of the 15 files, and the maximum code varies.       Another question: If I already have names for each column in the csv file (say in the first row), would it be possible to use these names for the variables in the dataset in sas? How could I include this in the code?   (Before I have used GETNAMES when using the the PROC IMPORT statement, but here I could not make it work)   Sorry for all the questions, but I am a bit desperate after using days on this.   Thanks a lot.         ... View more

Re: proc import csv file and missing values

by Calcite | Level 5 in SAS Procedures
‎11-28-2016 08:54 AM
‎11-28-2016 08:54 AM
Thank you!   I did it like this now, so far it works.   data WIO;  length fname $200 ;  do year = 2000 to 2014 ;  fname = cats("/folders/myfolders/WIO",year,".csv");  infile csv filevar=fname dsd dlm=',' firstobs=3 truncover end=eof;  do while (not eof); length ctr $20 sec $30 var3-var2466 8; input ctr -- var2466; output; end; end; stop; run;   The two character variables are in column 1 and 2, their names can be ctr and sec, and the rest of the variables are numeric variables. What does the $20, $30 and 8 indicate? And also the $200 specification in the second line?     The log notes that the minimum length for each dataset was 27108 and the maximum record length was 32767 for each of the imported csv files. Should these two lengths be the same?   LOG example (it says the same for each of the 15 imported csv files): NOTE: The infile CSV is: Filename=/folders/myfolders/WIO2014.csv, Owner Name=root,Group Name=vboxsf, Access Permission=-rwxrwx---, Last Modified=25. november 2016 kl 08.56, File Size (bytes)=67310096   NOTE: 2472 records were read from the infile CSV. The minimum record length was 27108. The maximum record length was 32767.   ... View more

Re: proc import csv file and missing values

by Calcite | Level 5 in SAS Procedures
‎11-28-2016 05:14 AM
‎11-28-2016 05:14 AM
Your right! Maybe a stupid choice by me, but I am quite new to this. I actually thought it would be better with xlsx in stead of csv after reading your advise, but I was very wrong I guess. Now I am trying with csv and another code (see above). ... View more

Re: proc import csv file and missing values

by Calcite | Level 5 in SAS Procedures
‎11-28-2016 05:12 AM
‎11-28-2016 05:12 AM
Thank you.   I tried this code now, including STOP; right before END;, and it works okey.   My first two variables are character variables, how do I specify that in the code?   Birgitte     ... View more

warning: multiple lengths were specified for variable X

by Calcite | Level 5 in SAS Programming
‎11-27-2016 05:45 PM
‎11-27-2016 05:45 PM
When I try to transform a work.dataset to a sas.dataset I get the following warning:   WARNING: Multiple lengths were specified for the variable JU by input data set(s). This can cause truncation of data.   The work data set (WIO) consists of 2467 columns and 36960 rows. The library reference is IIOdat.   Code: %macro setlist; %do i=2000 %to 2014; WIO&i %end; %mend setlist; data IIOdat.WIO; set %setlist; run;   Log: 56 %macro setlist; 57 %do i=2000 %to 2014; 58 WIO&i 59 %end; 60 %mend setlist; 61 62 data IIOdat.WIO; 63 set %setlist; 64 run;   WARNING: Multiple lengths were specified for the variable JU by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable OC by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable SK by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable UO by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable ABA by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable AFI by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable AJQ by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable ALU by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable AQC by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable AUG by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable AWO by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable AYS by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable BAW by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable BFE by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable BHI by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable BJM by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable BNI by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable BNM by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable BNU by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable BSC by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable BWK by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable CHE by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable CJI by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable CNL by input data set(s). This can cause truncation of data. NOTE: There were 2464 observations read from the data set WORK.WIO2000. NOTE: There were 2464 observations read from the data set WORK.WIO2001. NOTE: There were 2464 observations read from the data set WORK.WIO2002. NOTE: There were 2464 observations read from the data set WORK.WIO2003. NOTE: There were 2464 observations read from the data set WORK.WIO2004. NOTE: There were 2464 observations read from the data set WORK.WIO2005. NOTE: There were 2464 observations read from the data set WORK.WIO2006. NOTE: There were 2464 observations read from the data set WORK.WIO2007. NOTE: There were 2464 observations read from the data set WORK.WIO2008. NOTE: There were 2464 observations read from the data set WORK.WIO2009. NOTE: There were 2464 observations read from the data set WORK.WIO2010. NOTE: There were 2464 observations read from the data set WORK.WIO2011. NOTE: There were 2464 observations read from the data set WORK.WIO2012. NOTE: There were 2464 observations read from the data set WORK.WIO2013. NOTE: There were 2464 observations read from the data set WORK.WIO2014. NOTE: The data set IIODAT.WIO has 36960 observations and 2467 variables. NOTE: DATA statement used (Total process time): real time 48.26 seconds cpu time 20.61 seconds   What does this mean, and what can I do with it?   All help is very appreciated. ... View more

Multiple lengths were specified for the variable XX by input data set(...

by Calcite | Level 5 in SAS Programming
‎11-27-2016 05:29 PM
‎11-27-2016 05:29 PM
When I try to save a work.dataset as a sas.dataset I get the following warning message:   Multiple lengths were specified for the variable X by input data set(s). This can cause truncation of data.   The dataset (WIO) has 2467 columns (C, D, E etc.) and 36960 rows. IIOdat is the library.   Code: %macro setlist; %do i=2000 %to 2014; WIO&i %end; %mend setlist; data IIOdat.WIO; set %setlist; run;   Log: 58 %macro setlist; 59 %do i=2000 %to 2014; 60 WIO&i 61 %end; 62 %mend setlist; 63 64 data IIOdat.WIO; 65 set %setlist; 66 run;   WARNING: Multiple lengths were specified for the variable JU by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable OC by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable SK by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable UO by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable ABA by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable AFI by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable AJQ by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable ALU by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable AQC by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable AUG by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable AWO by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable AYS by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable BAW by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable BFE by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable BHI by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable BJM by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable BNI by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable BNM by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable BNU by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable BSC by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable BWK by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable CHE by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable CJI by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable CNL by input data set(s). This can cause truncation of data. NOTE: There were 2464 observations read from the data set WORK.WIO2000. NOTE: There were 2464 observations read from the data set WORK.WIO2001. NOTE: There were 2464 observations read from the data set WORK.WIO2002. NOTE: There were 2464 observations read from the data set WORK.WIO2003. NOTE: There were 2464 observations read from the data set WORK.WIO2004. NOTE: There were 2464 observations read from the data set WORK.WIO2005. NOTE: There were 2464 observations read from the data set WORK.WIO2006. NOTE: There were 2464 observations read from the data set WORK.WIO2007. NOTE: There were 2464 observations read from the data set WORK.WIO2008. NOTE: There were 2464 observations read from the data set WORK.WIO2009. NOTE: There were 2464 observations read from the data set WORK.WIO2010. NOTE: There were 2464 observations read from the data set WORK.WIO2011. NOTE: There were 2464 observations read from the data set WORK.WIO2012. NOTE: There were 2464 observations read from the data set WORK.WIO2013. NOTE: There were 2464 observations read from the data set WORK.WIO2014. NOTE: The data set IIODAT.WIO has 36960 observations and 2467 variables. NOTE: DATA statement used (Total process time): real time 35.36 seconds cpu time 11.51 seconds     What does this mean, and what can I do to fix it?   All help is very appreciated!!   ... View more

Re: proc import csv file and missing values

by Calcite | Level 5 in SAS Procedures
‎11-27-2016 05:12 PM
‎11-27-2016 05:12 PM
Thank you for the advises. I ended up saving the dataset in a xlsx file (each table in a seperate sheet) in stead of a csv file for each table, and now it works okay, but the programme runs much slower.   The commands: Proc import datafile="/folders/myfolders/WIO.xlsx" OUT=WIO&i DBMS=XLSX REPLACE; Getnames=no; sheet=WIO&i; RUN;  ... View more

proc import csv file and missing values

by Calcite | Level 5 in SAS Procedures
‎11-25-2016 05:33 AM
‎11-25-2016 05:33 AM
  Hello,   When I use 'proc import' to import csv files into SAS some observations become missing (these are not missing in the original csv files). Each csv file has 2474 rows and 2466 columns. It is several observations in the bottom right of the excel table that becomes missing.   Below is the commands I use.   I am trying to import 14 csv files by using a macro (data starting on row 3), and some missing observations (in the bottom right of the table) appears in all 14 of them.   It is not reported anything about this in the log.   %macro readdat; %do i = 2000 %to 2014; PROC IMPORT datafile="/folders/myfolders/WIO&i..csv" OUT=WIO&i DBMS=DLM REPLACE; DELIMITER='2C'x; Getnames=NO; Datarow=3; RUN; ...   %end; %mend readdat; %readdat;   What could be the problem? Help is very appreciated!     Best, Birgitte Ringstad                 ... View more

Export multiple SAS datasets into sheets in one excel file (in SAS Uni...

by Calcite | Level 5 in SAS Procedures
‎09-29-2016 02:24 PM
‎09-29-2016 02:24 PM
I am trying to export multiple sas datasets (gbotall, vabotall, vxrall) into one sheet each in one xlsx file (wiodvatrd), but I receive the error: ERROR: FILE= or TABLE= is required and must be specified.   I am using the SAS University Edition. So far I have tried with different codes, and below is one of them and parts its log. Do anyone see what I am doing wrong?   Code: PROC EXPORT DATA= myfolder.GBOTall DBMS=xlsx replace; sheet= "gbotall"; OUTFILE= "/folders/myfolders/WIODVATRD.xlsx"; RUN;   PROC EXPORT DATA= myfolder.VABOTall DBMS=xlsx replace; sheet= "vabotall"; OUTFILE= "/folders/myfolders/WIODVATRD.xlsx"; RUN;   PROC EXPORT DATA= myfolder.vxrall dbms=xlsx replace; sheet= "vxrall"; OUTFILE= "/folders/myfolders/WIODVATRD.xlsx"; RUN;    Log:  1          OPTIONS NONOTES NOSTIMER NOSOURCE NOSYNTAXCHECK;  55          56         PROC EXPORT DATA= myfolder.GBOTall DBMS=xlsx replace;  ERROR: FILE= or TABLE= is required and must be specified.  NOTE: The SAS System stopped processing this step because of errors.  NOTE: PROCEDURE EXPORT used (Total process time):        real time           0.00 seconds        cpu time            0.00 seconds         57         sheet= "gbotall";  58         OUTFILE= "/folders/myfolders/WIODVATRD.xlsx";  59         RUN;  60    Best regards, Birgitte ... View more

Re: Error: (execution) Invalid subscript or subscript out of range

by Calcite | Level 5 in SAS/IML Software and Matrix Computations
‎09-26-2016 01:44 PM
‎09-26-2016 01:44 PM
Thank you!   Indeed, I think that was the problem. I discovered that I made a mistake initially when I made the dataset (WFD) that I use to create the FD matrix, and therefore I had a smaller column range than planned. When I changed it to the correct one the code above worked.   Birgitte ... View more
Contact Me
Online Status
Offline
Date Last Visited
‎02-01-2018 05:18 AM
Quick links