@mohanj1 wrote: Thanks.   I never used the power shell cmdlet. So coudl you please let me know how to use the power shell cmdlet.   Regards, Mohan. https://www.google.com/search?q=powershell+select-string   Also, just to make clear:  when a SAS batch job is running, and writing to its log file, it has an exclusive lock on that file.  So, a SAS job cannot read from the log file that it is creating.  You have to read the log in a post-processing step, after the SAS job has finished.  grep and powershell are good tools for this, and is what I've recommended.  You could launch a 2nd SAS batch job to parse the log file from the first job, but IMO that is overkill, and not even the best tool for the application at hand.   "When the only tool in your toolbox is a hammer, everything looks like a nail".   I suggest you do a bit of self-study to improve your toolbox.   I'm unsubscribing from this one.  Good luck, hope you get it working! ... View more

But the jobs are scheduled in the server   How are the jobs scheduled in the server, i.e. what scheduler do you use? Do you have access to those jobs, i.e. can you edit the jobs? Even if you don't have edit access, how are the jobs created?  Do you pass the jobs to an admin person who implements them in the scheduler? Are the job logs written to a file share that you have access to? Are you on Windows or *nix?   So could you please let me know  sample procedure to write a code to check the ERROR in the log.   I already did in my last post.  On Windows, use the Select-String Powershell cmdlet.     ... View more

Why does it have to be "...using SAS code"?   I've done this all the time using scheduled jobs and post-processing.   On *nix I use grep. On Windows I use Powershell.  Or I install grep on Windows and use it as well (but usually I use Powershell).   For Windows, see https://github.com/scottbass/Powershell/blob/master/Scripts/Sas.ps1.    The Print-SASErrorsOrWarnings function beginning on line 478 prints ERRORS or WARNINGS to the output console.  And the scheduler software I used sent all console output in an email for failed jobs.  The Select-String cmdlet prints one line of context before and after the error message (something that would take a lot of work using SAS to process the log files).   Perhaps you can adapt this to meet your needs. ... View more

Hi @Reeza, I haven't looked too closely at the PROC TABULATE code (or revisited the docs - it's been a while since I've used it).  However, does your code calculate the running daily sums as the OP desired?  Or perhaps I misunderstood what the OP was asking? ... View more

Why is it so hard to get noobs to post their question in the form of a self-contained have/want data step?  Why do you expect us to convert your sample data into working code?   (Forum admins, when someone creates a new account, can you send them an email, or at least redirect them to a link, that directs them how to ask a question?)   Anyway, after expending the effort in converting the cut-and-paste job from your original post into a working data step, this is what I've got so far.  It's incomplete, but since you haven't been clear in asking your question, perhaps you can run with this and finish it.   You need to add loaddate to your data - the code can't magically know what data belongs to what loaddate.   My questions:   * How do you derive count? * Does ID have any relevance to what you're doing? * How do you want to name your columns?  Do they have to be SAS V7 column name compliant, or are you happy with name literals and all that entails?  See http://support.sas.com/documentation/cdl/en/lrcon/65287/HTML/default/viewer.htm#p18cdcs4v5wd2dn1q0x296d3qek6.htm   data have; input ID : 4. bucket1-bucket3 : 5.2 loaddate : date9.; format bucket: 5.2 loaddate date9.; datalines; 1234 10.00 20.00 70.00 01JAN2019 3456 10.00 20.00 70.00 01JAN2019 1234 10.00 20.00 70.00 02JAN2019 3456 10.00 20.00 70.00 02JAN2019 1234 10.00 20.00 70.00 03JAN2019 3456 10.00 20.00 70.00 03JAN2019 ; run; data dates; do loaddate="01JAN2019"d to "31DEC2019"d; output; end; format loaddate date9.; run; data source; merge have dates; by loaddate; run; proc summary data=source missing; by loaddate; var bucket:; output out=totals (drop=_type_ _freq_) sum= n= / autoname; run; options validvarname=any; * I don't know why the output does not have the loaddate (eg. 01JAN2019) as the column label ; * I'm running SAS 9.3 and EG 7.x; * Perhaps it will work properly for you??? ; proc transpose data=totals out=sums; idlabel loaddate; run; data want; set sums; array totals{*} COL:; totals_bucket=0; do i=1 to dim(totals); label=vlabel(totals{i}); putlog label=; * bail on first missing column ; if missing(totals{i}) then leave; totals_bucket+totals{i}; totals{i}=totals_bucket; end; drop totals: i; run; * Compare with the above output ; proc transpose data=totals out=sums2; id loaddate; run; data want2; set sums2; array totals{*} '01JAN2019'n--'31DEC2019'n; totals_bucket=0; do i=1 to dim(totals); label=vlabel(totals{i}); putlog label=; * bail on first missing column ; if missing(totals{i}) then leave; totals_bucket+totals{i}; totals{i}=totals_bucket; end; drop totals: i; run;   ... View more

@JJP1 wrote: ok what if it did not wait for unlocked file to be available and run the job with previous weekly available data.and what if the weekly dataset is not updated with latest records and yet to run may be just seconds.actually it is more of timing issue,it may occur and may not occure. sorry to annoy but kindly help do we have any other option or you mean that there is no other way except "FILELOCKWAIT" please.   I'm not sure why FILELOCKWAIT doesn't meet your needs?  But since you insist it does not...   I agree with @Patrick that a robust scheduler which handles job dependencies would help here.  Otherwise, ways that I have handled this:   1) A control table, where you insert a row when jobname FOO starts, setting StartDatetime and NULL EndDatetime.  Downstream jobs that have a dependency on FOO select the row where jobname=FOO and StartDatetime = MAX(StartDatetime) (i.e. the latest row for jobname FOO).  If EndDatetime = NULL then pause your current job using the SLEEP function.  Loop until EndDatetime is not NULL or a configurable timeout occurs.  If EndDatetime is not NULL, check if it is within a desired timeframe, i.e. it completed within the last 24 hours rather than 3 weeks ago.  PLUS you need to contend with potential locking on the control table itself (although the locking would be very brief) if you submit many jobs at once.  Or license SAS/Share.  Or use an RBDMS table for your control table.   2) Alternatively, create a marker file when jobname FOO starts.  Check for the existence of the marker file in downstream code.  Loop if the file exists.  Delete the file when jobname FOO ends.  Obviously this is simpler to code but you lose the metrics captured via option #1 above.   All of this takes coding in all your jobs.  And of of this "stuff" is handled by a full-featured scheduler.   https://github.com/scottbass/SAS/blob/master/Macro/lock.sas may give you some further design ideas.  It was written for Windows so would need to be heavily tested for Unix.  And if you're new to SAS and Macro it may be gibberish to you.  But it may give you some ideas you can run with. ... View more

Post your data as a complete data step we can work with rather than a cut-and-paste job. ... View more

https://github.com/scottbass/SAS/blob/master/Macro/loop.sas or https://github.com/scottbass/SAS/blob/master/Macro/loop_control.sas   See macro header for usage examples. ... View more