About Tom

marieK · ‎09-16-2011

thanks for your answers..our problem has been solved from alone over night. it might have been just a server-problem?! runtime is now the same with and without macro.

xz · ‎11-18-2011

Bruce, I experienced the same thing on Windows 7. The fix is quite simple: select any *.sas and right click then select open with. In the “open with” menu, select “The SAS System for Windows” instead of “SAS 9.2 for Windows”. Then we saw the *.sas icon changed from the SAS 9.2 grey-and-yellow downward triangle to the usual text-pad-black-person submit image. All the “Batch submit” options are now available when I right-click on a SAS file. “The SAS system for Windows” is a Windows application that integrate SAS options with Windows menu. Previously, I set “SAS 9.2 for Windows” as the default program to open *.sas files, and the right-click menu didn't have "batch submit".

Liangck · ‎10-11-2011

thanks tim, i actually doing the similar way u suggest.. liangck

jerry898969 · ‎09-13-2011

Thank you to everyone for your suggestions. I used Tom and Art's suggestions.

FriedEgg · ‎09-12-2011

Thanks _null_, I had forgotten about that option. /* create some dummy files */ data _null_; do i=1 to 3; call execute('filename file' || strip(i) || ' "/home/friedegg/file' || strip(i) || '.txt";'); call execute('data _null_;'); call execute(' file file' || strip(i) || ';'); call execute(' put "a b c d e";'); call execute(' put "f g h i j";'); call execute('run;'); end; run; filename indata '/home/mkastin/file*.txt'; data want; length _file _filex $512; infile indata eov=_firstrec_; input (blah1-blah5) (:$1.); if _n_ or _firstrec_ then delete; /* _firstrec_ will =1 for all files first record except the first */ run; /* remove this junk */ data _null_; do i=1 to 3; call execute('x "rm -f /home/friedegg/file' || strip(i) || '.txt";'); end; run;

FriedEgg · ‎09-12-2011

First the program would need to utilize unix style EOL characters or \n would need to properly identify the correct EOL. You can preprocess by converting from dos2unix dos2unix mymacro.sas tr -s "\n" mymacro.sas > mymacro_new.sas tr will squeeze (-s) duplicate apperances of the EOL char ("\n") and leave single apperances intact.

Cynthia_sas · ‎12-20-2012

Hi: When you have a local copy of SAS and do a %INCLUDE, you can include code snippets, or whole programs from your computer's drive or from a shared drive. When you run a stored process, first your stored process does NOT run on your local machine. It runs on a Stored Process Server or a Workspace Server. So when you have a stored process which contains a %INCLUDE, the Platform configuration process has some directories that are recommended down in the Lev1/SASEnvironment folder -- one directory is for autocall macros, another directory is for format libraries and a third directory is for SASCode, such as you might %INCLUDE. In your local session, you, as a programmer can write a program which will include code from any machine that your SAS session can get to. However in a stored process you don't, technically, have a "session" under your personal control, you request a stored process to execute and in the metadata, the appropriate server session is started up, but you really don't have a chance to see anything going on in the session. If your stored process has a%INCLUDE, it cannot use code on your local C drive. It must do the %INCLUDE from a location that is known to the server where the stored process will be running. The Platform config provides you this location. Conceptually, %INCLUDE will include code in both scenarios. Where SAS is running will make a difference in how you build the %INCLUDE reference. cynthia

Filipvdr · ‎09-02-2011

@Art: I didnt post all my code. My XML is generated fine, I just have a problem with the orange part I want to solve. @FriedEgg: I want really specific XML which i think can not be generated by a proc print or something else. @Peter C.: I work with 9.1.3 here. At other project I worked indeed with XML Libname engine, but not here because i really need specific XML @Tom: your reply is a possible answer to my question, i'm going to try it out now.. EDIT: Tom, I created my own VLIST: 'ProcessPlan','MainTool','user_id','Wafers_1','RecipeName_1','RecipeValue_1','RecipeName_2','Recip eValue_2','RecipeName_3','RecipeValue_3','RecipeName_4','RecipeValue_4','RecipeRptName_1','RecipeR ptValue_1','RecipeRptName_2','RecipeRptValue_2','RecipeRptName_3','RecipeRptValue_3','RecipeRptNam e_4','RecipeRptValue_4','RecipeRptName_5','RecipeRptValue_5','StepServices_1','StepServices_2','St epServices_3','StepServices_4','StepServices_5','col_ins_id','sstrMainStep','sstrCycleTimeExpected ','sstrReleaseStatus','RecipeParameters_1','RecipeParameters_2','RecipeParameters_3','RecipeParame ters_4' When i want to loop through the list it seems to cut these long parameternames somehow, any idea what this could be? Variable like ProcessPlan, Maintool, User all goes ok till Recipename_1.. EDIT: Solution: Adding a format for _name Thanks Tom!

FriedEgg · ‎09-08-2011

14 %macro layout; 15 #1 @1 mynum1 ??myfmt. 16 #1 @3 mychar $char2. 17 #2 @3 mynum2 ??myfmt. 18 %mend; 19 20 proc format; 21 invalue myfmt (default=2) 22 0 = 88 23 99 = .U 24 other = _same_; NOTE: Informat MYFMT is already on the library. NOTE: Informat MYFMT has been output. 25 run; NOTE: PROCEDURE FORMAT used (Total process time): real time 0.00 seconds cpu time 0.00 seconds 26 27 data fake; 28 input %layout; 29 cards; NOTE: The data set WORK.FAKE has 0 observations and 3 variables. NOTE: DATA statement used (Total process time): real time 0.00 seconds cpu time 0.00 seconds 30 ; 31 run; 32 33 proc sql noprint; 34 select 'if ' !! strip(name) !! '=. then ' !! strip(name) !! '=.U' into :missingn separated by '; ' 35 from sashelp.vcolumn 36 where libname='WORK' and memname='FAKE' and type='num'; 37 select 'if ' !! strip(name) !! '="" then ' !! strip(name) !! '="U"' into :missingc separated by '; ' 38 from sashelp.vcolumn 39 where libname='WORK' and memname='FAKE' and type='char'; 40 run; NOTE: PROC SQL statements are executed immediately; The RUN statement has no effect. 41 2 The SAS System 09:36 Thursday, September 8, 2011 NOTE: PROCEDURE SQL used (Total process time): real time 0.00 seconds cpu time 0.00 seconds 42 data _null_; 43 input #1 @1 orig1 $2. 44 #2 @3 orig2 $2. 45 %layout; 46 &missingn; 47 &missingc; 48 put orig1= mynum1= mychar= orig2= mynum2=; 49 cards; orig1=1 mynum1=1 mychar=A orig2=9 mynum2=9 orig1=99 mynum1=U mychar=C orig2=88 mynum2=88 orig1=62 mynum1=62 mychar=E orig2=/ mynum2=U orig1=[ mynum1=U mychar=[ orig2=}} mynum2=U orig1=.A mynum1=A mychar=. orig2=.C mynum2=C NOTE: DATA statement used (Total process time): real time 0.00 seconds cpu time 0.00 seconds 60 ; 61 run; 62 63 %put NOTE: Missingn == %bquote(&missingn); NOTE: Missingn == if mynum1=. then mynum1=.U; if mynum2=. then mynum2=.U 64 %put NOTE: Missingc == %bquote(&missingc); NOTE: Missingc == if mychar="" then mychar="U"

Peter_C · ‎08-31-2011

FriedEgg wrote: I have never experienced a behavior like you described with PROC FORMAT, do you have any links to provide me with some refernece to read on the issue? nope sorry FriedEgg, I have no link nor current evidence. But some releases-ago, an error popped up from a mixture of cntlin, cntlout and select statements that were unable to find the target member. I ran it several times to be sure. It may be a defect that has been removed since then, but I am cautious with that PROC (while it is still one of my favourites)

ScottBass · ‎09-07-2011

Or even: data have; input name $20.; datalines; SAW_PRICE_STD XYZ_STD ABC_STD_DEF std_123 xxx_std MIKE ABCDEFGHI ; run; data want; set have; new=prxchange("s/_STD$//io",-1,trim(name)); run; I'm really learning to like the PRX* functions...

data_null__ · ‎08-29-2011

Look in the PROC REPORT documentation at the SPLIT= option. Notice the default. Then think about your define statement.

Tom · ‎08-30-2011

If your input fields are all numbers then you can use data step logic to do it without macro code. Create an array of the target variables and another with the expected length of each variable. Then loop over the arrays keeping your own pointer into the input buffer. You can adjust the length depending on whether the value starts with a minus sign. data out; array var f1-f6 ; array len (6) _temporary_ (6*4) ; input @; col=1; do _n_ = 1 to dim(var); neg=substr(_infile_,col,1)='-'; var(_n_)=input(substr(_infile_,col,len(_n_)+neg),best.); col+len(_n_)+neg; end; drop col neg ; put (var(*)) (best6.); cards; 0.1 0.2 0.3 0.4 0.5 0.6 OK 0.110.220.330.440.550.66 OK 0.11-0.220.330.440.550.66 f2 shifts by 1 0.11-0.220.33-0.440.550.66 f2, f4 each adds 1 0.11-0.22-0.33-0.44-0.55-0.66 f2, f3, f4, f5, f6 all adds 1 -0.11-0.22-0.33-0.44-0.55-0.66 everything is wider by 1 -0.11-0.220.33-0.440.55-0.66 ; 0.1 0.2 0.3 0.4 0.5 0.6 0.11 0.22 0.33 0.44 0.55 0.66 0.11 -0.22 0.33 0.44 0.55 0.66 0.11 -0.22 0.33 -0.44 0.55 0.66 0.11 -0.22 -0.33 -0.44 -0.55 -0.66 -0.11 -0.22 -0.33 -0.44 -0.55 -0.66 -0.11 -0.22 0.33 -0.44 0.55 -0.66

Tom · ‎08-24-2011

It does not look like the psftp program does what you want it to do. You can test that by taking SAS out of the problem and issuing the proposed command from a DOS prompt. I think it would be much easier to use SAS to write the script for psftp than to depend on an external file. But you could use an external file as a model for the script that SAS would write. The datastep below will replace all references to '%1' with the actual directory. %let sdir=d:\raj ; filename script temp; data _null_; infile 'abc.bat' ; file script; input; _infile_ = tranwrd(_infile_,'%1',"&sdir"); put _infile_; run; %sysexec psftp.exe username@hostname -p portnumber(22) -pw password -batch -b %sysfunc(pathname(script)) ;

R_A_G_ · ‎08-21-2011

Thank you art297 it worked beautifully

Online Status	Offline
Date Last Visited	yesterday