That seems backwards.  Text copied from the normal Program Editor (not the "enhanced" editor) will just be text , it will not include any "font" information.   To preserve spacing in text make sure to do two things. 1) Make sure you do not have TAB characters in the text.  There are SAS editor options to have SAS automatically using spaces instead of physical TAB characters to indent text. 2) Make sure that the target system is using a monospace font. ... View more

Do the datasets all have the same structure? Do you want to output one single dataset that contains the observations from all of the datasets?  Or do you need to keep them separate?   Do you know the names of the datasets?  If not then how will you get the names?  Do you need to run this step on every dataset that has the variable VALUE?   Is there a reason you are leaving PERC as character but converting N to a number? Is there another variable with the overall N that you could use to re-calculate PERC instead of just reading in the rounded value that was written into the character variable VALUE?   NOTE:  BEST is the name of a FORMAT.  Your code works because SAS treats BEST when used as an INFORMAT as an alias for the normal numeric informat.   ... View more

Your SITEID variable is character. The code you generated was  where &myVar in (002 003); Which is trying to look for a character value in a list of numeric values.   To make string literals add quotes. Best to use single quotes so that macro triggers in the values of SITEID are not acted on by the macro processor. Note that trailing spaces are not meaningful in comparisons, but would make the text put into the macro variable longer, so remove those. select distinct quote(trim(SITEID),"'") into :SITES separated by ' ' from DB ;   ... View more

LInes longer than 70 will only cause problems for humans reading the code which could lead to unbalanced quotes, etc that they do not see.  But that is probably not your problem if the same code runs properly in other situations.   Lines longer than whatever default LRECL SAS uses to read the codef ile from SYSIN could cause problems.  But you state the program actually runs and only the log file is missing.  So that is probably not your problem.   Here are other things to check.   Is there some system process that is removing files from the location where PROC PRINTTO writes the file. Are you sure you are looking at the file that PROC PRINTTO is writing to?  Perhaps some difference in the execution environment is causing it to place that file somewhere else. Are you running multiple versions of the program at the same time?  If so then make sure that they are not all trying to write to the same LOG file.   ... View more

The problem seems to be that you want to treat the NO blocks differently based on whether or not they are at the END of of the list of not.   Also you did not provide instructions for what to do when the first observation has a NO value.   Since it is easier to remember the past than predict the future it would probably be easier if the data was sorted by increasing date instead of the decreasing date order you provided.   So assuming you have an ID variable and your date variable is an actual numeric variable with date values that just happens to have a format attached that makes them print in that style (I cannot tell from your printout if you want the dates to print in MDY or DMY order. )   You could do something like this: data want; do until (last.id); set have; by id date ; if flag='YES' then any_yes=1; if any_yes then flag='YES'; output; end; drop any_yes; run; Note that including DATE in the BY statement will allow SAS to detect it the observations are not actually sorted by ascending date values with each ID value. ... View more

Do you have any other indications that the SAS code is actively running?  Perhaps the program has crashed (or gone into an infinite loop) and that is why nothing is being written to the log.   Try changing startup options that writes to the log are flushed to the disk immediately.  That might allow you to see what is the last step that is actually running. https://communities.sas.com/t5/SAS-Programming/How-to-force-updates-to-SAS-Log/td-p/413993   Also with "background" execution I would assume that means it is running the job directly from the .sas file (instead of having code submitted by your front end tool such as SAS Display Manager or Enterprise Guide or SAS/Studio).  In which case the lengths of the lines in the .sas file might be an issue.  If a line gets truncated you might end up with unclosed quotes for example that might make the program hang.  Personally I try to make sure that no lines of code in the .sas file is longer then the 65-70 character limit that humans can read without moving their eyes side to side.   ... View more

Sounds like you are asking how to store files in SAS Viya for Learners.   I would assume that is possible to do.    It is definitely possible in the similar tool SAS OnDemand for Academics. ... View more

It is not clear to me what you are asking for.   Are you having trouble storing the FILE that is the notebook?   Note that the notebook contains the program you want to run.  It the data the program uses is not part of the program, for example if it comes from an external database or file or website, then when you open the notebook again I would assume you would need to rerun the step that read in that external data before it could be used. ... View more

How large are the two datasets?  Do they have indexes?  Trying to do full joins of large datasets could overwhelm the storage on your computer.   One of your new data steps looks very strange. DATA R.DATE1; SET R.DATE; IF YEAR='2025' THEN OUTPUT; IF MONTH GE '07' THEN OUTPUT; IF DAY GE '01' THEN OUTPUT; IF YEAR='2026' THEN DELETE; RUN; First, are YEAR, MONTH and DAY really character variables?   If so make sure that the MONTH and DAY variables always have the leading zeros. Otherwise values like '2' will be treated as greater than '07'.   Second let's look at what the logic is doing. ANY observation with YEAR='2025' are written. Then ANY observation with MONTH larger than '07' are written no matter what value of YEAR they have.  So the observations that also have year='2025' are written twice. Similarly with the DAY checking. And the DELETE statement is doing nothing because it is the last statement in the step and the explicit OUTPUT statement will have suppressed the normal implied OUTPUT that occurs at the end of a data step iteration.   So basically any observations that has a valid DAY will be written out.  Those that also have MONTH between 07 an 12 will be written again.  And those that are from 2025 will be written at least once whatever value they have for MONTH or DAY.  And depending on the value of MONTH and DAY will be written another one or two times.   What did you actually want that step to do?   ... View more

Is this a Job definition in SAS Viya?   I doubt that HTML itself could ask SAS to provide the current value of a macro variable.  Are you asking how to copy and paste the text you wrote in the log into the HTML tab so you can save that static text as part of the Job definition?   If not I would look at the demo jobs that SAS has provided that show how to drive an HTML selector from the contents of a dataset.   ... View more

Since you have not provided any real details let me just give some general advice.   Using a macro to remote submit SAS code can get confusing since you need to worry about two levels of abstraction.   Where the macro statements are executing and where the SAS code the macro generates is executing.   So for example what will the %PUT statements write in this program? %macro rsub; %let mvar=local; signon xxx sascmd='!sascmd'; %syslput mvar=remote; %put LOCAL &=mvar ; rsubmit; %put REMOTE &=mvar; endrsubmit; signoff xxx; %mend; %rsub; Result: NOTE: Remote signon to XXX complete. LOCAL MVAR=local NOTE: Remote submit to XXX commencing. REMOTE MVAR=local NOTE: Remote submit to XXX complete. NOTE: Remote signoff from XXX commencing. NOTE: Remote signoff from XXX complete. If you want the %PUT to run in the remote session you could use %NRSTR(). %nrstr(%put) REMOTE &=mvar; In general I find it best to avoid executing macro statements in the remotely submitted code blocks.   ... View more

If you meant to attach photos of something please use the Insert Photos icon (looks like a camera) to insert an image file instead of attaching a PDF file.   So did you look at the dataset and figure out what the actual names of the variables are? I hope they used standard variable names like NAME or DIVER instead of "diver's name"n.   Your second step is doing nothing so it is not needed. Just use the actual dataset directly. LIBNAME ch4lib "~/sasuser.v94/Chapter4"; PROC CONTENTS DATA = ch4lib.DIVING; RUN; This step does not seem to be calculating exactly what was asked for. /* Part B: PROC MEANS statement to calculate the total score per diver (w/ new scoring method) */ PROC MEANS DATA = DIVING NOPRINT; CLASS Name; VAR Score2; OUTPUT OUT = DiverTotals SUM = TotalScore; RUN; Hint: If you use NAME as a CLASS variable instead of a BY variable and do not include NWAY option in the PROC MEANS statement then in addition to getting one observation perper value of NAME you will also get an observation with the total score for the whole dataset. ... View more