cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
nnn123
‎07-15-2019
  • 16 Posts
  • 0 Likes Given
  • 0 Solutions
  • 2 Likes Received

Re: Logistic Regression in SAS Enterprise Guide

by Fluorite | Level 6 in New SAS User
‎07-04-2019 04:01 AM
‎07-04-2019 04:01 AM
My script in the {i} window keeps getting bounced as Spam so I've notified the moderator as per sites instructions ... View more

Re: Logistic Regression in SAS Enterprise Guide

by Fluorite | Level 6 in New SAS User
‎07-04-2019 03:59 AM
‎07-04-2019 03:59 AM
real time 0.01 seconds 2 The SAS System 07:49 Thursday, July 4, 2019 cpu time 0.01 seconds 49 50 DATA WORK.TMPMod; 51 SET WORK.SORTTempTableSorted; 52 length __RESPONSE $ 10; 53 IF Q14a=1 THEN __RESPONSE="01: 1"; 54 IF Q14a=2 THEN __RESPONSE="02: 2"; 55 IF Q14a=3 THEN __RESPONSE="03: 3"; 56 RUN; NOTE: There were 68746 observations read from the data set WORK.QUESTION_DATA_AND_STRATA. NOTE: MVA_DSIO.OPEN_CLOSE| _DISARM| STOP| _DISARM| 2019-07-04T08:45:25,802+01:00| _DISARM| WorkspaceServer| _DISARM| SAS| _DISARM| | _DISARM| 68746| _DISARM| 22904832| _DISARM| 11| _DISARM| 11| _DISARM| 166839623| _DISARM| 10854296320| _DISARM| 0.156250| _DISARM| 0.203000| _DISARM| 1877845525.600000| _DISARM| 1877845525.803000| _DISARM| 0.062500| _DISARM| | _ENDDISARM NOTE: There were 68746 observations read from the data set WORK.SORTTEMPTABLESORTED. NOTE: MVA_DSIO.OPEN_CLOSE| _DISARM| STOP| _DISARM| 2019-07-04T08:45:25,819+01:00| _DISARM| WorkspaceServer| _DISARM| SAS| _DISARM| | _DISARM| -1| _DISARM| 22904832| _DISARM| 11| _DISARM| 11| _DISARM| 166839629| _DISARM| 10854296603| _DISARM| 0.171875| _DISARM| 0.219000| _DISARM| 1877845525.600000| _DISARM| 1877845525.819000| _DISARM| 0.078125| _DISARM| | _ENDDISARM NOTE: The data set WORK.TMPMOD has 68746 observations and 72 variables. NOTE: MVA_DSIO.OPEN_CLOSE| _DISARM| STOP| _DISARM| 2019-07-04T08:45:25,819+01:00| _DISARM| WorkspaceServer| _DISARM| SAS| _DISARM| | _DISARM| 68746| _DISARM| 22904832| _DISARM| 11| _DISARM| 11| _DISARM| 167036755| _DISARM| 10854494020| _DISARM| 0.171875| _DISARM| 0.219000| _DISARM| 1877845525.600000| _DISARM| 1877845525.819000| _DISARM| 0.078125| _DISARM| | _ENDDISARM NOTE: PROCEDURE| _DISARM| STOP| _DISARM| 2019-07-04T08:45:25,819+01:00| _DISARM| WorkspaceServer| _DISARM| SAS| _DISARM| | _DISARM| 340316160| _DISARM| 22904832| _DISARM| 11| _DISARM| 11| _DISARM| 167202693| _DISARM| 10854494298| _DISARM| 0.187500| _DISARM| 0.235000| _DISARM| 1877845525.584000| _DISARM| 1877845525.819000| _DISARM| 0.078125| _DISARM| | _ENDDISARM NOTE: DATA statement used (Total process time): real time 0.23 seconds cpu time 0.18 seconds 57 58 TITLE; 59 TITLE1 "Logistic Regression Results"; 60 FOOTNOTE; 61 FOOTNOTE1 "Generated by the SAS System (&_SASSERVERNAME, &SYSSCPL) on %TRIM(%QSYSFUNC(DATE(), NLDATE20.)) at 61 ! %TRIM(%SYSFUNC(TIME(), TIMEAMPM12.))"; 62 PROC LOGISTIC DATA=WORK.TMPMod 63 PLOTS(ONLY)=ALL 64 ; 65 WEIGHT Q14a_Weight; 66 MODEL __RESPONSE=MethodCollection Gender AgeBand_1_2 Ethnicity Translated_recoded Sexuality_recode Religion PSR 66 ! SupportSetting MechanismDelivery Q1Std Q1ER Q1Comb Q2Std Q2ER Q2Comb Q2b Q2c Q3a Q3b Q4a Q4b Q5a Q5b Q6a Q6b Q7a Q7b Q8a 66 ! Q8b Q9a Q9b Q10 Q11 Q12 Q12sub Q12_recode Q13 Q13_recode Q14b Q15a Q15b Q15c Q15d Q16a Q16b Q16c Q16d Q17 Q18 Q19a Q19b 66 ! Q19c Q20a Q20b Q20c Q21 Q22a Q22b Q22c Q22d Q22e Q22f Q22Flag Q22bsub Q22csub Q22dsub Q22esub Q22fsub / 67 SELECTION=BACKWARD 68 SLS=0.05 69 INCLUDE=0 70 COVB 71 RSQUARE 72 LINK=LOGIT 73 CLPARM=BOTH 74 CLODDS=BOTH 75 ALPHA=0.05 76 ; 77 RUN; 3 The SAS System 07:49 Thursday, July 4, 2019 ERROR: There are no valid observations. NOTE: The SAS System stopped processing this step because of errors. NOTE: There were 68746 observations read from the data set WORK.TMPMOD. NOTE: MVA_DSIO.OPEN_CLOSE| _DISARM| STOP| _DISARM| 2019-07-04T08:45:25,944+01:00| _DISARM| WorkspaceServer| _DISARM| SAS| _DISARM| | _DISARM| 68746| _DISARM| 22904832| _DISARM| 11| _DISARM| 11| _DISARM| 40191768| _DISARM| 10894753102| _DISARM| 0.062500| _DISARM| 0.094000| _DISARM| 1877845525.850000| _DISARM| 1877845525.944000| _DISARM| 0.046875| _DISARM| | _ENDDISARM NOTE: PROCEDURE| _DISARM| STOP| _DISARM| 2019-07-04T08:45:25,944+01:00| _DISARM| WorkspaceServer| _DISARM| SAS| _DISARM| | _DISARM| 340316160| _DISARM| 22904832| _DISARM| 11| _DISARM| 11| _DISARM| 40258326| _DISARM| 10894753384| _DISARM| 0.062500| _DISARM| 0.094000| _DISARM| 1877845525.850000| _DISARM| 1877845525.944000| _DISARM| 0.046875| _DISARM| | _ENDDISARM NOTE: PROCEDURE LOGISTIC used (Total process time): real time 0.09 seconds cpu time 0.06 seconds 78 QUIT; 79 80 /* ------------------------------------------------------------------- 81 End of task code 82 ------------------------------------------------------------------- */ 83 RUN; QUIT; 84 %_eg_conditional_dropds(WORK.SORTTempTableSorted, 85 WORK.TMPMod); ... View more

Re: Logistic Regression in SAS Enterprise Guide

by Fluorite | Level 6 in New SAS User
‎07-04-2019 03:59 AM
‎07-04-2019 03:59 AM
Hi Paige thank you for replying. I will paste the Log code as you suggest cheers ... View more

Logistic Regression in SAS Enterprise Guide

by Fluorite | Level 6 in New SAS User
‎07-03-2019 12:23 PM
‎07-03-2019 12:23 PM
Hello,   I've been using an existing SAS EG job to process some survey information and am having a problem with a part of the job that does Logistic Regression.   I have used the in-built 'Logistic Regression' wizard menu in SAS EG and put the results of Question 1 in as the primary ('dependent' I think it's called?) variable and then all the other questions as secondary and followed the process through and it's showing me the p-values, weighted frequencies etc perfectly.   This has worked with nearly all the survey questions (Q2 vs all, Q3 vs all etc) but when I try plotting Question 14 vs all the LR step doesn't run and the log displays the message: ERROR: There are no valid observations   The data for this question is exactly the same as all the others (the responses to the survey are recorded as numbers 1 to 6) and the data quality is the same, no blanks, no NULL, no errors etc so does anyone know why it might be displaying this error for me when I'm using the LR wizard in exactly the same way? Q19 and Q20 are also not running, but also look fine in the raw data.   Thank you for any help you can offer! James ... View more

Re: proc surveyfreq syntax

by Fluorite | Level 6 in SAS Enterprise Guide
‎11-13-2018 10:22 AM
‎11-13-2018 10:22 AM
Hi FreelanceReinhard,   Thanks for such a quick response! These codes below create a separate table for each question though. I want them all in one big table if at all possible? There are 22 questions in the survey so it would create 21 mini tables otherwise.   Is this possible? ... View more

proc surveyfreq syntax

by Fluorite | Level 6 in SAS Enterprise Guide
‎11-13-2018 10:01 AM
‎11-13-2018 10:01 AM
Hi,   I'm currently working with some stratified survey data and want to run out big tables of one set of responses versus another. i.e. how did individuals that answered question 1 subsequently answer question 2, question 3, question 4 etc.   So far i have got this code running producing exactly what i want in a 'program' sheet within SAS EG:   proc surveyfreq data=QUESTION_DATA_AND_STRATA nosummary; tables Q1 * Q2/ row; strata LaCode; weight Q1_Weight; run;   The only limitation to this though is that this only shows question 1 vs question 2 - I am having to copy it each time for each question. How can i put multiple questions in so I get one big table with more manageable results? Either stacked side by side as columns or underneath each other as rows, it doesn't matter to me. I can't get the syntax right (line 2 is the issue), I've been trying things such as these below with no luck:   proc surveyfreq data=QUESTION_DATA_AND_STRATA nosummary; tables Q1 * Q2/ row; tables Q1 * Q3/ row strata LaCode; weight Q1_Weight; run;   and    proc surveyfreq data=QUESTION_DATA_AND_STRATA nosummary; tables Q1 * Q2; Q1 * Q3/ row; strata LaCode; weight Q1_Weight; run; ... View more

Re: Sorting data in SAS EG

by Fluorite | Level 6 in SAS Enterprise Guide
‎03-16-2018 09:22 AM
‎03-16-2018 09:22 AM
This is excellent thanks Patrick! Just what I needed 🙂 ... View more

Re: Sorting data in SAS EG

by Fluorite | Level 6 in SAS Enterprise Guide
‎03-16-2018 08:55 AM
2 Likes
‎03-16-2018 08:55 AM
2 Likes
i don't have a clue what that means - how's this: data have; input code name $ breakdown $ type $ measure_Value; datalines; 1 Leeds Total Total 450 1 Leeds Male Total 180 1 Leeds Female Total 270 1 Leeds 18-64 Total 160 1 Leeds 65 and over Total 290 1 Leeds Total Denominator 450 1 Leeds Male Denominator 180 1 Leeds Female Denominator 270 1 Leeds 18-64 Denominator 160 1 Leeds 65 and over Denominator 290 1 Leeds Total Numerator 450 1 Leeds Male Numerator 180 1 Leeds Female Numerator 270 1 Leeds 18-64 Numerator 160 1 Leeds 65 and over Numerator 290 3 Manchester Total Total 500 3 Manchester Male Total 195 3 Manchester Female Total 305 3 Manchester 18-64 Total 170 3 Manchester 65 and over Total 171 3 Manchester Total Denominator 500 3 Manchester Male Denominator 195 3 Manchester Female Denominator 305 3 Manchester 18-64 Denominator 170 3 Manchester 65 and over Denominator 171 3 Manchester Total Numerator 500 3 Manchester Male Numerator 195 ; run; ... View more

Re: Sorting data in SAS EG

by Fluorite | Level 6 in SAS Enterprise Guide
‎03-16-2018 08:11 AM
‎03-16-2018 08:11 AM
Code Name Breakdown Type Measure Value 1 Leeds Total Total 450 1 Leeds Male Total 180 1 Leeds Female Total 270 1 Leeds 18-64 Total 160 1 Leeds 65 and over Total 290 1 Leeds Total Denominator 450 1 Leeds Male Denominator 180 1 Leeds Female Denominator 270 1 Leeds 18-64 Denominator 160 1 Leeds 65 and over Denominator 290 1 Leeds Total Numerator 450 1 Leeds Male Numerator 180 1 Leeds Female Numerator 270 1 Leeds 18-64 Numerator 160 1 Leeds 65 and over Numerator 290 3 Manchester  Total Total 500 3 Manchester  Male Total 195 3 Manchester  Female Total 305 3 Manchester  18-64 Total 170 3 Manchester  65 and over Total 171 3 Manchester  Total Denominator 500 3 Manchester  Male Denominator 195 3 Manchester  Female Denominator 305 3 Manchester  18-64 Denominator 170 3 Manchester  65 and over Denominator 171 3 Manchester  Total Numerator 500 3 Manchester  Male Numerator 195 3 Manchester  Female Numerator 305 3 Manchester  18-64 Numerator 170 3 Manchester  65 and over Numerator 171 2 York Total Total 500 2 York Male Total 195 2 York Female Total 305 2 York 18-64 Total 170 ... View more

Sorting data in SAS EG

by Fluorite | Level 6 in SAS Enterprise Guide
‎03-16-2018 07:40 AM
‎03-16-2018 07:40 AM
Hi,   Using the example attached, is it possible to filter the data so it goes (in order of priority): 1. A-Z ascending on 'Name' then 2. Breakdown column ordered 'Total', 'Male', 'Female', '18-64', '65 and over' then 3. Type column ordered 'Total', 'Denominator' then 'Numerator'   I have done this manually in Excel for now but would like it automating in my SAS job   Thanks, James ... View more

Re: concatenate in column names

by Fluorite | Level 6 in SAS Enterprise Guide
‎01-25-2018 05:22 AM
‎01-25-2018 05:22 AM
Hi Kurt,   thanks for your input - unfortunately the column headings have to be like that in the Excel file this output will be pasted into, I realise they are not ideal. I just wondered if any formula (concatenate etc) can be worked into column names in any way ... View more

Re: concatenate in column names

by Fluorite | Level 6 in SAS Enterprise Guide
‎01-25-2018 05:01 AM
‎01-25-2018 05:01 AM
Thanks Andreas,   I want the column names to be like that purely because they are to be exported straight into an Excel file for publication, and the heading names in Excel are the format of "OUTCOME_MAR-2018" and can not be changed.   There will definitely only ever be one year in the YEAR field because the person running the job has chosen the year earlier via a prompt screen. If for example next year the user selects 2017, then I want the columns to automatically default to OUTCOME_MAR-2017 ... View more

concatenate in column names

by Fluorite | Level 6 in SAS Enterprise Guide
‎01-25-2018 04:40 AM
‎01-25-2018 04:40 AM
Hi,   Currently I have columns in SAS table called "OUTCOME_MAR-" , "OUTCOME-APR-", "OUTCOME-MAY-" etc and in the same table I have a column called YEAR which simply contains the year in every row (user-defined by a prompt at start of the process). OUTCOME_MAR- OUTCOME_APR- OUTCOME_MAY- OUTCOME_JUN- YEAR 10 20 30 5 2018 20 15 20 15 2018 10 10 10 20 2018 15 10 5 30 2018       Say for example if the YEAR column is populated with '2018' I then want to be able to automatically rename my columns to "OUTCOME_MAR-2018", "OUTCOME_APR-2018" in the query builder, is this possible? I can't see how I can use any formula in the 'column name' text box where I can reference other data or concatenate values. This is what I want: OUTCOME_MAR-2018 OUTCOME_APR-2018 OUTCOME_MAY-2018 OUTCOME_JUN-2018 10 20 30 5 20 15 20 15 10 10 10 20 15 10 5 30   Thanks ... View more
Contact Me
Online Status
Offline
Date Last Visited
‎07-15-2019 04:52 AM
Likes from
View All
Quick links