This problem is related to the community post area.  When I started posting on this community August 2020, everything was fine. I asked another question last Friday and somehow I found myself unable to reply to other people's replies. All I can do is "accept as solution" or "edit post" which allows me to edit my original post.  Where did the "reply" or "quick reply" button go?  I can still ask questions like I'm doing now. It's just I can't reply to other people's replies to my post.  The only thing I can do now is edit my post where I can @ people who replied to my post.  Can someone help me with this problem? I wonder if it's related to my account or browser. I guess it's not the browser as I'm using the latest Chrome. For example, here:  is Hash Table many keys to one key match doable?  and I can't reply to others' posts either. There is simply not a "reply" button anywhere, even in the vertical three dots under my picture. ... View more

I'm trying to match keys 'A' and 'B' both to key 'C'. I wonder if this is doable in hash table. Simplified version of this problem: key: Location, Gender Value: Pet data dict; infile datalines; input Location$ Gender $ Pet $; datalines; GreenBay M Dog Madison F Badger Milwaukie B Cat ; run; data have; infile datalines; input Subject$ Location$ Gender$; datalines; 1 GreenBay M 2 Madison F 3 Milwaukie M 4 Milwaukie F ; run; data want; infile datalines; input Subject$ Location$ Gender$ Pet$; datalines; 1 GreenBay M Dog 2 Madison F Badger 3 Milwaukie M Cat 4 Milwaukie F Cat ; run; Using 'dict' dataset as hashtable, I want the result 'want' dataset. Obviously, F and M in 'have' dataset should both match to B (means both) in dict dataset. Can we do something to the hash table to make this happen?  I can solve this in some non-hashtable ways: 1. alter work.dict so that if we see a B, we output(copy) it into 2 rows with F and M 2. proc sql left join. In reality, both 'have' dataset and 'dict' dataset have about 1000 rows so I really don't want to use the methods above. ... View more

This question has been asked before but I did not understand the explanation. Old link: https://communities.sas.com/t5/General-SAS-Programming/PROC-SQL/td-p/314917 The data is here: data work.pilots; infile datalines; input id name $ Jobcode $ Salary; datalines; 001 Albert PT1 50000 002 Brenda PT1 70000 003 Carl PT1 60000 004 Donna PT2 80000 005 Edward PT2 90000 006 Flora PT3 100000 ; run; We want to get a result that looks like this: Jobcode Salary Avg ------- ------ ----- PT1 50000 60000 PT1 70000 60000 PT1 60000 60000 PT2 80000 85000 PT2 90000 85000 PT3 100000 100000 It seems that the results come from average(salary) by group, ordered by id. Why does the code below work? The part I don't understand is highlighted in red. select Jobcode, Salary, (select avg(Salary) from WORK.PILOTS as P1 where P1.Jobcode=P2.Jobcode) as Avg from WORK.PILOTS as P2 order by Id ; Here's what I'm thinking about the red part subquery: select avg(salary) from work.pilots as p1 this gives us 1 value of avg(all salaries) in p1. It has no jobcode column. Thus the next line "where p1.jobcode = p2.jobcode" should not work. This would make more sense: select avg(Salary) from WORK.PILOTS as P1 group by jobcode However this code, although giving us 3 averages for 3 jobcodes, does not have an one-to-one relationship with pilots.id Can anyone explain step by step on how the codes marked in red works?   ... View more

Hello all, I used the exact code here in https://documentation.sas.com/?docsetId=proc&docsetTarget=n1w1xy48wd290bn1mqalitn7wy13.htm&docsetVersion=9.4&locale=en   My sas somehow cannot separate the txt file columns by tab. My log is pasted below: I changed text color for line 87-89.  It seems that SAS knows that I'm using delimeter by tab. It just fails to separate columns by '09'x I'm using SAS Studio the web client with virtualbox win10   1 OPTIONS NONOTES NOSTIMER NOSOURCE NOSYNTAXCHECK; 72 73 proc import datafile="/folders/myfolders/BOOK/cert/class.txt" out=class dbms=dlm replace; 74 datarow=5; 75 delimiter='09'x; 76 run; NOTE: Unable to open parameter catalog: SASUSER.PARMS.PARMS.SLIST in update mode. Temporary parameter values will be saved to WORK.PARMS.PARMS.SLIST. 77 /********************************************************************** 78 * PRODUCT: SAS 79 * VERSION: 9.4 80 * CREATOR: External File Interface 81 * DATE: 03AUG20 82 * DESC: Generated SAS Datastep Code 83 * TEMPLATE SOURCE: (None Specified.) 84 ***********************************************************************/ 85 data WORK.CLASS ; 86 %let _EFIERR_ = 0; /* set the ERROR detection macro variable */ 87 infile '/folders/myfolders/BOOK/cert/class.txt' delimiter='09'x MISSOVER DSD lrecl=32767 firstobs=5 ; 88 informat Name_____Gender___Age $20. ; 89 format Name_____Gender___Age $20. ; 90 input 91 Name_____Gender___Age $ 92 ; 93 if _ERROR_ then call symputx('_EFIERR_',1); /* set ERROR detection macro variable */ 94 run; NOTE: The infile '/folders/myfolders/BOOK/cert/class.txt' is: Filename=/folders/myfolders/BOOK/cert/class.txt, Owner Name=root,Group Name=vboxsf, Access Permission=-rwxrwx---, Last Modified=02Aug2020:19:43:43, File Size (bytes)=1620 NOTE: 16 records were read from the infile '/folders/myfolders/BOOK/cert/class.txt'. The minimum record length was 80. The maximum record length was 80. NOTE: The data set WORK.CLASS has 16 observations and 1 variables. NOTE: DATA statement used (Total process time): real time 0.01 seconds cpu time 0.00 seconds 16 rows created in WORK.CLASS from /folders/myfolders/BOOK/cert/class.txt. NOTE: WORK.CLASS data set was successfully created. NOTE: The data set WORK.CLASS has 16 observations and 1 variables. NOTE: PROCEDURE IMPORT used (Total process time): real time 0.11 seconds cpu time 0.05 seconds 95 96 proc print data=class; 97 run; NOTE: There were 16 observations read from the data set WORK.CLASS. NOTE: PROCEDURE PRINT used (Total process time): real time 0.05 seconds cpu time 0.05 seconds 98 99 OPTIONS NONOTES NOSTIMER NOSOURCE NOSYNTAXCHECK; 111 ... View more