Can you replicate the problem with the little step you showed?   Something like:   data want ; set temp_01 ; age_on_date = int(yrdif(dob, date_01, 'AGE')) ; if missing(age_on_date) then put dob= date_01= ; format dob date_01 ; run; If so, then please post the full log from running that step.  Well maybe, not the full log if it's 1000s of lines from the PUT statement.... ... View more

Check if your log says "Note: missing values were calculated at... "  That would suggest that either DOB or Date_01 are missing values for some records.  Many people treat that missing values note as an error message. ... View more

I'm not familiar with those macros, but I see they are provided by SAS.  I would probably start by running the code with the system option MPRINT turned on, then review the proc template code to look for the yaxisopts option and see if the label is there.   Alternatively,  for custom graphs I often find it easier to have the PROC output the data, and then write my own SGPLOT or GTL to generate the graph. ... View more

Looks like you can pull this from dictionary.tables:   proc sql ; select memname, sortname, sorttype, sortchar from dictionary.tables where libname="WORK" ; quit ; See also this thread, which uses dictionary.columns :  https://communities.sas.com/t5/SAS-Programming/Keeping-the-defined-sortedby-values-in-the-metadata/td-p/823697 ... View more

Make sense.  Overwriting datasets: data foo; set foo; run; can cause all kinds of confusion.  Glad you got it sorted. ... View more

One simple check is to see if a WHERE statement will find records in both datasets. If you run: proc print data=person_file; where person_contract='90091'; run; proc print data=contract_file; where contract_id='90091'; run; Do both PROC PRINT steps return rows?  Hopefully one of them does not, meaning the value '90091' is not in one of the datasets.  ... View more

It's often helpful to run PROC FREQ to check the values of your variables.   If you run: prof freq data=work.tsa_nodupkey; tables Incident_Date*Date_Received/missing list; format Incident_Date Date_Received year.; run; are the results informative? ... View more

Check the header of the file.  By default the title is not written to a cell in the spreadsheet, instead it is written to the header.   I think in Excel you can still do Page Setup to see the headers. ... View more

I assume that's just the beginning of the email?  So basically the body of the email is showing you the HTML code instead of rendering the HTML?   Since you have both M6 and M8 available, you might try writing the MSOFFICE2K output to a file, and then comparing the files you get from M6 and M8 to look for differences.  I'd be surprised if SAS intentionally changed the MSOFFICE2K template.   Once you have the differences, you could send the sample code and output files to tech support.     ... View more

Different data structure should only require a change to the ARRAY statement, to list the variables in the array.   Or if you can put all variables in the array, you could try something like:   array x _numeric_ ; ... View more

Think about how you will handle ties, if ties are possible.    I think Tom's lovely solution would return the first variable in the array found by WHICHN.   ... View more

PROC PRINTTO will write the the log file, as long as the PROC PRINTTO itself executes.     Is it possible there was an error in your code before the PROC PRINTTO step?  That could make SAS enter syntaxcheck mode and may not execute the PROC PRINTTO step.  It might be easier to start by avoiding PROC PRINTTO, and focus on the log files created automatically.  Most schedulers will basically batch submit the SAS jobs, and there will be a logfile written somewhere that the administrators have set up.  If you don't know where your log files are being written, you may want to ask your admins or other colleagues.   Also note, depending on how you have set the logic in your flow, if Job #1 errors, Job #2 may never start.  The scheduler should allow you to determine whether execution of Job #2 is dependent on successful execution of  Job #1 or not. ... View more

When your question is about an error, please post the log including the error message.    Below is the log I get from running your code.  It looks like partialcorr=. is an invalid value.   1 proc power; 2 multreg 3 model = random 4 nfullpredictors = 6 5 ntestpredictors = 1 6 partialcorr = . - 22 200 ERROR 22-322: Syntax error, expecting one of the following: a numeric constant, a datetime constant. ERROR 200-322: The symbol is not recognized and will be ignored. 7 ntotal = 500 8 power = 0.8 9 alpha = 0.05; 10 run; NOTE: The SAS System stopped processing this step because of errors. Is that the error you get? ... View more