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: 
A_Kh
Tuesday
  • 293 Posts
  • 126 Likes Given
  • 37 Solutions
  • 95 Likes Received

Re: Variable name from horizontal to vertical in sas dataset (not in p...

by Barite | Level 11 in SAS Programming
‎09-01-2021 11:46 AM
‎09-01-2021 11:46 AM
Hi @japelin ,    Thank you for your feedback. There is a big dataset with more than 200 variables, with long variable names but with only single digits as a value. Having vertical variable name could make it shorter and easier to read.  ... View more

Variable name from horizontal to vertical in sas dataset (not in proc ...

by Barite | Level 11 in SAS Programming
‎09-01-2021 11:15 AM
‎09-01-2021 11:15 AM
Hi all,    Does anybody know if there is any technique to change variable name from horizontal to vertical? It should be in sas dataset, not in proc step outputs (as I know in proc print it is possible).    Ex:   I have  SUBJID AGE GENDER   Want   S               A           G            U               G          E            B               E           N            J                             D            I                              E            D                             R     Many thanks, in advance!   ... View more

Re: PROC FORMAT vs LENGTH: how to avoid data truncation?

by Barite | Level 11 in SAS Programming
‎08-04-2021 07:50 PM
‎08-04-2021 07:50 PM
I see this gives required attributes as format and length, not "the formatted value" which is "0", "1" and "2". In your print results we still see original values "Yes", "No" and "Unable..."..   I just modified formatting part of your code and see I'm getting both required metadata and value: proc format;                    value $nyu (default=57)   "No"= "0"                                                             "Yes"= "1"                                                             "Unable to ........."= "2"; run;   data WANT(drop=R);        set HAVE(rename=(RELREC=R));        attrib RELREC length=$2 format=$nyu. ;        RELREC=put(R,$nyu.); run;   proc print; proc contents; run;   Couldn't paste contents results here...Please check it and give your feedback.  Appreciate your support! ... View more

Re: PROC FORMAT vs LENGTH: how to avoid data truncation?

by Barite | Level 11 in SAS Programming
‎08-04-2021 10:37 AM
‎08-04-2021 10:37 AM
Hi @ChrisNZ ,    In this example '0', '1', '2' are treated as source values. And they get formatted into "Yes", "No" and "Unable to..".    My problem is the opposite of this. "Yes", "No" and "Unable to.." are source values.. I need to format them into '0', '1' and '2' and fit the string in $2 length.    @Tom 's example works, in one hand, to create a new variable with the length of $2 and conditionally convert RELREC values into "0", "1" and "2" of new variable, and rename it as RELREC. Then apply $NYU. format... But the formatted value is not the original value here. When format removed you cannot see "Yes", "No" and "Unable to.." values... ... View more

Re: PROC FORMAT vs LENGTH: how to avoid data truncation?

by Barite | Level 11 in SAS Programming
‎08-03-2021 09:08 PM
‎08-03-2021 09:08 PM
Hi @Tom ,    Thank you for your input! What I did not understand is I've created format for "YES", "NO" and "UNABLE TO.." values. like: proc format;              value $nyu "NO"= "0"                                 "YES"= "1"                                  "UNABLE TO ADJUDICATE DUE TO INSUFFICIENT INFORMATION"= "2"; run;   In your example below the format is applied to "0", "1" and "2" values of new_relrec variable (not to 'yes', 'no' 'unable to..')..... It does give me desired METADATA (when checked in proc contents), however I did not understand the logic here.     data want; set have; length new_relrec $2; if relrec='No' then new_relrec='0'; else if relrec='Yes' then new_relrec='1'; else if relrec=:'Unable to' then new_relrec='2'; drop relrec; rename new_relrec = relrec; format new_relres $nyu.; run;   ... View more

PROC FORMAT vs LENGTH: how to avoid data truncation?

by Barite | Level 11 in SAS Programming
‎08-03-2021 07:11 PM
‎08-03-2021 07:11 PM
Dear community,    I have a dataset (imported from xlsx each time when run the program) that has predefined LENGTH for variables to fit all their values.  eg:  SUBJID           RELREC A100101         Yes A100102         No A100103         Unable to adjudicate due to insufficient information   When imported into SAS SUBJID has a length of $27 while RELREC has $57.  Per my client's data standards (specifications), export dataset must have following LENGTH and FORMAT for above variables:  VARIABLE                  LENGTH             FORMAT              Expected VALUE RELREC                     $2                       $NYU.                   "0" ("No")                                                                                              "1" ("Yes")                                                                                              "2" ("Unable to Adjudicate due to....")   My challenge is when applying format and length in DATA step RELREC value is getting truncated and not properly formatted due to data truncation. eg: RELREC (formatted) 0 Ye Un   To my understanding LENGTH cannot be shorter than the variable's actual value. I tried to assign permanent format at the first data step, then assign length (to a new variable for renaming it later as RELREC) in a different data step. But still getting the same outcome.    I hope someone from this community had encountered the same issue/or has clear understanding on the behavior of LENGTH vs FORMAT statements and could give some guidance in resolving this issue.    Many thanks in advance!       ... View more

Re: LOCF and retain statement

by Barite | Level 11 in SAS Programming
‎08-02-2021 10:41 PM
1 Like
‎08-02-2021 10:41 PM
1 Like
The way you used DROP statement before set statement is something new that i learnt today. 😃 I usually use RETAIN before SET statement, DROP - at the very end or as a dataset options.. My confusion about intermediate variables started from there and I thought _: as a temporary (automatic) variable... #1 and #2 are familiar to me. ... View more

Re: LOCF and retain statement

by Barite | Level 11 in SAS Programming
‎08-02-2021 10:24 PM
‎08-02-2021 10:24 PM
Hi @mkeintz, I appreciate your feedback. Another good technique to solve my problem😃. I'll keep in mind the behavior of explicit output statement while using Update statement, vs implicit output when using Merge statement. Very helpful, thank you very much! ... View more

Re: LOCF and retain statement

by Barite | Level 11 in SAS Programming
‎08-02-2021 05:17 PM
1 Like
‎08-02-2021 05:17 PM
1 Like
Hi @jimbarbour ,    Thank you for explanation, that's very helpful. Your code is just awesome! I haven't seen intermediate variables like yours before (not considering first/last.variables, i and arrays..). Would you please give me references where I could learn these variables.  As I already accepted the previous answer as solution I did not have a second chance to accept your code as the solution, but it did solve my problem. Thank you, again, for your time and guidance! ... View more

Re: LOCF and retain statement

by Barite | Level 11 in SAS Programming
‎08-02-2021 05:08 PM
1 Like
‎08-02-2021 05:08 PM
1 Like
Hi @ballardw ,    Thank you for checking in with me. There is not any case where OUTCOME is different by SUBJID. And I see two codes above work perfectly for solving my problem.  ... View more

Re: LOCF and retain statement

by Barite | Level 11 in SAS Programming
‎08-02-2021 04:58 PM
1 Like
‎08-02-2021 04:58 PM
1 Like
Hi @r_behata ,    Thank you so much, it works perfectly! ... View more

LOCF and retain statement

by Barite | Level 11 in SAS Programming
‎07-30-2021 08:53 AM
1 Like
‎07-30-2021 08:53 AM
1 Like
Hi all,    I need your assistance in resolving following issue:   Dataset given: SUBJID         OUTCOME 111                 negative 111 111 222                positive 222   Expected result: SUBJID         OUTCOME 111                 negative 111                 negative 111                 negative 222                positive 222                positive   I've been trying it with RETAIN and FIRST and LAST VARIABLES combination, but somehow could not get the desired result.  Please share your experience and provide some guidance. Your support is highly appreciated! Thank you! ... View more

Re: conditionally creating variables

by Barite | Level 11 in SAS Programming
‎04-21-2021 12:51 PM
‎04-21-2021 12:51 PM
Hi again,    Initially number of COMMENT variables was indefinite and loop code supposed to create the appropriate number of COMMENT variables based on data length. Now there are only 10 COMMENT fields, instead of indefinite number. That's what I was referring to.    Anyway, this problem has been solved. I got rid of error NOTE in the log USING SUBSTRN function instead of SUBSTR.    Thank you for your time!  ... View more

Re: Improper order for GUESSINGROWS=MAX ?

by Barite | Level 11 in SAS Programming
‎04-19-2021 10:30 AM
‎04-19-2021 10:30 AM
I thing the error here is in PROC IMPORT statement. DATAFILE option doesn't refer to xlsx file.  Try this: PROC IMPORT DATAFILE= "C:\USERS\....\ARGENTINAARS.xlsx" proc import datafile= "C:\Users\pnguyen\OneDrive - Massey University\PhD JOURNEY\leniency & operating\dataxlsx\ARGENTINAARS" out= ARGENTINA_sheet1 dbms= xlsx replace;   ... View more

Re: conditionally creating variables

by Barite | Level 11 in SAS Programming
‎04-14-2021 05:50 PM
‎04-14-2021 05:50 PM
Hi again,    I initially accepted your code as a solution. It worked perfectly for the case when varying number of COMMENTS is used.  Now I have had a change to this data standards and number of comments set to 10. I applied the code to the new logic, it is correctly splitting the string into multiple comments, but generating error log for substr function as following:   .............long string above.....................................................i=2 _ERROR_=1 _N_=8 NOTE: Invalid third argument to function SUBSTR at line 906 column 29. NOTE: Invalid third argument to function SUBSTR at line 911 column 29. NOTE: Invalid third argument to function SUBSTR at line 916 column 29. NOTE: Invalid third argument to function SUBSTR at line 921 column 29. NOTE: Invalid third argument to function SUBSTR at line 926 column 29. NOTE: Invalid third argument to function SUBSTR at line 931 column 29.   Would you please advise how to get rid of this error log?    Thank you again, and I really appreciate your help! ... View more
Contact Me
Online Status
Offline
Date Last Visited
Tuesday
Group Hubs for A_Kh
View All
Likes given to
Quick links