Hi. If those files are "restorable" with a system command then there should be no problem to import them through a pipped command line. You just have to adjust your previous file assignment to a proper file pipe command assignment. Now, important thing is, beside providing the necessary password you need to add the flag which redirects processing to screen/console (in order to pipe the result). You'll have to find this flag in the zip command documentation you're using. On Unix using the zip command, it should look like this (-c is the flag which redirects output to screen): * flags: -c output to stdout, -q quiet mode, -P specify the password; filename myfile pipe 'unzip -cq –P mypass FILE.zip' ; data _null_;      infile myfile; * import file;      input;      put _infile_; run; Cheers from Portugal. Daniel Santos @ www.cgd.pt ... View more

Yes, %SYSGET will retrieve UNIX environment variables, and it may be all you need. Another feature is the SYSPARM macro variable which is specified when launching SAS from the command line (-sysparm "value", option). More on this here: http://support.sas.com/documentation/cdl/en/mcrolref/61885/HTML/default/viewer.htm#a000543608.htm If what you need is access to the output of a system command (ls, cat, etc) submited within SAS then take a peak on pipe file commands: http://support.sas.com/documentation/cdl/en/hostunx/63053/HTML/default/n1ceb0xedanuj3n19l3g73awk1wf.htm Cheers from Portugal! Daniel Santos @ www.cgd.pt ... View more

Now that's a big decrease in performance. If code is the same for both stats, than this could only be a dramatic increase in IO Time or Wait Time (being Real-time=CPU Time+IO Time+Wait Time). Either your not getting the same slice of CPU (as TomKari pointed) or your IO as gotten pretty worse (could be a hardware problem, configuration or change of some sort). Cheers from Portugal. Daniel Santos @ www.cgd.pt ... View more

Yes, the "mess" that is SAS macro quoting and the lack of obviousness that is choosing the right masking macro function. First there was %NR/STR, than %NR/QUOTE, after that %NR/BQUOTE was introduced, and at last %SUPER... And each one has one or more particular set of features, being: - Compile time, and runtime execution: Some operate at compile time, while the others only evaluate at runtime (nothing happens at compile time their treated as text). - percent and ampersand masking: Easy to identify, every* macro function starting with %NR will mask the % and & preventing the resolve of macro variables/functions. - unmatched single quotes, double quotes and parentheses masking: Actually all quoting functions are capable of masking unmatched single/double quotes and parentheses, but some mask them char by char while other do this by pair unless you explicitly identify the unmatched pairs prefixing the char with a percent sign (%). Every* functions starting with the form %NRB* or %B* do not need to identify unmatched pairs. * there's actually a macro quoting function that doesn't follow the rule, %SUPER, which (as the name says) is the super-mega-power-thing on macro quoting. So with that, and knowing that %STR is a compile time function and %NRBQUOTE is a runtime one. %STR will not mask percent and ampersand (no %NR prefix) and will require to identify unmatched pairs (no %B* prefix). %NRBQUOTE will mask percent and ampersand (%NR prefix) and will not require to identify unmatched pairs (%NRB* prefix). For your particular case, % and & masking is not need, and the moment of function evaluation is pretty much irrelevant (compile/runtime). So, since you have a single unmatched quote, it's pretty much a matter of choosing If you want to identify it or not. From there, you may choose one of three functions. %STR or %QUOTE, which both require the % before the single quote and differ only on execution time (compile/runtime). Or %BQUOTE, which will not require to identify the unmatched quote, and is evaluated at runtime. All suggestions above are correct, as they will solve VD's single quote problem. That being said... @Artur, %NRBQUOTE is actually more than it's needed as there is no & or % to mask, %BQUOTE is just enough. @Ksharp, for %STR there is no need to mask matched pairs(), just the unmatched single quote. Cheers from Portugal. Daniel Santos @ www.cgd.pt ... View more

I guess you already figured a valid where expression where: (weekday("&sysdate"d) = 2 and ("&sysdate"d-1) <= LAST_CHANGED between <= ("&sysdate"d-3)) or (weekday("&sysdate"d) in (3,4,5,6) and LAST_CHANGED = "&sysdate"d-1) This should extract everything you need. If LAST_CHANGED is in a date/time form, just apply the DATEPART function to extract the Date portion of it, as the "&SYSDATE" var is represented with a Date only format (DATE9.) More on DATEPART function here: http://support.sas.com/documentation/cdl/en/lrdict/64316/HTML/default/viewer.htm#a000245883.htm Cheers from Portugal. Daniel Santos @ www.cgd.pt ... View more