I got it to work like you see below. I get a lost card note in the log which I can't yet explain but I'm looking at it now. If anyone sees a cleaner solution please let me know. And thank you everyone for the input. %let folder = \\kcpublic\PUBLIC\Public\SAS\Costing Run Logs\Costing Run Logs 09-10\ ; filename indsn "&folder"; data one; infile datalines truncover; length fil2read $150; input fil2read $char150.; fil2read = cats("&folder",fil2read); infile dummy filevar = fil2read end = done; file_name = fil2read; do while(not done); input @1 intext $char100.; output; end; datalines; Empty Model Prelim Project Log.txt Empty Model Previous Project Log.txt Profman Containers to Cars Marketing Prelim Ordered List Project Log.txt Profman Containers to Cars Marketing Previous Ordered List Project Log.txt Profman Containers to Cars Prelim Ordered List Project Log.txt Profman Containers to Cars Previous Ordered List Project Log.txt Profman Output Marketing Prelim Data to SAS Prm Stg Project Log.txt Profman Output to SAS PRM STG Prelim Project Log.txt Profman Output to SAS Prm Stg Previous Project Log.txt ; run; ... View more

If you want to find similarities of form usage between roles I think you want to make Role an ID variable and possibly your AM/PM varible. And add a maxclusters = 10 to the proc statement. Experimenting with values of maxclusters is what I find educational. It will assign each role, or role and time, to a cluster of similarity based on the form values. If you use a summary procedure such as Proc summary to count of useage per form you might want to standardize the counts using proc standard. ... View more

I've created a short example using sashelp.class to demonstrate one way to annotate values at the ends of the Hbars ...   data anno_in_bar; set sashelp.class; xsys='2'; ysys='2'; when='a'; midpoint=sex; subgroup=name; function='label'; position='4'; text=trim(left(name)); run;   proc sql; create table anno_end_bar as select unique sex, sum(height) as total_height from sashelp.class group by sex; quit; run; data anno_end_bar; set anno_end_bar; xsys='2'; ysys='2'; when='a'; midpoint=sex; x=total_height; function='label'; position='6'; text='20'x||'Total='||trim(left(total_height)); run;   data anno_all; length text $50; set anno_in_bar anno_end_bar; run;   pattern1 v=s color=yellow repeat=50; proc gchart data=sashelp.class anno=anno_all; hbar sex / type=sum sumvar=height nostats subgroup=name nolegend; run;   ... View more

Hi,   as Linus mentions, there are many technologies available for enabling High Availability on your servers and on your workstations. There are some general ICT technologies. I.e: - Example for servers: to create a cluster (active/passive with sync is a good first approach) of your servers and, optionally, your critical filesystems. - Example for workstations: Virtualized clients (Microsoft AppV, Citrix, VM ThinApp... that can be pushed under an schedule.   You may want to read a bit: http://support.sas.com/resources/papers/proceedings14/SAS305-2014.pdf   And, of course, as Lunus also mentioned, SAS Grid can be an option as well.   Best regards, Juan ... View more

This worked.. sort of. I thought I'd do it in a loop counting columns 1 to 13. This sounded promising until I tried it. The number of columns internal to SAS is apparently set by your columns statement not what is actually on the report. So it became 1 to 21. Using higher numbers causes all kinds of strange errors. I can't get some columns to turn red no matter what I do. In my code they are time, successful_rows, and last_rows I have no idea why. Unless it has to do with them already being set to a color in a previous compute block. But that doesn't explain why it does override the color in the first column. My compute block now looks like below: compute last_error_code;   if last_error_code gt 0 then do i = 1 to 21;   call define(i, "style/merge", "style=[background=red     font_weight=bold]");   end;   endcomp; All but three columns are now red, better but not right. Thanks for this response it did help a lot. ... View more

For the technical fixes. see SAS Hot Fix Downloads somebody at your organization should be able to organize that. For the user/solution/application part of ABm see: SAS Cost and Profitability Management (formerly SAS Activity-Based Management) the password for those can be got by asking them at your official sas contacts (TS) as part of your license. The evnorinments file (Windows desktop) you should cooperate with your desktop support guys on what is allowed. As zero-copy deployment and manually adjusting some location references that may be the easiest way to do that. Going into an expensive repacking process of the desktopclients or adding new complexity by maintaining a config file on a webserver (that is what is behind that) is not them most easiest thing. I like KISS approaches.       ... View more

PeterC  I do not like the use of undocumented functions. They are mostly undocumented for some reason. The monotonic for example is dependent on a order only being logical possible when not doing multi-threading.  Multi-threading is becoming the normal approach as it should be a gaining turn-arround time when several other conditions are in place. This is the big-data beyond comfort zone area. A like instruction SAS(R) 9.4 SQL Procedure User's Guide is fully documented and it can be passed to an external DBMS.   That is the same for eg Teradata supporting a lot of functions that are (should be) transported in Teradata sql.SAS/ACCESS(R) 9.4 for Relational Databases: Reference, Fifth Edition. The goal is letting the data reside and processed as close where it is stored. Avoiding additional transfers and copies. kckaiser did not mention anything of the physical involved environment.  When there is no optimized physical environment and he is trying to do some things in a limited existing sas environment the best choices could be totally different. When the data is stored locally and is limited of a single storage device the IO-time is the biggest factor to deal with. In that case a classic sas datastep can solve sometimes for more efficient some type of logical problems.  In the big data world is NO_SQL hyping.               ... View more