Piggybacking on @Ksharp's code here an option which modifies the master data set in place. data master; set sashelp.class; run; data trans; length name $ 8 sex $ 1; /* updates */ name='Robert'; sex='N'; output; name='Thomas'; sex='A'; output; /* inserts */ name='Ksharp'; sex='M'; output; run; data master(drop=_:); modify master end=last; if _n_=1 then do; dcl hash h1(dataset:'trans'); dcl hiter hh1('h1'); _rc=h1.defineKey('Name'); _rc=h1.defineData(all:'y'); _rc=h1.defineDone(); end; /* updates */ if h1.find()=0 then do; replace; _rc=h1.remove(); end; /* inserts */ if last then do; _rc = hh1.first(); do while (_rc = 0); output; _rc = hh1.next(); end; end; run; Please Note that for the Insert case all values for variables which only exist in the Master dataset but not in the Transaction dataset get retained (which is of course wrong). If you don't have all variables in your transaction dataset then you need to use a "call missing()" for the Insert case for all variables which only exist in the master dataset. ... View more

I've tried in the past to make this %trylock() macro work failsafe but with no real success. So can't really recommend to use it. ... View more

Tis type of logic is coming from advanced schedulers (Ctrl-D OPC expect LSF the same). The flow(job) is collection of programs to run on a regular scheme. - Dependicies and events are influencing when each program is allowed to run - actions as suspending a program (removing from requirements) are possible The logic to solve will be: 1- after a planned time and file2 does not exist have job2 suspendend (possible by running a job) 2- When Job2 is allowed to run more than once and is capable running on an empty file     Have a time event within the flow planned to deliver an empty file 3- This will be an excpetional case. Have your operators being instructed to suspend the job2 as reaction on the alert message (late) of the scheduling environment. All depends how the environment is organized and the options in your tooling.    ... View more

Hi Shi An easy way to go could be: 1. File trigger on "arrival" using your wildcard matching. 2. SAS job querying the directory with the trigger files and checking if there is more than one matching the file pattern having a creation time >= system time minus 5 minutes      - Exactly one matching file: SAS job creates a new trigger file with a different naming pattern      - More than one matching file: SAS job deletes any trigger files with the new naming pattern (if any left over from a previous run). 3. File trigger on "exist" looking for this new trigger file with the different naming pattern 4. Rest of flow. LSF itself has a rich command syntax but only a small subset is implemented into SAS Metadata (eg. the file trigger "arrival" which then creates the corresponding LSF command). Instead of using a SAS program checking for trigger files as I've suggested you could also write a script with LSF commands - "bhist" for example lets you query for job flows executed. If not licensed separately then I believe LSF comes as an OEM version and only allows you to schedule SAS programs. So eventually you need to write a SAS programs which then calls the LSF script in order to submit such commands. About documentation: Schedule Manager documentation is available from within SMC help. There is also some online doc available, eg. here http://support.sas.com/documentation/cdl/en/scheduleug/64110/PDF/default/scheduleug.pdf I found this - a bit outdated - paper which I liked quite a bit: http://support.sas.com/resources/papers/SASScheduling.pdf You can get LSF documetation directly from Platform Computing (it's now owned by IBM) or also from the SAS site: Scalability Community: Platform Suite for SAS ... View more

Conditional execution of jobs is normally done via scheduler. LSF for example allows for such conditional job execution. You have always the option to wrap a job into a macro using job pre- and post-code. In the pre-code section you have then something like "%macro MyMacro; %if <expression> %then %do;", and in the post-code you have something like "%end; %mend; %MyMacro;" You can do the same in the pre- and post-code of any node as well. If you want several nodes wrapped into such a macro then I probably would use separate user written code nodes to define the macro for clarity. But you could also just use the pre-code of the first node and the post-code of the last node to set this up. Not sure what happens if you feed an empty table to the teradata table loader. I would assume if the table is empty then no loading happens so may be you even don't have to care about conditional processing (but of course if it's a replace load then the target table would still get truncated). ... View more

You can export the EG project to SAS code and you then can import SAS code into DIS. The DIS job generated won't look very pretty though and you will get a cleaner result by re-building the job from scratch. ... View more

Hi: There is no such option to shrink or enlarge what is going to be on the page. You can impact the PDF viewer after the file is created using SAS system options, but you can't shrink or fit while the output is being created. That is why you have to write the report to fit within the margins using ODS STYLE= overrides. cynthia ... View more

DIS might very well generate SAS Data Step code, e.g. the Lookup Transformation uses (data step) hash objects or in the Loader Transformation you can even choose between "Modify" (=data step) and SQL. ... View more

XCMD might be disabled when running your job out of DIS (session created using object spawner). But when running the job in batch (like done via LSF) then the setting is very likely XCMD - else you can set it yourself by passing -XCMD as start option. I personally believe that for DIS development XCMD should be set. There was some time ago some rational posted which can be used to discuss this within an organisation - but I just can't find this thread anymore. ..... found it: The case for XCMD privileges in SAS Enterprise Guide - The SAS Dummy ... View more