Building off of your code, to calculate the start of each player's first winning streak, you could use the lag() function to look back.   data number_game_want; length win_streak 3.; set number_game; by player starttime; retain win_streak; if first.player then do ; win_streak = 0; _done=0 ; end ; if result = 'W' then win_streak + 1; else win_streak = 0; lag2playtime=lag2(playtime) ; if win_streak=3 and not _done then do ; retain _done ; _done=1 ; TimeToWinStreak=lag2playtime-starttime ; output ; end ; format TimeToWinStreak time5. ; run; ... View more

@_zeta_ wrote: I was able to replicate the case, It works!   ;*%mend;*);*';*";**/; run;  Now, we want to replicate this for all users that use SAS Studio, I can't do that in workspace autoexec.sas code because It should be place at the beginning of the user's code, may be exist another place to do that? I'm surprised Studio isn't already appending that magic string after each block of user submitted code.  That's what EG does.   Personally, I think automatically fixing unmatched quotes can be confusing to developers.  It can end up hiding the problem, because the IDE fixes it.   So I would recommend handling this as an education issue, and inform users that if if they receive the error you mentioned, they likely have a problem with unmatched quotes.  And they can either try submitting the magic string to fix the problem, or they can exit their SAS session and re-start it. ... View more

I think I understand now.   I think the problem is that when you run your code, you get an Excel file with two worksheets.  One has the pivot table you want (which fits in an Excel sheet), and the second has all of the data (which does not fit).  Is that right?  And the pivot table references the data in the AllData worksheet.   What you want is a way to make an Excel file with a pivot table where the source AllData is a SAS dataset out on the server, rather than a worksheet.   If you don't need a pivot table, it would be straight forward use the AMO to make a stored process which allows users to input options for the table definition (row, col, summary stats etc), then runs against a SAS dataset and returns results.  But I don't know if a pivot table use a SAS dataset as a source. ... View more

Sorry, I'm not understanding the  big picture.   If your data is too big for Excel to handle, then tableeditor or whatever destination can't solve that problem (assuming your users want to open the data in Excel). ... View more

I don't think noquotelenmax will effect the note about text immediately following a quoted string, e.g.:   1 options noquotelenmax; 2 %let foo='bar'foo ; ----- 49 NOTE 49-169: The meaning of an identifier after a quoted string might change in a future SAS release. Inserting white space between a quoted string and the succeeding identifier is recommended. ... View more

If you start a new session, and run a task, do you get that Note?   I tried to replicate the problem, but I couldn't, even with code like: 1 %let foo=%bquote(blah'AAA BBB CCC'blah) ; 2 %put &foo ; blah'AAA BBB CCC'blah The only way I could get that NOTE in the log is if I introduce an unmatched quotation mark, as suggested in this thread: https://communities.sas.com/t5/SAS-Programming/quot-NOTE-49-169-The-meaning-of-an-identifier-after-a-quoted/td-p/121796   ... View more

Interesting, I didn't know tableeditor could do that.    It might be easier just to use PROC TABULATE or PROC REPORT. That said, isn't your code missing a pivotdata_stats option to specify the summary statistics you want in the table?   Maybe start by running this minimal example from tech support, and see if it works: https://support.sas.com/kb/45/255.html. ... View more

I'm not an  admin, but I know it's possible to configure logging on the stored process server so that it will capture the full log from the stored process that was run.  I would do that, then review the log to find the step that caused the warning/error.    If you are seeing warnings in your log from the PROC IMPORT or PROC APPEND step, then yes that would explain the status being set to 4. It's best to correct your code to avoid those warnings.   There is also a NOWARN option which can be added to PROC APPEND to suppress warning messages. ... View more

If you set the system option mautocomploc, SAS will write a note to the log when it compiles an autocall macro that shows the file that was compiled, e.g.:   2 options mautocomploc ; 93 %put %lowcase(foo) ; MAUTOCOMPLOC: The autocall macro LOWCASE is compiling using the autocall source file C:\Program Files\SASHome\SASFoundation\9.4\core\sasmacro\lowcase.sas. foo   If you turn on the option mautolocdisplay, it will write similar information to the log every time an autocall macro is invoked.   To your second question, calling a macro from a subfolder does not effect which macro will be compiled.  When you call %check_env for the first time, SAS will look through the autocall libraries in the order they are listed in SASAUTOS, until it finds a file check_env.sas.   ... View more

To start with I would search for "ERROR".   The red X on the error tab is not a problem.  It is always there, as a visual icon to indicate it is the error tab.   The red X on the program tab is a concern.  It indicates (I believe) that an error was generated the last time code from the program was submitted.  I agree, it's surprising to see a red X on the program tab while the error tab reports 0 errors.     I wonder if it's possible you have turned off log messages at some point (e.g. via PROC PRINTTO or similar)?  Or if an error is being generated by EG pre-code or post-code which is not shown is the log?  Those are just guesses as to possible causes.  I don't know the actual condition that EG uses to flag the program tab with an X.     One thing you could try would be to run  a step that does not generate errors, and confirm that the red X on the program tab goes away, then run your full program again, and see if it returns. ... View more

@CathyVI wrote: @Tom Thank you. This is very helpful but one more thing. FIND is actually what I want. I don't have variable FIND in my dataset. I have two separate dataset List A and List B. How can I build the "if then statement" or what line of code can I add to your code to get the FIND variable. The table I presented was the output I wanted. Am sorry I should have stated that in my first post.  Look again at Tom's answer.  The FIND variable is created in the PROC SQL step: select A, max(0<findw(B,A,' ,.','it')) as FIND PROC SQL is very helpful in this case because it makes it easy to create a cartesian product.  If you're not familiar with PROC SQL, it's possible to write a cartesian product in DATA step, but it's more code. ... View more

In your simple example, does it still work if you replace the ODS text with: P 'הפאנל מתעדכן בכל יום ומהווה טבלה צוברת של העמדות החל מ01.09.2020 ועד יום עסקים אחרון'/Style=Header {fontsize=12pt color=black fontstyle=italic fontweight=bold just=R }; ?   It's great that you have an example that works, and an example that doesn't work.   Typically I would start with the example that doesn't work, cut it down to be much simpler (just one or two lines in the email).  And see if it works. Then I would make that example even simpler, in iterative steps, to see if it starts working.  So you could remove the style format, then remove the non-Latin characters, etc.  The hope is that as you make your non-working example more and more like the working example, you'll find the issue.   Or alternatively, you can take your working example, and add complexity to it, to see if it will break. ... View more

This is very surprising, and disappointing.  Since an admin could already make these functions unavailable by configuring SAS sessions to run in "lockdown mode," I'm surprised SAS would completely remove the functions.   The What's New has a list of the functions removed in M9.  In addition to the variations of ADDR, PEEK, and POKE, we also lost the MODULE functions.   https://documentation.sas.com/doc/en/pgmsascdc/9.4_3.5/whatsnew/n14c8glgh3j7hxn1b1byjs3sqnvz.htm#n0f4fpvhdzvo22n1rf9zubnzpkza   ... View more