About anjgupta

anjgupta · ‎09-07-2011

Hi, I'm trying to find some documentation on ? and ?? - new to me. Seems I can add ? or ?? to my invalue statements for all or some variables that might result in errors. FriedEgg uses a colon ":??" but Tom did not. Is one 'correct'? If you have any links to help me understand this operator better - great. Still searching.

anjgupta · ‎09-07-2011

I'll try just 'U' - but I need it to indicate the missing value of .U (numeric) and not the character 'U'. Thank you.

anjgupta · ‎08-31-2011

I could do that for month - which is a small range. But I also have items like birthweight in grams and then the range we accept is infinite. The options invaliddata=U; didn't accept .U which is the desired formatted value. Still trying.

anjgupta · ‎08-31-2011

I assume the OPTIONS way will affect the entire program. And the error handling way is particular to each variable. I have a lot of vars to read in for a particular infile - is there a middle way to have the error/invaliddata handled within 1 datastep for all incoming vars? Thank you

anjgupta · ‎08-31-2011

Hi, I'm using the following format: proc format; invalue month_pncf (default=2) 0 = 88 99 = .U . = .U other = _same_; run; expecting the raw data to be in numeric form. However, when the incoming data is a dash '-' in the .dat file, I get a value of dot '.' for the formatted data. Is there some way to make the proc format more robust so that dashes or other characters return .U? It seems the other=_same_ isn't handling non-numeric characters. The log has an error of "Invalid data for pnc_mth in line xxx" Ideally I'd like to do this solely with proc format - changing from an old way in which we scanned the data for 'illegal' vars prior to formatting. Thank you, Anjali

anjgupta · ‎08-23-2011

Thanks to you both. Think it's working! Didn't know about the default option - the learning never stops. This is a huuuuggge help and I appreciate your time.

anjgupta · ‎08-23-2011

Would you mind dissecting/explaining it a bit? It chtono1. equivalent to chtono above? The '1' doesn't indicate length, does it? Are the lengths implied in the code above? My raw data is all on 1 line per client, non delimited. And the SAS code is created from a spreadsheet containing: varName fromData startPointer endPointer Row nformat fdobmo birth 0085 0086 1 2. fdobdy birth 0087 0088 1 2. ever_mar birth 0090 0090 1 chtono. married birth 0091 0091 1 chtono. pat_ack birth 0092 0092 1 chtono. mat_deg birth 0093 0093 1 degf. At least that's from my last attempt at changing nformat to include some created informats as well as lengths with char and numeric designations. Ever grateful, Anjali

anjgupta · ‎08-23-2011

Yeah - back to the drawing board. Argh. I do have the start and end column documented for each variable and can subtract them +1 to get the length. Basically - am I correct that as soon as you designate length you also imply if it is char or numeric? And then my attempt falls apart? I've been struggling with this for weeks - maybe time to quit the attempt for finesse. It's so close - the initially char variables are indeed ending up as numeric. Just an issue with reading in too much data due to the lack of a length. Anjali

anjgupta · ‎08-23-2011

Thanks for the heads up. I'll check. Maybe the @0090 etc will help designate the start of a new var ... probably not! Just trying to avoid the double name convention - reading in 1 var as character and renaming it to a numeric.

anjgupta · ‎08-23-2011

It *seems* to be working without designating the length. Will test more. Previously, I was reading in the raw data with the $char1. or 1. informat. Then I was trying to apply my user-defined formats and ran into the char vs numeric issue. Your suggestion to use my user-defined informats makes so much sense. And much less code - as I can read and format the vars in 1 step: MPRINT(CREATE_INPUT_STRING_D3): #1 @0090 ever_mar chtono. MPRINT(CREATE_INPUT_STRING_D3): #1 @0091 married chtono. MPRINT(CREATE_INPUT_STRING_D3): #1 @0092 pat_ack chtono. Fingers crossed - seems to work. Many thanks.

anjgupta · ‎08-23-2011

Thank you for the response. Why is the length of 1 problematic? I have put the formats in a file that I include at the start of the program. I think you're suggesting #1 @0090 ever_mar chotno. ? Is that correct? I will do so. Guess I need a bit more clarity - sorry for the hassle. Anjali

anjgupta · ‎08-23-2011

Hi, If I need to input the data and include the variables' lengths - how can I incorporate the suggested solution? 355 data stout.&state._RawBirthData ; /* data read in to become formatted data */ 356 infile stbirth LRECL=&birthreclength linesize=&birthlinesize 357 N=&birthLinesPerObs missover; 358 %create_code_statements(birthfmt, pramsvars) /*informats for formatting birth file */ ... MPRINT(CREATE_CODE_STATEMENTS): ever_mar = input(ever_mar, chtono.); MPRINT(CREATE_CODE_STATEMENTS): married = input(married, chtono.); ... MPRINT(CREATE_INPUT_STRING_D3): #1 @0090 ever_mar 1. MPRINT(CREATE_INPUT_STRING_D3): #1 @0091 married 1. ... NOTE: Invalid data for ever_mar in line 2 90-90. NOTE: Invalid data for married in line 2 91-91. Thank you, Anjali

anjgupta · ‎08-22-2011

Thank you. I think that will work - just need to test it with how I'm reading in the raw data. I think I need to avoid infiling the data as character initially. ag

anjgupta · ‎08-20-2011

I can try - but the cards would be 'Y', 'N', 'X'. The raw data are character and I'm trying to use the same variable name and end up with 1,2,.N and .U. Thank you

anjgupta · ‎08-18-2011

Hello, I'd like to read in a variable and have it change from character to numeric - retaining the same name. The issue I'm facing is when a character value of .U or .N is inputted into numeric - I lose the missing type and all become just dot (.) If this isn't possible I can create new variables and drop the character variables - but if there is any way .... I'm reading in variables as character and applying the format: proc format; invalue chtono 'Y'= 1 'N'= 2 'X'= .N other= .U; Which results in character values of '1', '2', 'N', and 'U'. When I attempt to change these to numbers - I lose the Ns and Us and only have 'generic' missings for them. Regardless of an initial character length of 1 or 2. I change them via: data new(drop=x ); birthdata01 (rename=(&name. =x)); &name.=input(x, 2.); run; Most likely there isn't a way for SAS to translate a character 'U' to a missing numeric value of .U but thought to ask.

Online Status	Offline
Date Last Visited	‎02-18-2016 03:54 PM

Re: order of statements within datastep

order of statements within datastep

order of statements within datastep

order of statements within datastep

find which version added NOCELLPERCENT

find which version added NOCELLPERCENT

SUDAAN noprint option - eliminate headers

proc surveymeans and domain - order of output

proc surveymeans and domain - order of output

proc surveymeans and domain - order of output

Handle unexpected characters with Proc Format

Handle unexpected characters with Proc Format

Handle unexpected characters with Proc Format

Handle unexpected characters with Proc Format

Handle unexpected characters with Proc Format

keep same name - change var from char to numeric. Missing type an iss...

keep same name - change var from char to numeric. Missing type an iss...

keep same name - change var from char to numeric. Missing type an iss...

keep same name - change var from char to numeric. Missing type an iss...

keep same name - change var from char to numeric. Missing type an iss...

keep same name - change var from char to numeric. Missing type an iss...

keep same name - change var from char to numeric. Missing type an iss...

keep same name - change var from char to numeric. Missing type an iss...

keep same name - change var from char to numeric. Missing type an iss...

keep same name - change var from char to numeric. Missing type an iss...