About djbateman

djbateman · ‎04-25-2014

I am trying to store some values into some macro variables. My problem is that the step I am using automatically sorts the values alphabetically instead of in the order that I want. When I add an ORDER BY statement, I get a warning in the log. Here is an example of what I am doing (the dataset is a subset of information from SASHELP.VCOLUMN): data ec1456; length libname $8 memname $32 name $32 varnum 8; input libname $ memname $ name $ varnum; cards; EC1456 AE AESTDT_RAW 44 EC1456 AE AEENDT_RAW 50 EC1456 AE AECHGDT_RAW 81 ; run; proc sql; /*** Orders the variables alphabetically ***/ select distinct name into :var1-:var3 from ec1456; /*** Orders the variables by VARNUM but leaves a warning message ***/ select distinct name into :var1-:var3 from ec1456 order by varnum; quit; I have read that I can just add NOWARN to the PROC SQL statement, but I have also been warned that it should not be used in production code. Those forums were also written in 2009, so I thought that maybe things have advanced in the last 5 years. Any thoughts on how I can properly sort the variables without getting a warning message?

djbateman · ‎03-31-2014

I can't validate if this is correct or if it is just getting me something that looks very close, but it looks like just adding the missing y-values for the x-values beyond the scope of the data did the trick. Thanks!

djbateman · ‎03-31-2014

Can you give me an example of what you mean? I can get the predicted values for the data in range, but not extended beyond that. I attempted to use the stability data to get the parameter estimates. I then used that to assemble the formula for the regression line and was able to expand the predicted values. However, I can't get the 95% confidence limits. They are just the exact same as the predicted values. Can you tell me what I am doing wrong? data stability; input time impurity; cards; 0 0.65 3 0.68 6 0.72 9 0.75 12 0.85 ; run; /*** Get parmeter estimates for specified model ***/ ods listing close; ods output ParameterEstimates=est; proc reg data=stability; model impurity=time; quit; ods listing; /*** Store parameter estimates in macro variables ***/ proc sql noprint; select estimate into :int from est where variable='Intercept'; select estimate into :time from est where variable='time'; quit; /*** Create predicted values from the regression equation formed from parameter estimates ***/ data pred; do time=0 to 48 by .1; pred=&int.+(&time.*time); output; end; run; /*** Rerun regression analysis to get confidence limits ***/ proc reg data=pred; model pred=time / cli; output out=reg p=pred2; quit;

djbateman · ‎03-28-2014

I am trying to figure out how to make a prediction line extend beyond the scope of my data. For example, in an FDA guidance document (http://www.fda.gov/RegulatoryInformation/Guidances/ucm128092.htm) there is a sample stability plot where the data points stop at 12 months, but the regression and confidence line extend to 48 months (see plot below). Is it possible to do this simply with the SGPLOT procedure? Also, can I get just one confidence limit instead of both the upper and lower? Here is sample code of what I have done in an attempt to copy the graph (notice how my regression and prediction lines stop at 12 months and I have bot the upper and lower limits): data stability; input time impurity; cards; 0 0.65 3 0.68 6 0.72 9 0.75 12 0.85 ; run; proc sgplot data=stability; title "Shelf life Estimation with Upper and Lower Acceptance Criteria Based on a Degradation Product at 25C/60% RH"; scatter x=time y=impurity/ markerattrs=(symbol=diamond); reg x=time y=impurity/ lineattrs=(color=black) cli cliattrs=(clilineattrs=(color=black pattern=1)); refline 1.45 / lineattrs=(pattern=4 thickness=2 color=black); xaxis label='Time Point (Months)' values=(0 to 48 by 3); yaxis label="Degradation Product (%)" values=(0 to 3 by 0.5); keylegend / position=right; run;

djbateman · ‎01-31-2014

I am trying to learn how to better interface Excel with SAS. I found an example from a SAS User's Group paper (http://www2.sas.com/proceedings/sugi31/024-31.pdf) that shows the following code: LIBNAME WrkBk EXCEL 'My Workbook.xls' VER=2002; DATA WrkBk.class; SET sashelp.class; RUN; LIBNAME WrkBk CLEAR; When I try running it I get an error message in the log: ERROR: The EXCEL engine cannot be found. ERROR: Error in the LIBNAME statement. I know that I need the SAS/ACCESS Interface to PC Files in order to use the EXCEL engine in the LIBNAME statement. I know I have it because I ran PROC SETINIT; RUN; and I got the following log output: NOTE: PROCEDURE SETINIT used (Total process time): real time 0.00 seconds cpu time 0.00 seconds . . . Product expiration dates: ---Base SAS Software 29NOV2014 ---SAS/STAT 29NOV2014 ---SAS/GRAPH 29NOV2014 ---SAS Integration Technologies 29NOV2014 ---SAS/ACCESS Interface to PC Files 29NOV2014 ---SAS Workspace Server for Local Access 29NOV2014 ---DataFlux Trans DB Driver 29NOV2014 ---SAS Framework Data Server 29NOV2014 Does anyone know why I can't use Excel on my machine? I have also noticed that it will not let me import .xls files. I have to use .csv. Maybe this is a technical support question, but I thought I would try here first.

djbateman · ‎01-29-2014

"data" inside the macro %do loop is the name of your dataset as you described above. "stacked" is the name of the dataset that will be produced after you run the macro.

djbateman · ‎01-29-2014

I don't know if what you are trying to do is possible and still retaining the numeric aspect of date/time variables. You would have to change them to character values and then do a "find and replace" (probably using the SUBSTR() function). But this takes away all ability to use dates and time for their true nature. You won't be able to properly sort or find differences between dates any more.

djbateman · ‎01-29-2014

Of course, you can't use the macro DO loop in open code, so you would have to enclose it within a macro: %macro stack(); data stacked; set %do i=1 %to 21; data (keep=col&i rename=(col&i=col)) %end; ; run; %mend stack; %stack();

djbateman · ‎01-29-2014

If you know the number of columns, you could try: data stacked; set %do i=1 %to 21; data (keep=col&i rename=(col&i=col)) %end; ; run;

djbateman · ‎01-29-2014

Please see the attached Excel worksheet for what my final output should look like. I have two databases (safety and clinical) that I merged together to check for inconsistencies. For each patient, I am checking their serious adverse events (SAE) to make sure that the SOC, PT, start/stop dates, relationship, and death dates match in both databases. I have two different types of traffic lighting that I need to do: First, if there is an SAE that is in one database but not the other, it is noted in the SAEMISS variable, and I would like to highlight that whole row. Second, if the SAE is in both databases, I would like to only highlight the 2 corresponding variables where there is no match. For example, if a patient has the same SOC in both databases, but the PT name is slightly different, then I just want to highlight the two PTNAME cells for that case (and the same for any other variables that are different between databases). I think I can highlight the rows from my first scenario by using the following code in PROC REPORT: compute saemiss; if saemiss^='' then call define(_row_,"style","style={background=red}"); endcomp; However, I am stuck on the second scenario. I can find how to highlight when a numeric value is within a specified range, but I can find an example for character values that compare across observations. Any ideas on if this is possible?

djbateman · ‎01-20-2014

If possible, it would be nice to read in everything into 2 columns. I would then transpose the data so that I have 7 variables (study, title, recruitment, results, conditions, interventions, & URL) and 13618 observations. Is it possible? If not, I can deal with the best we can get. The Conditions variable is the most important.

djbateman · ‎01-20-2014

Does anyone have any idea how I could get the attached txt file into SAS? I attempted to change it to a delimited file using a colon, but there are too many colons in the variable values. The format of the file is the variable name in the first column and the variable value in the second column.

djbateman · ‎01-16-2014

I never would have thought of that on my own. Thank you so much!

djbateman · ‎01-16-2014

Suppose I have two datasets with dates as follows: Dates1: Subject Date1 001 29AUG2013 002 21MAY2013 002 04JUL2013 002 20SEP2013 003 17JUN2013 004 16DEC2013 Dates2: Subject Date2 001 08May2013 001 25JUN2013 001 13AUG2013 002 17JAN2013 002 09APR2013 002 21MAY2013 003 24JAN2013 003 18MAR2013 003 17JUN2013 004 17JUN2013 004 27JUN2013 004 19AUG2013 004 30SEP2013 004 11NOV2013 I need to create a new dataset that compares DATES1 and DATES2. If any of the dates in DATES1 are found in DATES2 for a given subject, then I want to flag that subject. In other words, for the above example, my output would look like this: Subject Match 001 0 002 1 003 1 004 0 I have been playing with this for a couple of days now, and I can't seem to find a solution. What would be the best way to merge these two datasets so I can compare Date1 and Date2? My main obstacle is the fact that there can be multiple entries for a single subject in both datasets, and I need to compare all dates in both datasets for a match. Any ideas?

djbateman · ‎08-15-2013

Suppose I have a library of SAS datasets that are updated regularly, and I use those datasets to create new analysis datasets for each update. I want to store those new analysis datasets in archived folders. Is it possible to have SAS create a folder in my code, or do I have to manually create the folder and then tell SAS where to store the data? For example, let's say that I have my base datasets stored in C:\Studies\DrugA\Protocol1\Data. And suppose that I am outputting my analysis data into the following directory: C:\Studies\DrugA\Protocol1\AnalysisDatasets. However, I want to archive them, so I will have a new subfolder for each date I run the data, so I might have the following folders: C:\Studies\DrugA\Protocol1\AnalysisDatasets\2013-01-01 C:\Studies\DrugA\Protocol1\AnalysisDatasets\2013-02-10 C:\Studies\DrugA\Protocol1\AnalysisDatasets\2013-02-17 C:\Studies\DrugA\Protocol1\AnalysisDatasets\2013-04-11 etc. Is there a way to set up SAS code to create a folder based on the date the program is run, or do I have to manually create the folder and then change the LIBNAME statement in my code?

Online Status	Offline
Date Last Visited	yesterday

How to Compare a Merge ID Variable

Re: How to know if a date from a pipe command is ddmmyyyy or mmddyyyy

Re: How to know if a date from a pipe command is ddmmyyyy or mmddyyyy

How to know if a date from a pipe command is ddmmyyyy or mmddyyyy

Re: Retain Trailing Zeros in Numeric Variables

Retain Trailing Zeros in Numeric Variables

Re: ODS EXCEL Won't Automatically Adjust Row Height

Re: ODS EXCEL Won't Automatically Adjust Row Height

Re: ODS EXCEL Won't Automatically Adjust Row Height

Re: ODS EXCEL Won't Automatically Adjust Row Height

Re: GUESSINGROWS ( EXCEL to SAS) ??

Re: How to Compare a Merge ID Variable

Re: How to Compare a Merge ID Variable

Re: How to know if a date from a pipe command is ddmmyyyy or mmddyyyy

Re: Find Distinct Values in a Horizontal List

Re: PROC IMPORT XLSX File and Specify Formats

Re: COMPRESS Function Modifier Warning

Force Arrow Head on HIGHLOW Plot HIGHCAP Option

Re: Converting XLSX to CSV in SAS

Convert .XPT to SAS Datasets

PROC SQL Macro Variables (INTO Statement) - with ORDER BY Statement

Re: Extend Prediction Lines Beyond Data Scope

Re: Extend Prediction Lines Beyond Data Scope

Extend Prediction Lines Beyond Data Scope

LIBNAME and EXCEL Engine

Re: all column stacked in one

Re: display datetime with missing day/month/second

Re: all column stacked in one

Re: all column stacked in one

Traffic Lighting with Character Values

Re: Importing Messy Text Data

Importing Messy Text Data

Re: Multiple Match Merging?

Multiple Match Merging?

Can SAS Create Folders?