abcd123 Tracker

Re: variable reduction in Time series

abcd123 — Thu, 17 Aug 2017 18:11:27 GMT

Thanks. Are you suggesting adding those additional variables and treat the problem as a general linear model? (BTW, what does "seasonality" mean? Is it a dummy variable?)

variable selection

abcd123 — Thu, 17 Aug 2017 16:45:22 GMT

Hello, all

I am fitting a time series model(ARIMA) and I have about 100 variables to choose from. I have tried PROC VARCLUS to reduce this number to 40, but still it is too much. Is there a way I can further reduce this number?

I know PROC GLMSELECT could be one option; however, from what I know, PROC GLMSELECT only works for general linear model. It it suitable to use PROC GLMSELECT for time series model selection?

Thank you very much.

variable reduction in Time series

abcd123 — Wed, 16 Aug 2017 16:08:25 GMT

Hello, all

I know PROC GLMSELECT could be one option; however, from what I know, PROC GLMSELECT only works for general linear model. It it suitable to use PROC GLMSELECT for time series model selection?

Thank you very much.

Re: SAS date input

abcd123 — Wed, 18 Nov 2015 19:02:16 GMT

Thank you all for help!

SAS date input

abcd123 — Wed, 18 Nov 2015 17:40:45 GMT

Hello,

I am trying to input some dates using input datatement. Here is raw data&colon;

Date

12/10/2014

1/1/2015

9/30/2015

As you can see, the date could be any length(10, 9, or 8), and as a result, mmddyy8. or mmddyy10. will not work.

Is there a way to input such mixed formated dates?

Re: first row exceed 32767, lrecl not work

abcd123 — Fri, 07 Aug 2015 21:37:18 GMT

Wow, this is exactly what I want!!! Thank you so much!!!

Re: first row exceed 32767, lrecl not work

abcd123 — Wed, 05 Aug 2015 18:09:21 GMT

Thanks, I tried to set options LRECL= 100K, however I got following error message: Option value for SAS option LRECL must be between 1 and 32767.

In addition , I checked my variable headings and all variable name length are less than 32. So it seems that it is the 32767 restriction that cause the problem.

first row exceed 32767, lrecl not work

abcd123 — Wed, 05 Aug 2015 17:13:47 GMT

Hello,

I am trying to import a csv file; first row contains variable names, and there are 10000 or so variables. My code look like following:

filename foo 'C:\Users\Desktop\aaaa_2.txt' lrecl=100000;

PROC IMPORT OUT= WORK.ABC

DATAFILE= foo

DBMS=TAB REPLACE;

GETNAMES=YES;

DATAROW=2;

RUN;

Although I specified lrecl in the code, the generated variable names are still messed (not showing correct name, but just "VAR3526", "VAR3527" etc) . Here are the log message I got:

EFI will truncate records > 32767; your record length was 100000

Number of names found is less than number of variables found.

It seems SAS still truncates after 32767 characters. Why lrecl not work?

Re: sas input selected columns

abcd123 — Tue, 04 Aug 2015 21:09:03 GMT

Thanks, Tom. This is very helpful.

sas input selected columns

abcd123 — Tue, 04 Aug 2015 17:38:02 GMT

Hello, All

I have a csv file "abc.csv", it has 5000 variables (var1-var5000, column1 through column5000), and nearly million rows. However I am only interested in var1, var1390,var3782, and var4703. I know I can do it using following code:

filename myfile "abc.csv";

data want(keep=var1 var1390 var3782 var4703);

infile myfile;

input var1-var5000;

run;

However the code do waste time inputing those un-wanted columns.

My question is: is there a way to input only wanted columns, i.e. var1, var1390,var3782, and var4703?

Re: sas proc sql pass through xml

abcd123 — Thu, 21 May 2015 18:36:30 GMT

Thanks for reply. I am sure your method would work out, but I feel there should be a more xml-like way to do the job.

sas proc sql pass through xml

abcd123 — Thu, 21 May 2015 16:24:50 GMT

Hello,

I am using proc sql pass through to extract xml data from a db2 server, the query looks like following:

select xmlquery('data($DATA/*:annotation/*:EventStart/@data)') as MyData

from db2server

The returned data is like following:

<?xml version="1.0" encoding="windows-1252" ?>1234567

But all I need is the numeric part, i.e., 1234567. How to remove the leading <?xml version="1.0" encoding="windows-1252" ?>?

Thanks.

Re: how to sepcify databse in proc sql pass through

abcd123 — Mon, 01 Sep 2014 14:15:06 GMT

Thank you all so much for helpful discussion.

Re: how to sepcify databse in proc sql pass through

abcd123 — Mon, 01 Sep 2014 02:07:32 GMT

Thanks for help.

Another question is: if I want to run a sql stored procedure, I have to use pass through (i.e., libname statement cannot run stored procedure), is this correct?

how to sepcify databse in proc sql pass through

abcd123 — Sat, 30 Aug 2014 21:29:17 GMT

hello,

the following statement runs successfully which will connect to the default database on My_DB2_Server_Name:

CONNECT TO db2 as myDB2 (datasrc=My_DB2_Server_Name user = 'MyUserName' password = 'MyPassWord');

Now I want to connect to another database; I tried following 2 methods:

CONNECT TO db2 as myDB2 (datasrc=My_DB2_Server_Name user = 'MyUserName' password = 'MyPassWord' database='AnotherDataBase');

CONNECT TO db2 as myDB2 (datasrc=My_DB2_Server_Name user = 'MyUserName' password = 'MyPassWord' schema="AnotherDataBase");

However, neither works.

I know how to do change database connection using LIBNAME; however, is there a way we can specify the databse in the pass through? Thanks for your help.

Re: proc sql query to extract value out of xml data

abcd123 — Mon, 07 Apr 2014 23:18:10 GMT

Thanks. I have figured outthe correct format of pass through for db2 server.

Re: proc sql query to extract value out of xml data

abcd123 — Mon, 07 Apr 2014 22:20:19 GMT

Thank you very much.

I have never used pass through facility. I just googled on line and try to make pass through work, but couldn't (most likely my pass through grammar is not right). The following is a workable proc sql statement. Could you please help me to write a pass through version of this statement? Thank you very much again.

libname DB2_SALES db2 datasrc = vagerdb2 user = 'hxf' password = "A2b56" schema='SALES_INFO';

proc sql;

create table test as

select * from DB2_SALES.north_region;

quit;

proc sql query to extract value out of xml data

abcd123 — Mon, 07 Apr 2014 20:40:52 GMT

Hello, all

I have a table (which is on a db2 database) with several columns. One of the column is actually xml data type. I need to extract some value out of this xml data.

I am trying to use proc sql to accomplish this job. However after I google online, it seems there is no such proc sql query for xml data.

My question is: how to extract value from xml data? is proc sql capable of this? or is there any other tool in sas?

Thanks.

Re: WARNING: The quoted string currently being processed has become more than 262 characters long

abcd123 — Wed, 26 Feb 2014 17:52:58 GMT

Thank you for help. I found out what the problem is: there are too many spaces tailoring in macro variable &file. After those spaces are removed, it worked.

WARNING: The quoted string currently being processed has become more than 262 characters long

abcd123 — Wed, 26 Feb 2014 16:31:03 GMT

Hello,all

I am trying to execute a dos command within sas:

%sysExec copy "&file" "&new_destination";

however, I got a warning message

WARNING: The quoted string currently being processed has become more than 262 characters long. You may have unbalanced quotation marks.:

Apparently, it is my macro variable &file that is too long.

I tried options NOQUOTELENMAX; the warning message is gone, however, still no file is copied to the new_destination.

Can anyone help to solve this problem? Thanks