Dear SAS community,     I started working with the inegrated scheduler of SAS Enterprise Guide. To test it, I wrote a dummy project containing only one very simple dummy program:   %let Var1 = 'Hello World'; data testdata1; run; I then scheduled the workflow to be run once, and according to the schedule history the task was finished. But: The time stamp of the log file of the dummy program did not change. So, the program did not run, did it? And if so, why shouldn't it? I've run these simple lines locally, and they work, so there shouldn't be an issue with syntax.   Also, is there a way to get a log file of the job itself, like   'Running job at THU 4th JAN 2021 12:00:00 PM...... job completed successfully at THU 4th JAN 2021 12:00:30 PM'   and not just the log file of the program? Thanks for any help with this,   Miriam 🙂 ... View more

Dear SAS community,   I am having a personal crisis due to PROC LOGISTIC. I am training my model using a data set scoringsatz, and I want to test it using testsatz, like this:   PROC LOGISTIC DATA=&scoringsatz outest=work.Model_Parameters outmodel=work.model_out PLOTS(ONLY)=ALL ; class &varlist_model ; MODEL &ziel (Event = '0')= &varlist_model / gof SELECTION=none SLE=0.05 SLS=0.05 CORRB RSQUARE CTABLE LINK=LOGIT CLPARM=WALD ALPHA=&alpha. ; OUTPUT OUT=&scoringsatz._out (LABEL="" DROP=__FLAG) PREDPROBS=INDIVIDUAL; score data=&testsatz out=ergebnis_out ; But here's the problem: ergebnis_out only shows missing values for P_1 and P_0. And I have been trying to figure out for 2 days now why that is.   - Scoringsatz and Testsatz have exactly the same number of columns and column names. - If I test the model using the trainingset, it works. - If I split the trainingset using surveyselect and then use 1 of the sets for training and the other for testing it also works.   So, it should be due to the testset? But except for different entries it has the exact same structure??   I cannot post parts of the datasets as they are sensitive data with personal info.   Thanks for any hints, Miriam   ... View more

Dear SAS community,   I installed the University edition of SAS last week and am now working through the SAS online course no. 2.    The following code (activity 2.04), which is my solution and also the official solution, is supposed to produce a table with 5 rows, one for each value of basin (the one with the highest MaxWindMPH).   However, if I run this, I get a table with 54 rows and multiple entries for identical values of 'Basin'.     ***********************************************************; * Activity 2.04 *; * 1) Change the WHERE statement to a subsetting IF *; * statement and submit the program. How many rows are *; * included in the output table? *; * 2) Move the subsetting IF statement just before the *; * RUN statement and submit the program. How many rows *; * are included in the output table? *; * 3) Consider the sequence of the statements in the *; * execution phase. Where is the optimal placement of *; * the subsetting IF statement? *; ***********************************************************; proc sort data=pg2.storm_2017 out=storm2017_sort; by Basin MaxWindMPH; run; data storm2017_max; set storm2017_sort; by Basin;     if last.Basin=1; StormLength=EndDate-StartDate; MaxWindKM=MaxWindMPH*1.60934; run;   Now, my question: Is there simply a mistake in this solution (which, just by chance, I also made in my solution) or has there been an update in SAS which changed the behaviour/usage of last.myvariable/first.myvariable? I naively expected that this code sorts the input data according to Basin and then decsending wind speed, and by last.Basin=1 only keeps the last entry for each basin, the one with the highest wind speed.   I am using SAS Studio for my studies.   Thanks for your help,   Miriam     ... View more