Hi Chang, Unfortunately I am working on SAS 9.1:) So your solutions in my case looks like unreachable for a long time))) Anyway thanks! ... View more

Hi Geofferey, Thanks for your code, sorry for such late reply, I had a lot of tasks, as usual. I compared my and your codes, my(using sas procuderes, macros etc.) has less lines, but yours(proc iml) works fuster, but in my case it was'nt very critical becouse source relation table isn't big I also was surprized that you realized the task without recursion, but then I have found that proc iml doesn't support recursion at all so it's ok))). Unfortunatelly I can't show you my code becouse of security rules in our company but shortly - My code is just set of macros plus recursion plus I made some kind of "Checkpoints" in order to provide possibility debug the macro a little bit. Thanks! ... View more

Hi Geofferey, First of all thanks for your answer. I've already succeed in implementation Tarjan's algorithm(it's a little bit improved version of Kosaraju's algorithm.) I realized the task not using IML tool with it benefits, I didn't know about the tool before, so I've implemented the task using standard SAS language elements + recursion. But I'll with please will look to your version of implementation of the algorithm using IML. For me interesting is performance side, lines of codes that takes your version etc.Actually SAS isn't very useful for such kind of tasks that needs  stack, lists, recursion etc., but realize such tasks is real but with worse performance then ,for example, C,java or javascript provide. When I'll have free time i'll look to your version. But for me it was real surprise that sas hasn't realized at list DFS(Depth-first search), becouse sas is the BI tool and such kind of tasks , as for me, is a common in many business process, it's not only theoretical-mathematical tasks, but it's my opinion base on my own work backlog... Anyway-thanks! ... View more

Hi again Lin, I suppose you are using SAS version 9.2 or later, in this case your macro will work perfect, but I have SAS 9.1.3 so in my version FINFO function isn't so flexible as on later version, I can't extract filesize and another attribtes using this function in SAS 9.1.3. But anyway thanks for your answer:)! ... View more

Thanks Tom! ... View more

Hi again, Thanks, it's probably what I needed. Only one small remark - data step return not all files that are on folder, just 4-5, plus some header and footer, as you wrote higher...Nut offcourse it can be simply deleted. Thanks! ... View more

Hello, Can you please append at least one column to input statemant in data step that you described higher? I ask becouse I have already made similar solution with x command that run .bat file that run .vbs file(Visual script) file that just look into some folder get all sub file and needed property then store it in csv file and then I read this file to sas data set by infile statement but I feel that should be easier and more optimal solution... So can you please tune your code in last data step: data have; infile test; input ; *using column input to get whatever contents you want. You may need to skip the headlines; run; Thanks! ... View more

Hi Lin, Thanks for your anwer, I tried and sub-file names retriview correct, but I need not just file name, I need also file size and date of last modification. File size probably can be found by FINFO function, but this func can't return date of last modification... May be this property can be found by some different function etc.? I have already made solution with .vbs(Visual script) file that just look into some folder get all sub file and needed property then store it in csv file and then I read it to sas by infile statement but I feel that should be easier and more optimal solution... Thanks! ... View more

Hi Cynthia, It's probably what I need:), thanks! I'll just check how it will influance on performance and if it will be acceptable - I'll use this ESCAPECHAR function to achive needed format view. Thanks once more! ... View more

Hi Cynthia, I see your point, I also tried before option that you described in your example(outputwidth etc.),but the root of problem is that if I'll not assign column width in proc report for each column, this width will be automatically defined by ODS pdf engine ,based on margins, papersize, fontsize as you described, and if few columns has values with long chars one row of data splits into two that is absolutelly unreadible. For now I just set column width for each column(cellwidth statement) but sometimes it's also not the best variant becouse as I described higher - I can't predict len. of columns,so , for example, if I set for all of them same length,-  in one report all cols can has similar length - in this case all is ok, but in another report(with same set of columns but diff data) one column can has long string and another is just empty, so logically will be make this one column wider than another one. As I know in HTML tables exits possibility limit whole HTML table size and column width automatically defines from HTML tables cell content(just len of value in cell), and proc report in the end ganarates HTML table, so I supposed that should exist option that can limit whole proc report width, so even if all columns will have long char - each row will not be splitted into two, it will be just very high and it width will be some logicall depended from margins, papersize, fontsize values length of another columns etc. But ok, looks like I spend too much time on this small issue:) Thanks! ... View more

Thanks! ... View more

Thanks Doc! ... View more