Your path should look like this:
/SASBIWS/rest/storedProcesses/EOT4MAC/stp_02_ws
Where
Red is the base name to call the stored process passing the parameters as XML, like in your first screenshot
In blue is the full pathname to the stored process
Have a look at the doc here:
http://support.sas.com/documentation/cdl/en/wbsvcdg/64883/HTML/default/viewer.htm#n1wblekhip1yrln1fv2s5b6a2d9f.htm
Bruno
... View more
Are you using RECFM=N to read the file. If yes there are no records as the file is just a long string of bytes.
Does the file have just 3 data values and this group of values repeats till the end of the file, or are their many more different data values. Do you have "record layout" of the data values?
If you run the following code (with your file) what does the log file look like:
data test;
infile "yourfile" ;
input char $1.;
run;
... View more
Some code change make it work, data values in the DATA Step where delimited by a tab char changed to comma.
Add another join condition for the id.
data have;
infile cards dlm=",";
input id time value $;
datalines;
1,86,A
1,87,B
1,88,C
1,89,D
1,90,E
2,86,D
2,87,E
2,88,A
2,89,C
2,90,B
;
run;
proc sql;
create table want as
select
have1.*
, case
when have2.time is null then have1.time+1
else have2.time
end as time_1
, case
when have2.value is null then "n/a"
else have2.value
end as value_1
from
have have1
left join
have have2
on
have1.id = have2.id
and have1.time=have2.time-1
order by
have1.id
,have1.time
;
quit;
... View more
This blog entry http://blogs.sas.com/content/sasdummy/2012/03/20/sas-program-by-processing/ by @ChrisHemedinger shows a very good example of a programming pattern executing the same code but with different values for certain statements and options.
In your case, you would list all the different values for macro vars x1 - x3 in a SAS data set in one variable.
You can also use the following macro sample to work through a list:
%macro iterator(valueList=);
%local i value;
%let i = 1;
%let value = %scan(&valueList, &i);
%do %while( &value ne );
%put NOTE: &sysmacroname processing &=value;
/* do something here, your SAS code */
%let i = %eval(&i + 1);
%let value = %scan(&valueList, &i);
%end;
%mend;
%iterator(valueList=ID Time Place)
... View more
I would talk with your Hadoop person, why the drop table tablename does not delete a managed table HDFS data.
Maybe you also need to contact SAS Tech Support for further analysis.
To work around this, use the SQL Passthrough drop table tablename PURGE as this does everything.
Bruno
... View more
So I suggest to do the following:
Create program nodes that contain your desired code and package it into a macro, somthing like
%macro sql01;
proc sql;
...
quit;
%mend;
Create a a control program that will look like this:
%sql01
%sql02
%sql03
In this way, you still have your smaller units, for editing etc. and you have your final control program that calls all the macros in the appropriate sequence, maybe even with parameters.
Bruno
... View more
In general when you want to do something like this, I recommend to follow these principles:
All analysis variable have an alias (varname=alias), this allows to use the same var more than once, for instance because you need more than one statistic. Also it has the advantage, that you can use the alias name whereever you need this variable name: DEFINE statement, CALL DEFINE routine, assignment statement etc.
Add a computed column at the very end of your COLUMN statement and set the NOPRINT option in the DEFINE statement. You can now code everything you need in the compute block of this computed column. Since it is at the end of the column list, it can access all the variable values to the left.
The code below illustrates this.
data mycars;
set sashelp.cars(obs=10);
if mod(_n_, 3) then do;
msrp = invoice;
end;
run;
proc report data=myCars;
column make model invoice=inv2 msrp=msrp2 _dummy;
define make / display;
define model / display;
define inv2 / analysis sum;
define msrp2 / analysis sum;
define _dummy / computed noprint;
compute _dummy;
if msrp2 > inv2 then do;
call define("msrp2", "style", "style={background=gold}");
call define("inv2", "style", "style={background=cx88e55c}");
end;
endcomp;
run;
Bruno
... View more
For every program node in the processflow. SAS Enterprise Guide does add some code at the beginning and at the end, see sample below:
1 ;*';*";*/;quit;run;
2 OPTIONS PAGENO=MIN;
3 %LET _CLIENTTASKLABEL='Program';
4 %LET _CLIENTPROCESSFLOWNAME='Process Flow';
5 %LET _CLIENTPROJECTPATH='';
6 %LET _CLIENTPROJECTPATHHOST='';
7 %LET _CLIENTPROJECTNAME='';
8 %LET _SASPROGRAMFILE='';
9 %LET _SASPROGRAMFILEHOST='';
10
11 ODS _ALL_ CLOSE;
12 OPTIONS DEV=PNG;
13 GOPTIONS XPIXELS=0 YPIXELS=0;
14
15 GOPTIONS ACCESSIBLE;
16 /* my code */
17
18 GOPTIONS NOACCESSIBLE;
19 %LET _CLIENTTASKLABEL=;
20 %LET _CLIENTPROCESSFLOWNAME=;
21 %LET _CLIENTPROJECTPATH=;
22 %LET _CLIENTPROJECTPATHHOST=;
23 %LET _CLIENTPROJECTNAME=;
24 %LET _SASPROGRAMFILE=;
25 %LET _SASPROGRAMFILEHOST=;
26
27 ;*';*";*/;quit;run;
28 ODS _ALL_ CLOSE;
29
30
31 QUIT; RUN;
So you can not have a program node with just the "%macro a;", does not make sense.
Why do you need to package all the SQL into a macro?
Within a processflow you can connect the various program (your individual Proc SQL) nodes in a specific sequence and run the complete branch.
... View more
Hi
To read a file that has LF, x"0a" as part of their data value, you can use the option TERMSTR=CRLF, this was alread metioned.
If you are using SAS Enterprise Guide, by default you will not see the text that comes after the LF. Better do a Proc PRINT from your data.
The following code:
filename xcsv "c:\temp\sample.csv" termstr=crlf;
proc import file=xcsv out=want dbms=csv replace ;
run;
proc print data=want;
run;
Will read a file that looks like this:
... View more
What kind of output format do you need to create: HTML, PDF, CSV,...?
If it is PDF, there is a way for Proc REPORT to do this using a group var that changes for every row.
See sample below.
data myclass;
gName + 1;
set sashelp.class;
run;
filename xpdf temp;
ods pdf file=xpdf;
ods pdf startpage=no;
proc report data=myClass nocenter;
column gName name sex age;
define gName / group noprint;
define name / display;
define sex / display;
define age / display;
break after gname / page;
compute before gname / style={just=left};
length printLine $ 80;
printLine = catx(":", "Line for", gName);
line printLine $char80.;
endcomp;
run;
ods pdf close;
So depending on what you need there might be a different approach.
Bruno
... View more
