Hi @Patelbb - as best as I can tell from the log text the variable VSORRES is character so you cannot read it into the new variable VSORRESX using a numeric informat, it just doesn't make sense hence the invalid argument reference you're seeing in your log. ... View more

Ohh ok thank you so much!!!! This makes more sense now!! ... View more

Concur with all the others, a clear case for Maxim 3. ... View more

Directory SDTM does not exist in that location. @Patelbb wrote: Hi,   This is the result from the submitted code. The file path I used was copied right from the file so not sure why it doesn't recognize it.   135  filename DIR pipe 'dir "C:\SAS 9.4\SAS-II Class\Raw Data\SDTM" '; 136  data null_; 137    infile DIR; 138    input; 139    put _infile_; 140  run; NOTE: The infile DIR is:       Unnamed Pipe Access Device,       PROCESS=dir "C:\SAS 9.4\SAS-II Class\Raw Data\SDTM",       RECFM=V,LRECL=32767  Volume in drive C is OS  Volume Serial Number is 1A1D-B685  Directory of C:\SAS 9.4\SAS-II Class\Raw Data Stderr output: File Not Found NOTE: 5 records were read from the infile DIR.       The minimum record length was 0.       The maximum record length was 46. NOTE: The data set WORK.NULL_ has 5 observations and 0 variables. NOTE: DATA statement used (Total process time):       real time           0.63 seconds       cpu time            0.06 seconds     ... View more

@FreelanceReinh wrote: @Reeza wrote:   Then the issue is at 22 characters in, I added 1234567890 underneath, each 0, is a 10, so second 0 is 20, and 22 is 2 in red. That indicates the issue is at fdosedt.    323      duration= lcontdt-fdosedt+1; 12345678901234567890123   Hi @Reeza,   I agree that it's helpful to study these notes in the log, but I think the column number (22) points to the minus sign in this case, i.e., to where the first "operation on missing values" in this line occurred. It doesn't reveal whether lcontdt or fdosedt contains the missing value if not both are missing. (At least I can't see a difference in my PC SAS 9.4 log.) You are correct, the column indicator is not exactly correct so OP should check all variables involved in the calculation.  ... View more

You need be more careful in what variables you are referencing. Take this little block of code: 271 ** Create new variable that contains numeric values of s_cmstdtc; 272 ** If the first character of s_cmstdtc is 'U', leave numeric value missing; 273 274 format sort date9.; 275 sort = input(s_cmstdtc, ??date9.); 276 if upcase(substrn(sort,1,1))= "U" then sort = .; You convert the characters in S_CMSTDTC into a date value in SORT.  But then try to use a character function on the numeric variable SORT.  Didn't you mean to check S_CMSTDTC?  Also shouldn't you check it BEFORE trying to convert it to a date?    But even easier just delete the last line since the assignment statement above it will have already converted strings that are not valid dates (including strings that start with the letter U) to missing values.   Also look at this block of code earlier 263 ** Create new variable for s_cmtrt; 264 if (s_cmtrt ne ' ') then medname = Medication; 265 else if (s_cmtrt eq ' ') then Medication = 'None'; The comment mentions only one input variable, but the IF statement is reading from some other variable named MEDICATION.  Then the ELSE statement will modify that MEDICATION variable, but do nothing with the MEDNAME variable.  Did you mean to change the MEDICATION variable?  Did you mean to not set the MEDNAME variable to anything?  Is it a new variable or an existing variable that is being read in from the source dataset? ... View more

Hi: Thanks for posting the rest of your code. So, do you see the NOTE about "Groups are not created ...." That would be my suggestion for the first place to start debugging. Cynthia ... View more

Start by determining how you get those strings in your data in the first place. I'm 99% sure those should have been valid SAS dates and not character variables. ... View more