The purpose of the function/step is to calculate the number of working minutes spent on a task for an employee.  There are SLAs/targets, and to be fair, the weekend shouldn't contribute towards the time spent, nor should the time outside of working hours be included either. I think my test case was too simplistic. I probably should have had it span a weekend, or a fortnight. Okay, so if we compare 03FEB2015:09:20:00.000 and 30JAN2015:16:50:00.000 should be (17-9) * 60 + 20 + 10 = 510. I've tested the supplied code, one of them looks to work (though there is a tiny offset): 16         %let dt_str = '30JAN2015:16:50:00.000'dt; 17         %let dt_end = '03FEB2015:09:20:00.000'dt; 18         19         data hai_kuo; 20            a=&dt_end.; 21            b=&dt_str.; 22            c=mod(intck('minute', b,a),60); 23            d=abs(minute(b)-minute(a)); 24         25            put c= d=; 26         run; c=30 d=30 NOTE: The data set WORK.HAI_KUO has 1 observations and 4 variables. NOTE: Compressing data set WORK.HAI_KUO increased size by 100.00 percent.       Compressed is 2 pages; un-compressed would require 1 pages. NOTE: MVA_DSIO.OPEN_CLOSE| _DISARM|         STOP| _DISARM| 2015-02-06T08:44:29,434+11:00| _DISARM| WorkspaceServer| _DISARM| SAS|       _DISARM| | _DISARM| | _DISARM| 14991360| _DISARM| 11| _DISARM| 16| _DISARM| 263433| _DISARM| 96476329| _DISARM| 0.000000|       _DISARM| 0.000000| _DISARM| 1738791869.434000| _DISARM| 1738791869.434000| _DISARM| 0.000000| _DISARM| | _ENDDISARM NOTE: PROCEDURE| _DISARM|         STOP| _DISARM| 2015-02-06T08:44:29,434+11:00| _DISARM| WorkspaceServer| _DISARM| SAS| _DISARM| |       _DISARM| 15257600| _DISARM| 14991360| _DISARM| 11| _DISARM| 16| _DISARM| 264440| _DISARM| 96476596| _DISARM| 0.000000|       _DISARM| 0.000000| _DISARM| 1738791869.434000| _DISARM| 1738791869.434000| _DISARM| 0.000000| _DISARM| | _ENDDISARM NOTE: DATA statement used (Total process time):       real time           0.01 seconds       cpu time            0.01 seconds       27         28         29         data xia_keshan; 30            do i= &dt_str. to &dt_end.; 31               if weekday(datepart(i)) in (2:6) and 9 <= hour(timepart(i)) < 17 then seconds+1; 32            end; 33         34            minutes=divide(seconds,60); 35            put minutes=; 36         run; minutes=510.01666667 The second one works, it looks as though it's incrementing based on seconds.  If the periods are really far apart the job will take ages to run, eg 50 years.  I need to think about whether this is really what I want or not, but I think it does work ! ... View more

I thought about using the dictionary views/tables in the SASHELP library.  I wasn't able to find WORK sessions for other users, just my current session. I tried a script, and I think it works.  I have it scheduled to run at 9pm every night.  This is what I ended up with: *delete filter_for_ datasets that can cause locks on data; *from; *http://techie-buzz.com/tips-and-tricks/recursively-delete-files-in-folders-and-sub-folders-using-command-prompt.html; x 'w:'; x 'cd W:\SASWORK\temp'; x 'del /s filter_for_*.sas7bdat'; Pretty simple solution in the end I think, not particularly elegant, but it gets the job done. I'm still interested if there is a better solution to this though? ... View more

Sorry, I was lazy, yes, I did mean using SAS Web Report Studio. In in SAS Web Report Studio, I've attempted to create a SAS Web Report (usually has a suffix of .srx, what do people usually call this?).  In that SAS Web Report, I have put in a Stored Process (as opposed to a table, or graph, etc). I want the Excel file created when the user visits this page.  They have no access to SAS Enterpride Guide.  I would be very happy to create plain HTML files, but I wouldn't know how to have a Stored Process execute? My example of C: drive was too simplistic in hindsight, it's actually going to a place on the network.  The workspace server should have visibility of the spot that I'm attemping to export to. It doesn't have to be a Stored Process, it can be anything, I just couldn't think of a better way of doing this. Note, I already have a SAS Web Report, with a Stored Process that just lists all the data, the nice thing is it doesn't display thousands of records, but only the first 40.  The user in turn clicks on the export button, and they get a zip file.  They extract it, open the Excel file, and then save it as another Excel file.  I felt that this was quite a long round-about way to get a listing of data in Excel. What I want is for a user to be able to visit something which in turns generates an Excel file (a dump of a SAS dataset) on the network.  Whilst the Addin for Microsoft Office sounds ideal, I have two issues with it, licencing and even installing it.  If licencing wasn't an issue, I would have contacted technical support for help on that.  I don't want to generate a dump of the data everyday. Thanks. ... View more

I've finally gotten the time to look at this again. I think I've found it. This is what I did: * Looked at some code in the location Barry suggested, for our installation it was F:\SAS\Config\APM93\SASEnvironment\SASCode\Jobs\usageReports\artifactTopTen.sas * Observe there is a call to %artifactReportSubSet; near the top of the code, it was two lines above the reference to &numWeeks. * Looked in the Macro directory, for us it was F:\SAS\Config\APM93\SASEnvironment\SASMacro\artifactreportsubset.sas, chose the job which looked to have the macro in it (pretty well named I'd say) * Find that the contents has all the magic figures I'm interested in I'm more comfortable changing the figure in one location, rather than hard coding it in individual jobs. Hopefully if anyone else has this issue, this might help. I think I was not following Barry very well because it looks as though we've on 9.3 and he was on 9.2. ... View more