Hi @DavidPhillips2,   In general you can use the SAS datastep functions (there are exceptions!). For the current date you have today(). If you want the date and time in one use datetime().   proc sql; select name, datetime() format=datetime22. from sashelp.class; quit; ... View more

Hi @Riana,   The location that you seeing (or should be seeing) is controlled by the metadata configuration of the workspace server. It is the "File Navigation" setting available under the advanced options of that workspace server properties in SAS Managemt Console. Check that setting or have it checked by your admin people and work from there. Also, when comparing with your collegues make sure you are looking at the same server (SASApp or whatever is available to you). Each server context may have a different setting.   Hope this helps, - Jan. ... View more

So I talked about this at the Data Management booth in the Quad and a few eyebrows were raised but noone had the answer. So they suggested to open a track with tech Support which I did. And lo and behold the answer came swift and caused a facepalm moment for me.   The Output Directory property of the Data Step Batch server works in concert with the "Send the output to a file" option of the Schedule Manager in SMC. If you right-click on the Schedule Manager plugin you get access to that option. So if that option is checked and you have a location specified for the batch server than the -print option is added to the SAS command that is composed when deploying the job. Easy as that. I did not find any reference to this option in the online or in-app help. When naming the .lst file the "Prefix the SAS log file with the flow name" option is also honoured. Just no timestamps or anything so output files will be overwritten.   So finally the riddle is solved. Thanks for all chiming in and I hope we all learned something.   Regards, - Jan. ... View more

Hi CF,   This has all the signs of a classic table lookup problem. This class of challenges can be approached in a few ways, a merge (SQL or Datastep) being amongst them.   Your final choice would be based upon aspects like the size of the base table, the lookup table and their relative sizes. Also your preparedness to recreate the base table is important. Without going to provide detailed code I would suggest, assuming that the base table is both large and much larger than the lookup table, is to used either:   1) SQL update 2) Datastep with MODIFY and a hash table lookup.   Keep in mind that every row in your table will have that binary (a datatype that does not exist in SAS; use a flag of type char(1)) variable. Just the value differs. Your question seems to suggest that you are looking for a way of adding the variable only for "Deficit" accounts.   Hope this helps you on your way. There are many many code examples on-line to get you going.   - Jan. ... View more