Nothing wrong about your query, unless this part: [pre] AND WKLY_SLS_Q 0 [/pre] Which I suspect should be: [pre] AND WKLY_SLS_Q eq 0 [/pre] But it could be a typo. Everything else should work has supposed. I'm also assuming that, although you are not keeping COST_A, it does exists in work.STORE_SLS and is necessary to group the variables. Cheers from Portugal. Daniel Santos @ www.cgd.pt ... View more

Yes off course. - Match by key (implies reading both table, unless you use an index on the master table). - Append the data, then eliminate duplicated rows by key. - Keep track of the loaded keys in a smaller table, and check the table before appending data. Latest being the less resource demanding, you need to make sure that every process who updates the master table, will insert the key in the tracking table. Cheers from Portugal. Daniel Santos @ www.cgd.pt ... View more

proc STDIZE is quite a clean and effective solution to perform a "en masse" replace. For one or two isolated variables I kind like the [pre] VAR=sum(VAR,0); [/pre] instead of the if ... then syntax. Cheers from Portugal. Daniel Santos @ www.cgd.pt ... View more

From what I understand you just need to compose and issue the right system commands. There is more than a way to issue a system commando through SAS, one of which, being the X statement, See here: http://support.sas.com/documentation/cdl/en/lrdict/62618/HTML/default/a000212624.htm From there, you can run any system command that you wish. Cheers from Portugal. Daniel Santos @ www.cgd.pt ... View more

Nice job. I kind of prefer to build a convenient XML query and pass it to the METADATA procedure. Here some doc about it: http://support.sas.com/documentation/cdl/en/lrmeta/60739/HTML/default/a003177570.htm Both will do the same. METADATA procedure is best if you wish to extract a considerable amount of info from the repository(ies), since the answer is returned in a XML file (which can be imported into a SAS dataset through the XML/XMLMAP engine). Cheers from Portugal. Daniel Santos @ www.cgd.pt ... View more

I would also go with Scott's suggestion. You just need to retain the previous SALES date/time and subtract it to the next element on the group (ID). Then reset the retained value to 9:00am. Like this: [pre] data OUTDATA; length ELAPSED 8; format ELAPSED mmss5.; set INDATA; by ID; * assume INDATA is sorted by ID; drop _:; retain _AUX 8; * retain auxiliary var; if first.ID then _AUX=dhms(datepart(DATE),9,0,0); * reset auxiliary var; ELAPSED=DATE-_AUX; * calculate elapsed time; _AUX=DATE; * store current time for next iteration; run; [/pre] Cheers from Portugal. Daniel Santos @ www.cgd.pt ... View more

A good start would be starting with the Open Metadata Interface: https://support.sas.com/documentation/onlinedoc/91pdf/sasdoc_913/omd_gs_9971.pdf I have done some cool things (mainly building some stats about metadata objects) by using the interface, but what you are trying to do is completely different. Rebuilding the code directly from the Metadata Server (unless there is some pretty straightforward method for doing that!) could represent quite an effort. Cheers from Portugal. Daniel Santos @ www.cgd.pt ... View more

Theoretically yes, but I think it would involve querying the metadata server remotely. Anyway you do not need to deploy jobs one by one from DI Studio, but you probably already know that. Cheers from Portugal. Daniel Santos @ www.cgd.pt ... View more

Could you please share your code? Cheers from Portugal. Daniel Santos @ www.cgd.pt ... View more

http://www.google.com Cheers from Portugal. Daniel Santos @ www.cgd.pt ... View more

Are we talking about a SAS 9.2 installation? Because this feature is not available prior that version. Cheers from Portugal. Daniel Santos @ www.cgd.pt ... View more

Yes indeed. The appropriate way would be to include your code into the autoexec file (same directory of your sas executable, or use -autoexec comand line to specify another location). Check: http://support.sas.com/documentation/cdl/en/hostunx/61879/HTML/default/a002460936.htm And: http://support.sas.com/documentation/cdl/en/hostunx/61879/HTML/default/autoexec.htm Cheers from Portugal. Daniel Santos @ www.cgd.pt ... View more

Hi. Replace the single quotes with double quotes. Macro variables do not get resolved to their values inside single quoting. Cheers from Portugal. Daniel Santos @ www.cgd.pt ... View more

Yes. Misplaced parenthese. I did not got the time to test the code, the correct syntax would be: [pre] call symput( cats('FILELIST',put(_N_,best.)), catx(' ',symget('FILELIST'),EXTERNALNAMES) ); [/pre] Cheers from Portugal. Daniel Santos @ www.cgd.pt ... View more

First you should sort by MARK SALES, both in a descending order. [pre] proc sort data=INDATA; by descending MARK descending SALES; run; [/pre] Then, assuming that MARK will hold a value which is 0 or 1, what you want is output every element with MARK=1 and every element with MARK=0 that are first in the group (if any). This can be done using the auto variables FIRST/LAST to identify the first element of the group: [pre] data OUTDATA; set INDATA; by descending MARK; * output every MARK=1 and every first element of the group MARK=0; if MARK=1 or first.MARK; run; [/pre] Code above not tested! Cheers from Portugal. Daniel Santos @ www.cgd.pt ... View more