Hi, Of course there will be no difference in available disk space before and after the execution, because SAS cleans up after executing (joining) and uploading the results. But you also write, you were monitoring while ETL is executing. Also it might be possible, that you have used  small datasets, and everything happened in the memory of the SAS Workspace Server. Some options that can help monitoring: options sastrace=',,,d' sastraceloc=saslog; options fullstimer; options msglevel=i; Also check the UTILLOC option. Sometimes it points to a different location than WORK. Could you attach the code that was generated by DI Studio? ... View more

If you use PROC SQL: A) No. B) Yes, on the Workspace Server. In this case LASR would act just as a simple data provider. Instead use PROC IMSTAT SCHEMA statement. Or PROC IMSTAT SCORE stement with a hash object. Or if you store tables in Hive/Impala use the hadoop/impala access engines with PROC SQL. Use native Haadoop tools. ... View more

Have you tried to use the tables that  are created by the Text Mining Nodes? Those create exactly the same tables (usually in long format, not transposed). Also, if you have ideas, I would suggest posting into:  "Text and Content Analytics" forum. (I wonder what text miners think about measuring pairwise correlations and selecting the best ~100 variables for predictive modeling.) If you have technical questions (like this one), this forum is adequate. ... View more

Hi, Segment Profile Node creates different stats and graphs about the clusters or segments. It does nothing specific for SOM/Kohonen. So, the interpretation of the Segment Profile node is the same as you would use it after a "regular" Cluster Node. SOM/Kohonen has one additional feature compared to other methods: each cluster (which corresponds to an output neuron) has a row and a column number. Clusters are forced into a grid. Every cluster will have 2 or 4 neighbors... You could visualize this grid (heat map?), maybe coloring based on number of obs, or average of some variable. It would be like a nonlinear 2D mapping of your higher dimensional data. (Remember: by default SOM initializes with a kind of linear 2D mapping based on the first 2 principal components.) ... View more

This removes the password protection from a dataset (not the library): proc datasets;    modify dataset (pw=oldpwd/);    run; quit; ... View more

Your data size and HW sizing seems to be OK. 2) Yes, you can use it without the where statement.  If you try it: can you save the table that way? ... View more

Hi, what is &secdat in your example? Is it a table sored on LASR? Are you using the SASIOLA libname engine? PROC OLIPHANT can load a table from SAS server (or a table accessible from SAS server) to SASHDAT. This is not what you need. You want to save an in-memory LASR table (SASIOLA) to disk (SASHDAT). Use IMSTAT instead. Can you share the IMSTAT code you have used? Also the libname statement that creates the libraries. What is the version of SAS you are using? What is the size (in Gbytes) of the table? How many nodes and memory do you have? ... View more

output importance= SAS/STAT(R) 13.2 User's Guide: High-Performance Procedures ... View more

Hi, Here's an example using sashelp.class (no tested throughout): proc hpsplit data=sashelp.class maxdepth=4 maxbranch=2 nodestats=arbol; /* nodestats guarda el arbol */   target sex; /* variable a predecir */   input height; /* variables en base a las q predecimos */   code file="c:\temp\model_dtree.sas"; /* guarda el modelo construido */   rules file="c:\temp\rules_dtree.txt"; /* reglas aplicadas */ run; /* Aplicar el modelo: */ data valid;   set sashelp.class;   %include "c:\temp\model_dtree.sas"; run; proc means data=valid noprint nway;   var P_SexM;   class sex;   output out=outmeans n=n; run; proc sort data=valid out=valid_sorted;   by descending P_SexF; run; data valid_cum;   if _N_=1 then do;   TP=0;FP=0;   set outmeans(where=(sex='F') keep=sex _FREQ_ rename=(_FREQ_=FN));/*initially FN=Num of females*/   set outmeans(where=(sex='M') keep=sex _FREQ_ rename=(_FREQ_=TN));/*initially TN=Num of males*/   output;   end;   set valid_sorted end=last;   TP+(sex='F');FP+(sex~='F');   FN+(-(sex='F'));TN+(-(sex~='F'));   sens=TP/(TP+FN);   _1mspec=1-(TN/(TN+FP));   output; run; proc sgplot data=valid_cum;   series x=_1mspec y=sens; run; Also check this thread: ... View more

Hi, On the below link you can find the User's Guide: High-Performance Procedures for all versions of SAS: SAS/STAT Check you version, and look at the appropriate description. It seems in SAS/STAT 14.1 HPSPIT syntax will more similar to the other SAS/STAT procedures  (class statement,  model statement). You can write the predictions of HPSPLIT to a dataset than use standard tools to  produce ROC curve (PROC SGPLOT) or CV matrix (PROC MEANS). You can also use PROC LOGISTIC with the nofit option to produce "automatically" ROC: SAS/STAT(R) 13.2 User's Guide To produce tree graphs you could: - Use PROC NETDRAW. It is part of SAS/OR (I think it is available on SAS OnDemand for Academics😞 SAS/OR(R) 13.2 User's Guide: Project Management - Calculate the layout of the tree than use lines circles, polygons, etc. to draw it (SGPLOT). Not easy. - Output the structure of the tree to a text file, than use a graph drawing tool like GraphViz. (Sorry, I know it is not available on SAS OnDemand for Academics, but if you download that text file, you can run a locally installed GraphViz on it.) - Generate interactive tree with SAS/GRAPH: SAS/GRAPH(R) 9.4: Java Applets and ActiveX Control User's Guide   (Check technical requirements here.) ... View more

For your first question: As Jaap mentioned, it is possible, that EG and EM connect to different Workspace Servers. Another possibility is that EM "does not see" metadata defined libraries, only those that are pre-assigned. When you log-in with EG pre-assigned libraries are yellow, non-pre-assigned libraries are white. It is a single click in MC to pre-assign a library. ... View more