All New SAS User posts

Re: About base exam

Reeza — Tue, 11 Aug 2020 20:35:40 GMT

Where are you getting your practice questions from? SAS changed the exam structure last year (July?), perhaps the material hasn't been updated to match.

About base exam

Jianan_luna — Tue, 11 Aug 2020 20:17:04 GMT

I am planning to take Programming Associate/Base Programming Specialist. I am confused whether INFILE/ARRAY/INPUT statement included in the exam. I check the exam guide, there is nothing related it. But when I do the practice questions, there are some related it. Thanks so much.

Re: SAS Sudio Sends Data to SAS?

Cynthia_sas — Mon, 10 Aug 2020 23:34:20 GMT

Hi:
When you say that you are "less familiar with Enterprise or 9.4", I assume you mean SAS Enterprise Guide or SAS Display Manager on Windows, also known as the SAS Windowing Environment.

An editor is an editor is an editor is an editor (with apologies to Gertrude Stein). All of the SAS Editors have a place to type code; all of the SAS Editors have a way for you to review the SAS log after the code runs. All of the SAS Editors have a way to review results. The look and feel of the editors is different. How you launch each editor is a bit different. How you submit code is a bit different (click the little running man or click the Run menu item). How and where you save code is different. How you address files is slightly different. But this is all minor and you can learn to work with the differences.

SAS Enterprise Guide, SAS Studio, SAS Display Manager on Windows are all just different ways to communicate with SAS -- different graphical user interfaces. SAS Enterprise Guide and SAS Studio can work with your code and send it to the main SAS executable program. That main SAS program can reside in any of these places:
1) a local install on a Windows C: drive
2) a network install on a company server
3) a Business Intelligence platform install (like #2, only with a metadata server and more security and other servers in the mix)
4) a cloud install, such as using SAS Studio and Enterprise Guide with SAS on a cloud server (such as our SAS OnDemand for Academics cloud server or an company cloud either on-premises or hosted remotely)

#1, #2 and #3 above are typically company or school configurations. #4 could be a company configuration, but it is also the way we deliver free access to SAS for non-commercial learning purposes. I would NOT recommend uploading your own data, especially patient data to our SODA server just because you only want to use SAS Studio.

SAS University Edition on a Virtual Machine uses SAS Studio to communicate with SAS inside the Unix Virtual Machine. However, SAS Enterprise Guide and SAS on Windows will NOT communicate with SAS this way when using SAS University Edition.

I could type my SAS programs in Notepad or Wordpad or Textpad or even in Word. But I can't submit the code to SAS from any of those editors. However, assuming I saved my typed program and I knew the location of the SAS executable program and I have the right permissions, I could go to a command window and batch submit my SAS program (in most of the above usage scenarios).

We have lots of videos that show how to use Enterprise Guide and if you are a student at NCSU, as your username implies, then you could access training via NCSU's license. You could send mail to elearn@sas.com to find out how a student can access Enterprise Guide training.

Hope this helps convince you to give Enterprise Guide a try. SAS Studio isn't your only resource.
Cynthia

Re: Question about means ins SAS 9.4

Annie_Fréchette — Mon, 10 Aug 2020 23:18:39 GMT

Yep! These data are medical histories of these ladies... So it is treated just as humans data.

I'll make up fake data next time!

Thanks again Paige!

Re: SAS Sudio Sends Data to SAS?

Reeza — Mon, 10 Aug 2020 21:57:22 GMT

If you're using Academics on Demand, this your data is in the SAS cloud and this likely violates your companies policies. Since you're mentioning a training environment, I suspect your colleague is correct and your data would be sent externally.
If you're using SAS University Edition then no data is sent externally, but usage statistics are sent to the server.
If you're using a custom installation of SAS Studio then no data is sent externally.

Re: Question about means ins SAS 9.4

PaigeMiller — Mon, 10 Aug 2020 21:20:43 GMT

Data on cows is "sensitive"? It's not like you are publishing a person's medical history. And in any event, if it is "sensitive", then you can make up fake data with fake cow ID to match your problem.

Re: Question about means ins SAS 9.4

Annie_Fréchette — Mon, 10 Aug 2020 20:52:41 GMT

hi Paige!

Sorry for everyhting, I accepted your first post cause I did add a mean function and it worked.

/*1, tranposer pour avoir une seule ligne par lactation*/
proc sort data=qulac;
by no_ferme cow lac;
run;
proc transpose data=qulac out=qulact prefix=LS_;
var SCC_linear_score;
by no_ferme cow lac;
run;
/*2 calculer une moyenne par lactation*/
data qulact;
set qulact;
lsmean=mean(ls_1, ls_2, ls_3, ls_4, ls_5, ls_6, ls_7, ls_8, ls_9, ls_10, ls_11, ls_12, ls_13);
run;

So you have answered my question, thanks again. I was writing a part of my "first" code because I tought that is what you have asked, but obviously it is not... I'm not really familiar with the use of macros and my data are sensitive, but in the future i will try my best to meet your demands.

Best regards,

Annie

SAS Sudio Sends Data to SAS?

jmpalumbNCSU — Mon, 10 Aug 2020 20:37:19 GMT

Hello all, I'm learning to use SAS Studio as it's the coding environment the training modules were taught in and I'm not the most computer literate person, so to make things easier on myself I've been using it alone. My coworker who requested that I take the training says that I cannot use the SAS Studio environment for our data as it takes the form of patient records and is therefore shared with SAS when I use Studio. Is this true? I'd like to continue using it if I can since I'm much less familiar with Enterprise or 9.4 which are also on this PC. Please advise.

Re: Question about means ins SAS 9.4

PaigeMiller — Mon, 10 Aug 2020 20:22:24 GMT

Until I see your data as SAS data step code, I can't respond to your specific question.

It does seem to me that PROC SORT and PROC TRANSPOSE are not needed, and you didn't even try the MEAN() function in a data step.

Re: SAS DAte conversion to numeric

Tom — Mon, 10 Aug 2020 19:11:07 GMT

SAME will only yield the same result as END with the starting date is the 31st day of the month.

1541  data example;
1542     thisdate = '30APR2020'd ;
1543     samedate = intnx('month',thisdate,1,'s');
1544     lastdate = intnx('month',thisdate,1,'e');
1545     format _all_ date9.;
1546     put (_all_) (=/);
1547  run;


thisdate=30APR2020
samedate=30MAY2020
lastdate=31MAY2020

Re: Question about means ins SAS 9.4

Annie_Fréchette — Mon, 10 Aug 2020 18:55:30 GMT

Hi! Thank you, will try it! I wasn't sure what part of code I should write because I have just transposed a table...

/*1, tranposer pour avoir une seule ligne par lactation*/
proc sort data=qulac;
by no_ferme cow lac;
run;
proc transpose data=qulac out=qulact prefix=LS_;
var SCC_linear_score;
by no_ferme cow lac;
run;

Should I create a small subsample of data (cards) at first?

Thanks, I'm tryin to follow the requests, but strugglin a little bit!;)

Re: Question about means ins SAS 9.4

PaigeMiller — Mon, 10 Aug 2020 18:42:39 GMT

You can use the MEAN() function in a data step.

Normally, and in the future, we ask you to provide data as SAS data step code and not as screen captures. If you want us to write code to help you, please provide data in the desired form.

Question about means ins SAS 9.4

Annie_Fréchette — Mon, 10 Aug 2020 18:25:48 GMT

Hi! I'm tryin to calculate a mean LS for a lac (see the print screen) Not every cow have the same number of test in their lactation. How can I code SAS for this: Sum all the LS ne . then divide it by the number of LS ne . And put the result in a new variable called LSmean.

Thanks you very much!!

Re: SAS DAte conversion to numeric

ballardw — Mon, 10 Aug 2020 17:32:44 GMT

You several problems in your example. If 2020-04-31 is supposed to be 31 April 2020 then that date is not a valid date to begin with.

If you want SAS to modify date values then you should look at the INTNX function.

https://communities.sas.com/t5/SAS-Communities-Library/Working-with-Dates-and-Times-in-SAS-Tutorial/ta-p/424354 has a PDF with much information about dates.

Since you are apparently passing this to Teradata then there is strong likelihood that somewhere you have a data value that is not handled correctly as well. I have no idea what a date like

1200431

is supposed to represent, so I am assuming that is some sort of Teradata convention.

A basic date change example in SAS:

data example;
   thisdate = '30APR2020'd ;
   otherdate = intnx('month',thisdate,10,'s');
   format thisdate otherdate date9.;
run;

The last parameter of the INTNX function is an alignment, you can have a date returned that is the begining of the period, use 'B', the end of the period, use 'E' or the same point in the target period, use 'S'. Since the example is using the last data of a month the 'same' is the last day of the target month.

Re: Is my output correct

ballardw — Mon, 10 Aug 2020 17:16:45 GMT

Typically when a phrase like "between the age of 18 - 50 years" is used then the data should be subsetted to that range, typically with a Where statement or data set option. Your frequencies for Age don't show any ages outside that range so go so far.

However you apparently have multiple "gender" variables and we have no way of knowing which is the "current" value. From the request, that is the only one that should be used.

Since the request says "a frequency table of current gender and sexual orientation " I would normally interpret that as meaning first, one table, not 6 plus and graphs, and second that you have gender and orientation in a single table. If race is not part of the request do not include it, if required then describe how race is supposed to be included.

In Proc Freq that would be a Tables statement like: Tables genderc*sex_o;

With the stated requirement and the shown output, if I were grading this as an assignment it would likely get a D because no where do you have gender and orientation together.

If the requirement does not want graphs then turn of the graphs before running proc freq.

Re: What does it mean if SAS says variable type is not on file?

Kimberly_2020 — Mon, 10 Aug 2020 16:48:58 GMT

It worked! Thank you!

Re: What does it mean if SAS says variable type is not on file?

Reeza — Mon, 10 Aug 2020 16:44:30 GMT

proc freq data=WORK.SYPHILIS;
where18<=age<=50;
tables genderB genderC sex_o RACE age / plots=(freqplot cumfreqplot);
run;

This is likely what you want.

Your TYPE portion doesn't make sense since those are variable names. Not sure what you were expecting to happen within that portion of code but it doesn't do what you think it does 🙂

Re: What does it mean if SAS says variable type is not on file?

Kimberly_2020 — Mon, 10 Aug 2020 16:32:39 GMT

Thank you!

Re: What does it mean if SAS says variable type is not on file?

Kimberly_2020 — Mon, 10 Aug 2020 16:31:42 GMT

variables called genderB and genderC

Is my output correct

Kimberly_2020 — Mon, 10 Aug 2020 16:28:29 GMT

"Create a frequency table of current gender and sexual orientation for patients between the age of 18 - 50 years" was my instructions...I want to know if my output is correct. Please see attachment.

Re: What does it mean if SAS says variable type is not on file?

Reeza — Mon, 10 Aug 2020 16:24:28 GMT

It seems like you're confusing variable values and variable names.

Is your variable called type with values of genderB, genderC or do you have variables called genderB, genderC?

I guarantee that code is not correct or at least what you want or expect.

Re: What does it mean if SAS says variable type is not on file?

Reeza — Mon, 10 Aug 2020 16:23:00 GMT

I'm guessing the error means SAS doesn't think you have a variable called TYPE in your syphilis data base. You can check this in your IMPORT code or via PROC CONTENTS. You'll want to check the label versus name as well, this is a common mistake to use the labels instead of names.

Re: What does it mean if SAS says variable type is not on file?

Kimberly_2020 — Mon, 10 Aug 2020 16:22:00 GMT

That worked but it gave me a frequency table for all ages and not age 18-50 like before. My instructions were to create a frequency table of current gender and sexual orientation for patients between the age of 18 - 50 years.

proc freq data=WORK.SYPHILIS;
	proc contents data=work.syphilis;
	tables genderB genderC sex_o RACE age / plots=(freqplot cumfreqplot);
	where Type in ("genderB", "genderC", "sex_o", "RACE") and 18<=age<=50;
run;

Re: What does it mean if SAS says variable type is not on file?

Kimberly_2020 — Mon, 10 Aug 2020 16:11:26 GMT

And I already imported the CSV file into SAS

Re: What does it mean if SAS says variable type is not on file?

Reeza — Mon, 10 Aug 2020 15:59:36 GMT

Run a PROC CONTENTS on your data set and check the name AND label of your variables.

What does it mean if SAS says variable type is not on file?

Kimberly_2020 — Mon, 10 Aug 2020 15:52:31 GMT

Hello there,

SAS keeps saying that the variable type is not on file....What does this mean? WHen I did a one way frequency table without the where statement it ran...But when I made this edit, it didn't.

Code:
proc freq data=WORK.SYPHILIS;
	tables genderB genderC sex_o RACE age / plots=(freqplot cumfreqplot);
	where Type in ("genderB", "genderC", "sex_o", "race") and 18<=age<=50;
run;

Log: 

1          OPTIONS NONOTES NOSTIMER NOSOURCE NOSYNTAXCHECK;
 SYMBOLGEN:  Macro variable _SASWSTEMP_ resolves to /home/u49152646/.sasstudio/.images/db1b9e49-6774-45a2-9899-069be7ad3673
 SYMBOLGEN:  Some characters in the above value which were subject to macro quoting have been unquoted for printing.
 SYMBOLGEN:  Macro variable GRAPHINIT resolves to GOPTIONS RESET=ALL GSFNAME=_GSFNAME;
 72         
 73         /*
 74          *
 75          * Task code generated by SAS Studio 3.8
 76          *
 77          * Generated on '8/10/20, 8:32 AM'
 78          * Generated by 'u49152646'
 79          * Generated on server 'ODAWS03-USW2.ODA.SAS.COM'
 80          * Generated on SAS platform 'Linux LIN X64 3.10.0-1062.9.1.el7.x86_64'
 81          * Generated on SAS version '9.04.01M6P11072018'
 82          * Generated on browser 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko)
 82       ! Chrome/84.0.4147.105 Safari/537.36'
 83          * Generated on web client
 83       ! 'https://odamid-usw2.oda.sas.com/SASStudio/main?locale=en_US&zone=GMT-07%253A00&ticket=ST-27624-sinmcsizLgE19kH9QBkl-cas'
 84          *
 85          */
 86         
 87         proc freq data=WORK.SYPHILIS;
 88         tables genderB genderC sex_o RACE age / plots=(freqplot cumfreqplot);
 89         where Type in ("genderB", "genderC", "sex_o", "race") and 18<=age<=50;
 ERROR: Variable Type is not on file WORK.SYPHILIS.

SAS DAte conversion to numeric

jorquec — Mon, 10 Aug 2020 15:51:42 GMT

Hi all,

I am struggling in some date conversion.

Is there a way of conversion for this subtraction as Tenure_length_months results in a numeric number in the same format as Teradata output. Despite this code works on SAS, the final result for column Tenure_lenght_month does not manky any sense on my model with SAS results.

When I run on Teradata column Tenure_length_months give me numbers like 125,31,48 which is absolutely fine however SAS gives me results like 6278800, 6252333 that could be right on a SAS approach but is not what I would like to see as an output for this column.

Example:

Considering today as 2020-04-31 I would have a customer that is with us in 10 months

Teradata results

ten_date

Start_Month_End

tenure_mth

Tenure_length_months

Tenure_Months

02/07/2019

31/07/2019

201,907.00

10.98

Considering today as 2020-04-31 I would have a customer that is with us the same 10 months but SAs calculate in another way so gives me results like 627880.

SAS results

ten_date

Start_Month_End

tenure_mth

Tenure_length_months

Tenure_Months

02JUL2019 31JUL2019 201907 627880.40 627880

How I should write to see the same results as Teradata please?

proc delete
   lib= smm  data=payg_base_1;
run;

proc sql;                                                        
connect to teradata                                                     
(user=&td_usr. password=&td_pass. server = 'edwprod' database = 'insights_consumer' mode = teradata);                                                         
EXECUTE (
                                                          
CREATE SET TABLE sasmod_manager.payg_base_1 AS                                                       
(                                                         

select  a.*,

bb.Effective_From_Dt as ten_date ,
ADD_MONTHS(ten_date - EXTRACT(DAY FROM ten_date) + 1, 1) - 1 AS Start_Month_End,
cast(trim(extract (year from  ten_date ))  || trim(extract (month from  ten_date  ) (format '99')) as float) as tenure_mth,
((  '2020-04-31' - ten_date)/ 30.42) AS Tenure_length_months,

Cast(( Tenure_length_months ) AS INT)  AS Tenure_Months

from

(  select       subscr_id,  
  subscr_num,
Tariff_Offering_Id,    
 Device_Type_Id   ,
sales_channel_id

/*from NUC_PL_USER_VIEW.SUBSCR_TRACK WHERE DATE    between effective_from_dt  and  effective_to_dt */
from NUC_PL_USER_VIEW.SUBSCR_TRACK WHERE 1200431  between effective_from_dt  and  effective_to_dt 
AND PREPYD_IND = 'Y'  
AND pandl_segment_id = 1 
AND mobile_broadband_ind = 'N' 
AND TELEMATIC_IND='N' 
AND (  Internal_BASE_IND=1 ) 
 )  a  

         left join
( select     subscr_id,    Effective_From_Dt    from     NUC_PL_USER_VIEW.SUBSCR_TRACK 
   WHERE    
   PREPYD_IND = 'Y'    AND pandl_segment_id = 1   AND mobile_broadband_ind = 'N'   AND TELEMATIC_IND='N'  AND Internal_BASE_IND=1    /* START DATE*/
  qualify rank () over (  partition by  subscr_id    order by  Effective_From_Dt asc )  =1     )  bb
   on a.Subscr_id=bb.Subscr_id 
 

) WITH DATA PRIMARY INDEX(subscr_id);)BY TERADATA;                      
quit;

Re: how do repeat the ID for every patient 11 times

Angel_Larrion — Mon, 10 Aug 2020 14:51:44 GMT

The following code should work, it repeats the last observation of each id until there is 11 observations per id.

data want;
set have;
by id;
retain i 1;

if first.id then do;
    i=1;
    i=i+1;
    output;
end;

else if last.id=0 and first.id=0 then do;
    i=i+1;
    output;
end;


else if last.id then do;
    do until (i=12);
        i=i+1;
        output;

        status=0;
    end;
end;
 
drop i;
run;

Re: how do repeat the ID for every patient 11 times

Shmuel — Mon, 10 Aug 2020 14:36:13 GMT

Looking at your table posted each observation have a unique KEY made of

ID T1 and T2.

What values should T1, T2 have in next added observations ?

Steps to result will be:

1) select distinct values of ID taken from current dataset

2) replicate IDs 11 times including T1 T2 values creating a skeleton dataset

3) merging the skeleton with the current dataset by ID T1 T2

Re: how do repeat the ID for every patient 11 times

sasgyro — Mon, 10 Aug 2020 13:59:24 GMT

Yes,

i need every instance repeated 11 times because I want the data to reflect the patient at different time intervals. the intervals for the experiment are the same for each patient and we took their vitals at each instance so there are other variables. however some patients died during before the full time length of experiment so there is no data for times above when they died. I still want to include them to 11 times for continuity and mark them as Status=0 for dead at this time interval. Im trying to put the data in a counting style.

The data wu

ID. T1T2StatusTrtNumberSizeZ

1	0	3	1	1	1	3	12.3
1	3	10	1	1	1	3	14.7
1	10	15	1	1	1	3	13.8
1	15	23	0	1	1	3	15.5

2	0	3	1	1	1	5	12.3
2	3	10	1	1	1	3	14.7
2	10	15	0	1	1	3	13.8
2	15	23	0	1	1	3	15.5

Re: how do repeat the ID for every patient 11 times

Shmuel — Mon, 10 Aug 2020 04:04:13 GMT

What other variables are in your dataset? Should they be missing or with any initial value?

Please post an sample of your dataset.

Why do you want the IDs to be in 11 observations ? what is the logic or needs?

One way to do it is to select distinct IDs, replicate them to have 11 times each and then

remerge them with your dataset by ID and maybe some other variable (like a date).

how do repeat the ID for every patient 11 times

sasgyro — Mon, 10 Aug 2020 01:32:29 GMT

how do repeat the ID for every patient so that they have 11 instances they appear in the dataset. Some patients appear 3 4 7 or 11 times but I want everyone to be featured 11 times.

Re: Struggling with Missingness in a data set

Rick_SAS — Sun, 09 Aug 2020 11:37:46 GMT

The SAS documentation has an example of how to compute FIML by using structural equation modeling with PROC CALIS.

Re: Struggling with Missingness in a data set

Ksharp — Sun, 09 Aug 2020 11:25:28 GMT

Do you want impute missing value by EM algorithm ?

wrote a blog about it recently .

Re: Struggling with Missingness in a data set

PaigeMiller — Sun, 09 Aug 2020 11:05:48 GMT

Some people will fill in the mean of the data in place of the missings and also create a new variable which is 0 if the original variable was not missing and 1 if the original variable was missing. Then you put the original variable and the new variable into the model. This essentially predicts the observations with the original variable missing at a constant offset from the observations when the original variable was not missing.

Re: Struggling with Missingness in a data set

Norman21 — Sun, 09 Aug 2020 08:25:20 GMT

From what you describe, the people are not "missing" the question, they are deliberately choosing not to answer it. This is information that might be useful for your model.

You can try recoding this variable to "not answered" (or whatever) then run the logistic regression.

Re: several questions: options control, format control, ods procedure tables output data sets

Tom — Sun, 09 Aug 2020 03:43:23 GMT

If you want to write a text file use the PUT statement. If you want to use a "FORTRAN like format list" then () in around the variable names and separate () around the formats.

data _null_;
  set HAVE ;
  file 'myfile';
  put (varlist) (fmtlist);
run;

To write a delimited file use the DSD option. No need to for formats so just list the variables.

data _null_;
  set HAVE ;
  file 'myfile' dsd ;
  put varlist ;
run;

If you want to list all of them you can use the _ALL_ keyword, but then you need to use the () or else it writes name=value instead and includes automatic variables like _N_. No need to list formats, but you need to put something in the format list so use a pointer control like +0 or a modifier like : .

  put (_all_) (+0);

Re: several questions: options control, format control, ods procedure tables output data sets

Tom — Sun, 09 Aug 2020 03:37:12 GMT

Are you looking for the CENTER/NOCENTER option?

Just include it in your autoexec.

options nocenter;

Struggling with Missingness in a data set

klongway — Sun, 09 Aug 2020 02:16:50 GMT

Hello,

I am running a logistic regression with four predictor variables, 1 outcome variable, and 6 covariates. My N is around 2000 participants.

For one of my four predictor variables, there are around 1000 people missing the question. The question asked was very sensitive and it is normal for people to skip it on surveys per other papers. The situation is similar for one of my covariates, where a question on a sensitive topic is also skipped by a substantial number of people.

Right now when I run it, my data set ends up cut in half. My major professor will not let me do multiple imputations and wants me to do Full Information Maximum Likelihood to account for the missing data.

Does anyone have any advice on if I can do this in SAS?

Thank you!

Re: several questions: options control, format control, ods procedure tables output data sets

SASKiwi — Sun, 09 Aug 2020 01:24:20 GMT

With question 1 try this SAS option: options nocenter;

Re: several questions: options control, format control, ods procedure tables output data sets

Reeza — Sun, 09 Aug 2020 02:10:37 GMT

This blog post will help answer Questions 3/4

https://blogs.sas.com/content/iml/2017/01/09/ods-output-any-statistic.html

Q2:

I usually recommend using PROC EXPORT to get the structure of code needed - printed to the log and then customize as needed.

https://documentation.sas.com/?docsetId=proc&docsetTarget=n0jcjrzsseiw2qn1gi12k645u75y.htm&docsetVersion=9.4&locale=en

Q3:

The code is slightly backwards, you reversed the table name and the name of the output data set. It should be:

*incorrect;
ods output bprawfreqs=OneWayFreq;

*correct;
ods output OneWayFreq = bprawfreqs;

No idea what you mean with Q1.

FYI - its likely significantly easier to answer your questions if you take some time to format them and to post them separately unless they're related like 3/4.

wrote:

this is a stored-up list.

1) Somewhere, i've seen that it is possible get rid of that centered output and have left justified output in the results viewer window. What was showed was the specific command that went in the syntax file. Stumbling around, i found a directory or file called options. I'm looking for a permanent fix. Do modify the options file? What option name and how done?

2) Today, i wanted to write out a text data file. In spss i'd say

write outfile='path string' var list (optional Fortran-type format specification). Nice and simple and highly controllable. I see in Cody's book how to export an excel file. Mplus, the receiving program, takes only text files. In SAS, how would i write out a text data file and, if desired, control variable formats and new lines. For example: recid y1-y50 (f4.0,2x,25f3.0/6x,25f3.0).

3) I want to export a set of frequency tables to a dataset. Based on Cody's book I used this

52 ods output bprawfreqs=OneWayFreq;
53 proc freq data=pbitems; tables dpb4-dpb16; run;

WARNING: Output 'bprawfreqs' was not created. Make sure that the output object name, label, or path is spelled correctly. Also, verify that the appropriate procedure options
are used to produce the requested output object. For example, verify that the
NOPRINT option is not used.

So. i believe the object name is correct because i did and ODS Trace command. I assume that the file (bprawfreqs is just a sas data set and it's location is controlled by the active lib statement (Correct or not?)

I read the documentation for proc freq and see that there is an "out' subcommand for a table statement. However, as i understand the documentation what is written out to the named dataset is only the last named frequency/crosstab table in the table subcommand. That's useless and it's hard to believe that is true.

4) I want to come back to the output export problem. Recently i was running GEE models Working through the iterations of IV variable combinations, i had a list of 26 or 27 and I had to run each combination with two different DVs. The PIs requested that i summarize the results and what they wanted to see the coefficients and their significance values. (I want to say something to head off Proc Report: The coefficients and their significance are looked at and discussed, decisions are made, and the syntax and mht files could be deleted because they served their function). In spss i could say OMS "analysis type" select if table="coefficients" ahead of the first GEE model and OMS End after the last one. In Cody i read that i can specify ods select >object< (persist); and that will do what i want. True?

That does it for now. Thanks.

several questions: options control, format control, ods procedure tables output data sets

emaguin — Sat, 08 Aug 2020 20:15:20 GMT

this is a stored-up list.

1) Somewhere, i've seen that it is possible get rid of that centered output and have left justified output in the results viewer window. What was showed was the specific command that went in the syntax file. Stumbling around, i found a directory or file called options. I'm looking for a permanent fix. Do modify the options file? What option name and how done?

2) Today, i wanted to write out a text data file. In spss i'd say

write outfile='path string' var list (optional Fortran-type format specification). Nice and simple and highly controllable. I see in Cody's book how to export an excel file. Mplus, the receiving program, takes only text files. In SAS, how would i write out a text data file and, if desired, control variable formats and new lines. For example: recid y1-y50 (f4.0,2x,25f3.0/6x,25f3.0).

3) I want to export a set of frequency tables to a dataset. Based on Cody's book I used this

52 ods output bprawfreqs=OneWayFreq;
53 proc freq data=pbitems; tables dpb4-dpb16; run;

WARNING: Output 'bprawfreqs' was not created. Make sure that the output object name, label, or path is spelled correctly. Also, verify that the appropriate procedure options
are used to produce the requested output object. For example, verify that the
NOPRINT option is not used.

So. i believe the object name is correct because i did and ODS Trace command. I assume that the file (bprawfreqs is just a sas data set and it's location is controlled by the active lib statement (Correct or not?)

I read the documentation for proc freq and see that there is an "out' subcommand for a table statement. However, as i understand the documentation what is written out to the named dataset is only the last named frequency/crosstab table in the table subcommand. That's useless and it's hard to believe that is true.

4) I want to come back to the output export problem. Recently i was running GEE models Working through the iterations of IV variable combinations, i had a list of 26 or 27 and I had to run each combination with two different DVs. The PIs requested that i summarize the results and what they wanted to see the coefficients and their significance values. (I want to say something to head off Proc Report: The coefficients and their significance are looked at and discussed, decisions are made, and the syntax and mht files could be deleted because they served their function). In spss i could say OMS "analysis type" select if table="coefficients" ahead of the first GEE model and OMS End after the last one. In Cody i read that i can specify ods select >object< (persist); and that will do what i want. True?

That does it for now. Thanks.

Re: Creating a frequency table using age

PaigeMiller — Sat, 08 Aug 2020 19:54:33 GMT

I think this will work

where  Type in ("genderC", "genderB", "sex_o") and 18<=age<=50

This assumes age is numeric

Creating a frequency table using age

Kimberly_2020 — Sat, 08 Aug 2020 18:57:06 GMT

Hello there,

I am trying to create a frequency table for gender and sexual orientation between the ages of 18-50. Where am I going wrong.

Code:
proc freq data=WORK.SYPHILIS;
	tables genderC genderB sex_o age RACE / plots=(freqplot cumfreqplot);
	where  Type in ("genderC", "genderB", "sex_o", age "18-50");
run;

Log:

87         proc freq data=WORK.SYPHILIS;
 88         tables genderC genderB sex_o age RACE / plots=(freqplot cumfreqplot);
 89         where  Type in ("genderC", "genderB", "sex_o", age "18-50");
                                                            ___
                                                            22
                                                            202
 ERROR: Syntax error while parsing WHERE clause.
 ERROR 22-322: Syntax error, expecting one of the following: a quoted string, ).  
 ERROR 202-322: The option or parameter is not recognized and will be ignored.
 90         run;

Re: Skipping cycles based on dates contained in another dataset

MMariani — Fri, 07 Aug 2020 16:23:49 GMT

Sorry for the late answer but I was caught up at work.
The code eventually worked, there were just some changes needed to optimize it that my team leader showed me after being able to reach me.
So thanks a lot for the advice!

Re: proc sql

Naveen1111 — Fri, 07 Aug 2020 13:34:22 GMT

Many many thanks for ur support. I m sorry as i m a new learner and will keep posting these qstions.

Re: how to chain datasets with same name and variables structure

Ksharp — Fri, 07 Aug 2020 11:54:20 GMT

data vzk_2020;
set vzk_2020_1 - vzk_2020_8 ;
run;

OR Just:
data vzk_2020;
set vzk_2020_: ;
run;

Re: proc sql

KurtBremser — Fri, 07 Aug 2020 10:44:59 GMT

proc sql;
insert into a
(select * from b where /* add condition that selects the two rows */)
;
quit;

For more detailed help, supply example data for both datasets in usable form (data steps with datalines).

Re: how to chain datasets with same name and variables structure

PierreYvesILY — Fri, 07 Aug 2020 10:43:22 GMT

thank you Kurt, have a nice day!

Re: how to chain datasets with same name and variables structure

KurtBremser — Fri, 07 Aug 2020 10:38:31 GMT

This is where you need a macro. You need one SET statement, but multiple datasets in it.

%macro dsnames;
%do i = 1 %to 8;
  vzk_2020_&i.
%end;
%mend;

data vzk_2020;
set
  %dsnames
;
run;

Take note where I placed semicolons, and where I omitted them.

how to chain datasets with same name and variables structure

PierreYvesILY — Fri, 07 Aug 2020 10:33:25 GMT

Hello SAS experts,

I have a list of datasets with the same name and variables structure, and I want to add them all in a single one.

this doesn't work:

data vzk_2020;

do i=1 to 8;

set vzk_2020_i;

end;

run;

what's the correct way?

regards,

Re: proc sql like operator

Naveen1111 — Fri, 07 Aug 2020 10:30:18 GMT

thanks.

Re: Creating three new variables in a panel ?

andreas_lds — Fri, 07 Aug 2020 10:28:38 GMT

wrote:

3. I have several variables which are in percentage (they have been calculated using avg() format=percent7.2 ). I need to convert these to numbers. so for example 91.70% should be converted to 0.917.

Thanks so much in advance for your help.

once more: a format only changes how a variable is displayed, not the value of the variable.So removing the format from the variable should solve that issue.

proc sql to copy records from one table to another

Naveen1111 — Sat, 08 Aug 2020 13:07:21 GMT

Hi All,

i have one question. There are two datasets A and B, want to move/copy two rows from table B to A. Could someone help me which syntax I should use IN proc SQL.

Regards

Navin

Re: How do I plot individual variables over time

Reeza — Thu, 06 Aug 2020 19:45:30 GMT

And it's likely easier if you add the LCLM and UCLM options to the PROC MEANS to get the lower and upper confidence limits of the mean if that's what you prefer.

Re: How do I plot individual variables over time

Reeza — Thu, 06 Aug 2020 19:43:25 GMT

This is definitely possible, take a look at the VBARPARM documentation within SGPLOT and see what options it offers to add them on.
Hint: LIMITLOWER/LIMITUPPER

https://go.documentation.sas.com/?docsetId=grstatproc&docsetTarget=n0mc5dtithid5mn13c54dlgaceq3.htm&docsetVersion=9.4&locale=en

Re: How do I plot individual variables over time

cdunlea — Thu, 06 Aug 2020 19:31:57 GMT

Thank you Reeza!! It worked! Is there a way I can also add standard deviation to the graph as well?

Re: How do I plot individual variables over time

Reeza — Thu, 06 Aug 2020 19:25:40 GMT

When you post code please use a code block so that your code is formatted and legible.

proc means data=wide_merged_file_sans_pooled mean stddev median min max;
var gmcsf_fuvisit_f0 gmcsf_fuvisit_f1 gmcsf_fuvisit_f2 gmcsf_fuvisit_f3 gmcsf_fuvisit_f5
gmcsf_fuvisit_f6 gmcsf_fuvisit_f7 gmcsf_fuvisit_f8; 
run;

1. Save output from PROC MEANS to a data set

2. Graph data from data set

#1 is to add an ODS OUTPUT statement to capture the output, there are multiple ways to do this but this provides the data in a nice format for graphing. You do need to add the STACKODS option on the PROC MEANS statement as well.

proc means data=wide_merged_file_sans_pooled mean stddev median min max STACKODS;
var gmcsf_fuvisit_f0 gmcsf_fuvisit_f1 gmcsf_fuvisit_f2 gmcsf_fuvisit_f3 gmcsf_fuvisit_f5
gmcsf_fuvisit_f6 gmcsf_fuvisit_f7 gmcsf_fuvisit_f8; 
ods output summary = summaryStats;
run;

#2 Graph it

proc sgplot data=summaryStats;
vbarparm category = variable response=mean;
run;

wrote:

Hello All, I am attempting to plot the means of 8 individual variables in my dataset over time. I am using SAS university so proc gplot is not an option.

What I want is a way to take my proc means and plot it. So far nothing has worked. Here is the proc means I am running

proc means data=wide_merged_file_sans_pooled mean stddev median min max;
var gmcsf_fuvisit_f0 gmcsf_fuvisit_f1 gmcsf_fuvisit_f2 gmcsf_fuvisit_f3 gmcsf_fuvisit_f5
gmcsf_fuvisit_f6 gmcsf_fuvisit_f7 gmcsf_fuvisit_f8; run;

I want to take the results of this proc means and plot it with an x-axis of "fuvisit"(each variable is a follow up visit) and a y axis of "Mean" along with standard deviation.

Any advice is appreciated.

Re: Remove decimal from variable

Reeza — Thu, 06 Aug 2020 19:19:49 GMT

Is it character or numeric variable?

How do I plot individual variables over time

cdunlea — Thu, 06 Aug 2020 19:19:47 GMT

Hello All, I am attempting to plot the means of 8 individual variables in my dataset over time. I am using SAS university so proc gplot is not an option.

What I want is a way to take my proc means and plot it. So far nothing has worked. Here is the proc means I am running

proc means data=wide_merged_file_sans_pooled mean stddev median min max;
var gmcsf_fuvisit_f0 gmcsf_fuvisit_f1 gmcsf_fuvisit_f2 gmcsf_fuvisit_f3 gmcsf_fuvisit_f5
gmcsf_fuvisit_f6 gmcsf_fuvisit_f7 gmcsf_fuvisit_f8; run;

I want to take the results of this proc means and plot it with an x-axis of "fuvisit"(each variable is a follow up visit) and a y axis of "Mean" along with standard deviation.

Any advice is appreciated.

Re: Saving files in SAS University Edition

Reeza — Thu, 06 Aug 2020 19:12:02 GMT

Set up a libname to where you want the files stored and move the files there. You can use PROC COPY or PROC DATASETS to move them over efficiently.

libname myFiles '/folders/myfolders/Proj1234/data/';

proc copy in=work out=myFiles;
run;

Saving files in SAS University Edition

Tim_sas_ — Thu, 06 Aug 2020 19:09:44 GMT

Hello,

I know it is a very basic question but my search did not yield satisfactory results so far.

I want to save data files permanently from my work library. Do I have to export them into myfolders or is there a more convenient way to do this in SAS University edition?

Many thanks for any help!

Tim

Re: Remove decimal from variable

novinosrin — Thu, 06 Aug 2020 18:20:58 GMT

compress(var,'.') should work?

Remove decimal from variable

marleeakerson — Thu, 06 Aug 2020 18:17:00 GMT

Hello,

How do i remove a decimal from a variable?

For example - go from:

3.4

66.5

z4.1

to:

665

z41

Is this possible using the cat or catx function?

Re: Creating three new variables in a panel ?

KurtBremser — Thu, 06 Aug 2020 18:14:02 GMT

Sort by brand, year and week.

Then run a data step:

data want;
set have;
by brand;
retain id count 0;
if first.brand
then do;
  id + 1;
  count = 1;
end;
else count + 1;
run;

To display the percent value in its raw form, just change the format to a "normal" one like 8.3.

Creating three new variables in a panel ?

AntonioFinn — Thu, 06 Aug 2020 17:52:36 GMT

I have a panel dataset which includes weekly data for several brands across four years (250 observations per brand). I appreciate if you help me with doing the following three things (I apologize in advance if I shouldn't ask multiple questions under one topic). Also sorry I cannot share a sample of my data due to NDA.

1. My dataset includes a column named "brand_name". I want to create a new column ("id") which uniquely identifies each brand. So it should take on the same value for all the 250 rows associated with each brand.

2. I need a new variable which assigns a number (from 1 to 250) to each observation for each brand. My dataset includes two columns "Year0" and "week". For each brand, my data starts from the 6th week of 2014 up until 52nd week of 2014. Then, from week 0 of 2015 to week 52 of 2015, and so on. In other words, when "Year0" is 2014, "week" starts from 6 all the way to 52. Then for the next row, in which "Year0" is 2015, "week" is 0 (so the variable week starts over with a change in Year0). The new variable should assign 1 whenever Year0 is 2014 and week is 6, and continue this until the last observation, for which it should be 250.

3. I have several variables which are in percentage (they have been calculated using avg() format=percent7.2 ). I need to convert these to numbers. so for example 91.70% should be converted to 0.917.

Thanks so much in advance for your help.

Re: Extract first and last name from character variable

Shmuel — Thu, 06 Aug 2020 07:31:38 GMT

Sorry, it seems that I had some misunderstanding;

try next code:

data have; 
 length note $200.;
 input note $ ;
 note = tranwrd ( note, "_", " " );
cards;
This_is_the_Requestor:_Mary_L._Santiago_Reason:
Additional_text_This_is_the_Requestor:_John_Doe_Reason:_stuff
This_is_the_Requestor:_Tyler_Nguyen_Reason:_text_text
;
run;

data want;
 set have;
     pos1 = findw(note,"Requestor:");
     pos2 = findw(note,"Reason:");
     fullname = strip(substr(note,pos1+10,pos2-pos1-10));
     drop pos1 pos2;
run;

Re: Extract first and last name from character variable

KurtBremser — Thu, 06 Aug 2020 06:53:05 GMT

Try this:

data want;
set have;
length name $30;
note = scan(note,2,':');
call scan(note,-1,pos,le,'_','m');
name = translate(substr(note,2,pos - 2),' ','_');
keep name;
run;

Re: Extract first and last name from character variable

andreas_lds — Thu, 06 Aug 2020 05:26:33 GMT

As soon as personal names are involved, sooner or later things will get interesting. Without a proper delimiter between first-name and last-name this problem can't be solved, because the number of words forming first-name and last-name is rarely two (one word for each), starting the interesting part: from the second to the next-to-last word you have to decide, whether the word belongs to first-name or last-name. This is pure guesswork and will not lead to usable results.

The following step extracts the names and stores in in one variable:

data want;
   set have;
   
   length FullName $ 40 rxName 8;
   retain rxName;
   drop rxName;
   
   if _n_ = 1 then do;
      rxName = prxparse('/requestor:_(.+)_reason/i');
   end;
   
   if prxmatch(rxName, note) then do;
      FullName = prxposn(rxName, 1, note);
      FullName = translate(FullName, ' ', '_');
   end;
run;

Re: Extract first and last name from character variable

Shmuel — Thu, 06 Aug 2020 04:35:33 GMT

The delimiter between the two names id ":" then:

first_name = scan(note,1,":");
second_name = scan(note,2,":");

Extract first and last name from character variable

bkq32 — Thu, 06 Aug 2020 01:51:29 GMT

I have a variable that has a first name and last name embedded in it. How can I extract the name into a new variable, assuming it always comes after "Requestor: " and before "Reason:"?

data have; 
 length note $200.;
 input note $ ;
cards;
This_is_the_Requestor:_Mary_L._Santiago_Reason:
Additional_text_This_is_the_Requestor:_John_Doe_Reason:_stuff
This_is_the_Requestor:_Tyler_Nguyen_Reason:_text_text
;
run;

data have;
 set have;
 note = tranwrd ( note, "_", " " );
run;

Re: How do I import a CSV file into the SAS library

Shmuel — Wed, 05 Aug 2020 20:35:53 GMT

1) If the AGE is a group given as "18-50" then use

where age = "18-50";

If AGE is a number like 25 then you can use

where age between 18 and 50;

2) The title of your post is "How do I import a CSV file into the SAS library".

You got the solution to your question.

The new post dealing how to subset your date according to age group

should be posted as a new query.

Re: How do I import a CSV file into the SAS library

Kimberly_2020 — Wed, 05 Aug 2020 20:33:52 GMT

Attached is my data. Again, my where statement was:

where age between 18 and 50

Re: How do I import a CSV file into the SAS library

Reeza — Wed, 05 Aug 2020 20:17:19 GMT

We don't have your data so can only guess at what you're asking...if you need specific help you need to provide sample data.

Re: How do I import a CSV file into the SAS library

Kimberly_2020 — Wed, 05 Aug 2020 20:00:01 GMT

It is a group age...(Age of people between the age of 18 and 50)

I got a frequency table from age 18-50....but I didn't use the word "is"..Does it matter

proc freq data=WORK.SYPHILIS;
	tables age sex_o genderC genderB RACE / plots=(freqplot cumfreqplot);
	where age between 18 and 50;
run;

Re: How do I import a CSV file into the SAS library

Shmuel — Wed, 05 Aug 2020 19:52:44 GMT

Your variable is named age. What kind of values does it contain?

The WHERE statement may be either

where age is between 18 and 50

where age is "18 to 50"

depending on age variable - is it an age of a person or

is it a group age/

Re: How do I import a CSV file into the SAS library

Kimberly_2020 — Wed, 05 Aug 2020 19:48:34 GMT

I figured it out..I did where age between 19 and 50;

Re: How do I import a CSV file into the SAS library

Kimberly_2020 — Wed, 05 Aug 2020 19:42:53 GMT

This is what it says:

proc freq data=WORK.SYPHILIS;
	tables age sex_o genderC genderB / plots=(freqplot cumfreqplot);
	where age_group= '18 to 50';
run;

Log: 

 1          OPTIONS NONOTES NOSTIMER NOSOURCE NOSYNTAXCHECK;
 72         
 73         /*
 74          *
 75          * Task code generated by SAS Studio 3.8
 76          *
 77          * Generated on '8/5/20, 12:06 PM'
 78          * Generated by 'u49152646'
 79          * Generated on server 'ODAWS02-USW2.ODA.SAS.COM'
 80          * Generated on SAS platform 'Linux LIN X64 3.10.0-1062.9.1.el7.x86_64'
 81          * Generated on SAS version '9.04.01M6P11072018'
 82          * Generated on browser 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko)
 82       ! Chrome/84.0.4147.105 Safari/537.36'
 83          * Generated on web client
 83       ! 'https://odamid-usw2.oda.sas.com/SASStudio/main?locale=en_US&zone=GMT-07%253A00&ticket=ST-58631-NKEgz3Gaqesii60Jleii-cas'
 84          *
 85          */
 86         
 87         proc freq data=WORK.SYPHILIS;
 88         tables age sex_o genderC genderB / plots=(freqplot cumfreqplot);
 89         where age_group= '18 to 50';
 ERROR: Variable age_group is not on file WORK.SYPHILIS.
 90         run;
 
 NOTE: The SAS System stopped processing this step because of errors.
 NOTE: PROCEDURE FREQ used (Total process time):
       real time           0.00 seconds
       user cpu time       0.00 seconds
       system cpu time     0.00 seconds
       memory              1375.50k
       OS Memory           38572.00k
       Timestamp           08/05/2020 07:33:34 PM
       Step Count                        265  Switch Count  0
       Page Faults                       0
       Page Reclaims                     242
       Page Swaps                        0
       Voluntary Context Switches        0
       Involuntary Context Switches      0
       Block Input Operations            0
       Block Output Operations           0
       
 91         
 92         OPTIONS NONOTES NOSTIMER NOSOURCE NOSYNTAXCHECK;
 104

Re: How do I import a CSV file into the SAS library

Kimberly_2020 — Wed, 05 Aug 2020 19:36:37 GMT

It says that the age_group is not on the work.syphilis file. Where did I go wrong?

Re: How do I import a CSV file into the SAS library

Kimberly_2020 — Wed, 05 Aug 2020 19:35:53 GMT

proc freq data=WORK.SYPHILIS;
	tables age sex_o genderC genderB / plots=(freqplot cumfreqplot);
	where age_group= '18 to 50';
run;

Log: 

1          OPTIONS NONOTES NOSTIMER NOSOURCE NOSYNTAXCHECK;
 72         
 73         /*
 74          *
 75          * Task code generated by SAS Studio 3.8
 76          *
 77          * Generated on '8/5/20, 12:06 PM'
 78          * Generated by 'u49152646'
 79          * Generated on server 'ODAWS02-USW2.ODA.SAS.COM'
 80          * Generated on SAS platform 'Linux LIN X64 3.10.0-1062.9.1.el7.x86_64'
 81          * Generated on SAS version '9.04.01M6P11072018'
 82          * Generated on browser 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko)
 82       ! Chrome/84.0.4147.105 Safari/537.36'
 83          * Generated on web client
 83       ! 'https://odamid-usw2.oda.sas.com/SASStudio/main?locale=en_US&zone=GMT-07%253A00&ticket=ST-58631-NKEgz3Gaqesii60Jleii-cas'
 84          *
 85          */
 86         
 87         proc freq data=WORK.SYPHILIS;
 88         tables age sex_o genderC genderB / plots=(freqplot cumfreqplot);
 89         where age_group= '18 to 50';
 ERROR: Variable age_group is not on file WORK.SYPHILIS.
 90         run;
 
 NOTE: The SAS System stopped processing this step because of errors.
 NOTE: PROCEDURE FREQ used (Total process time):
       real time           0.00 seconds
       user cpu time       0.00 seconds
       system cpu time     0.00 seconds
       memory              1375.50k
       OS Memory           38572.00k
       Timestamp           08/05/2020 07:33:34 PM
       Step Count                        265  Switch Count  0
       Page Faults                       0
       Page Reclaims                     242
       Page Swaps                        0
       Voluntary Context Switches        0
       Involuntary Context Switches      0
       Block Input Operations            0
       Block Output Operations           0
       
 91         
 92         OPTIONS NONOTES NOSTIMER NOSOURCE NOSYNTAXCHECK;
 104

Re: How do I import a CSV file into the SAS library

Reeza — Wed, 05 Aug 2020 19:27:10 GMT

You add a WHERE statement to filter out/in the groups you want.

WHERE age_group = '18 to 50';

Re: How do I import a CSV file into the SAS library

Kimberly_2020 — Wed, 05 Aug 2020 19:03:29 GMT

Thanks

Re: How do I import a CSV file into the SAS library

Kimberly_2020 — Wed, 05 Aug 2020 19:01:11 GMT

I have it now. I need a frequency table for an age group (18-50) along with gender

proc freq data=WORK.SYPHILIS;
	tables genderC genderB age / plots=(freqplot cumfreqplot);
run;

How do I write the code for an age group of 18-50

Re: How do I import a CSV file into the SAS library

Reeza — Wed, 05 Aug 2020 19:00:50 GMT

https://video.sas.com/detail/video/4664358166001/using-the-import-data-utility-in-sas-studio

Re: How do I import a CSV file into the SAS library

Shmuel — Wed, 05 Aug 2020 18:52:31 GMT

You can use either proc import:

proc import file="Path_and_FileName.csv"
            out=test dbms=csv 
            replace;
     getnames=yes;  /* assume first line contains variable names */
run;

Try it and if any issue post the full log showing your code and messages.

Depending on data types you may have issues especially getting the wrong type.

If possible post also a sample lines from the csv file.

Re: How do I import a CSV file into the SAS library

Reeza — Wed, 05 Aug 2020 18:51:04 GMT

Yes it's possible. Use an Import Data task is likely your best bet if you're unfamiliar with SAS.
Or use PROC IMPORT. That creates a SAS data set that can then be worked with in SAS.

Re: How do I import a CSV file into the SAS library

Kimberly_2020 — Wed, 05 Aug 2020 18:03:09 GMT

My end goal is to create a frequency table..it lets me enter the source of the data but the data set is not showing up in the library

How do I import a CSV file into the SAS library

Kimberly_2020 — Wed, 05 Aug 2020 18:00:57 GMT

How do I import a csv file into the library or is it possible?

Re: Physical file does not exist

Kimberly_2020 — Wed, 05 Aug 2020 17:17:37 GMT

I finally got it!! Thank you for all your help!

Re: Physical file does not exist

Kimberly_2020 — Wed, 05 Aug 2020 16:55:41 GMT

Got it...Now I have an output but it is empty...I tried coding a different way from the tutorial videos that you sent me...

data sample;
	infile '/home/u49152646/EPG194/rapid_syphilis/sample.csv' dlm=',' firstobs=2;
	input rapid_syphilis race gendec genderb sex_o housing_status sessiondate age druguse condom risk;
run;

Log was pretty long but it says invalid data and gain my output data was empty:

 
 1          OPTIONS NONOTES NOSTIMER NOSOURCE NOSYNTAXCHECK;
 SYMBOLGEN:  Macro variable _SASWSTEMP_ resolves to /home/u49152646/.sasstudio/.images/52784700-4b6e-40f6-aa6a-258160043ad9
 SYMBOLGEN:  Some characters in the above value which were subject to macro quoting have been unquoted for printing.
 SYMBOLGEN:  Macro variable GRAPHINIT resolves to GOPTIONS RESET=ALL GSFNAME=_GSFNAME;
 72         
 73         data sample;
 74         infile '/home/u49152646/EPG194/rapid_syphilis/sample.csv' dlm=',' firstobs=2;
 75         input rapid_syphilis race gendec genderb sex_o housing_status sessiondate age druguse condom risk;
 76         run;
 
 NOTE: The infile '/home/u49152646/EPG194/rapid_syphilis/sample.csv' is:
       Filename=/home/u49152646/EPG194/rapid_syphilis/sample.csv,
       Owner Name=u49152646,Group Name=oda,
       Access Permission=-rw-r--r--,
       Last Modified=04Aug2020:10:54:25,
       File Size (bytes)=826571
 
 NOTE: Invalid data for rapid_syphilis in line 2 1-8.
 NOTE: Invalid data for race in line 2 10-14.
 NOTE: Invalid data for gendec in line 2 16-19.
 NOTE: Invalid data for genderb in line 2 21-24.
 NOTE: Invalid data for sex_o in line 2 26-33.
 NOTE: Invalid data for housing_status in line 2 35-46.
 NOTE: Invalid data for sessiondate in line 2 48-65.
 NOTE: Invalid data for age in line 2 67-75.
 NOTE: Invalid data for condom in line 2 80-81.
 NOTE: Invalid data for risk in line 2 83-100.
 RULE:     ----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0                      
 2         Received,White,Male,Male,Bisexual,Not Homeless,West Hollywood MTU,27-Apr-18,50,No,Did not use condom
      101  ,High 105
 rapid_syphilis=. race=. gendec=. genderb=. sex_o=. housing_status=. sessiondate=. age=. druguse=50 condom=. risk=. _ERROR_=1 _N_=1
 NOTE: Invalid data for rapid_syphilis in line 3 1-8.
 NOTE: Invalid data for race in line 3 10-14.
 NOTE: Invalid data for gendec in line 3 16-19.
 NOTE: Invalid data for genderb in line 3 21-24.
 NOTE: Invalid data for sex_o in line 3 26-36.
 NOTE: Invalid data for housing_status in line 3 38-49.
 NOTE: Invalid data for sessiondate in line 3 51-68.
 NOTE: Invalid data for age in line 3 70-78.
 NOTE: Invalid data for condom in line 3 83-84.
 NOTE: Invalid data for risk in line 3 86-103.
 3         Received,White,Male,Male,Gay/Lesbian,Not Homeless,West Hollywood MTU,28-Apr-18,23,No,Did not use con
      101  dom,High 108
 rapid_syphilis=. race=. gendec=. genderb=. sex_o=. housing_status=. sessiondate=. age=. druguse=23 condom=. risk=. _ERROR_=1 _N_=2
 NOTE: Invalid data for rapid_syphilis in line 4 1-8.
 NOTE: Invalid data for race in line 4 10-14.
 NOTE: Invalid data for gendec in line 4 16-19.
 NOTE: Invalid data for genderb in line 4 21-24.
 NOTE: Invalid data for sex_o in line 4 26-33.
 NOTE: Invalid data for housing_status in line 4 35-42.
 NOTE: Invalid data for sessiondate in line 4 44-61.
 NOTE: Invalid data for age in line 4 63-71.
 NOTE: Invalid data for condom in line 4 76-77.
 NOTE: Invalid data for risk in line 4 79-96.
 4         Received,White,Male,Male,Bisexual,Homeless,West Hollywood MTU,28-Apr-18,49,No,Did not use condom,Hig
      101  h 101
 rapid_syphilis=. race=. gendec=. genderb=. sex_o=. housing_status=. sessiondate=. age=. druguse=49 condom=. risk=. _ERROR_=1 _N_=3
 NOTE: Invalid data for rapid_syphilis in line 5 1-12.
 NOTE: Invalid data for race in line 5 14-35.
 NOTE: Invalid data for gendec in line 5 37-40.
 NOTE: Invalid data for genderb in line 5 42-45.
 NOTE: Invalid data for sex_o in line 5 47-57.
 NOTE: Invalid data for housing_status in line 5 59-70.
 NOTE: Invalid data for sessiondate in line 5 72-89.
 NOTE: Invalid data for age in line 5 91-99.
 NOTE: Invalid data for condom in line 5 104-105.
 NOTE: Invalid data for risk in line 5 107-124.
 RULE:     ----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0                      
 5         Not Received,Black/African American,Male,Male,Gay/Lesbian,Not Homeless,West Hollywood MTU,28-Apr-18,
      101  52,No,Did not use condom,High 129
 rapid_syphilis=. race=. gendec=. genderb=. sex_o=. housing_status=. sessiondate=. age=. druguse=52 condom=. risk=. _ERROR_=1 _N_=4
 NOTE: Invalid data for rapid_syphilis in line 6 1-12.
 NOTE: Invalid data for race in line 6 14-18.
 NOTE: Invalid data for gendec in line 6 20-23.
 NOTE: Invalid data for genderb in line 6 25-28.
 NOTE: Invalid data for sex_o in line 6 30-40.
 NOTE: Invalid data for housing_status in line 6 42-53.
 NOTE: Invalid data for sessiondate in line 6 55-72.
 NOTE: Invalid data for age in line 6 74-82.
 NOTE: Invalid data for condom in line 6 87-88.
 NOTE: Invalid data for risk in line 6 90-103.
 6         Not Received,Asian,Male,Male,Gay/Lesbian,Not Homeless,West Hollywood MTU,28-Apr-18,26,No,Did use con
      101  dom,Low 107
 rapid_syphilis=. race=. gendec=. genderb=. sex_o=. housing_status=. sessiondate=. age=. druguse=26 condom=. risk=. _ERROR_=1 _N_=5
 NOTE: Invalid data for rapid_syphilis in line 7 1-12.
 NOTE: Invalid data for race in line 7 14-18.
 NOTE: Invalid data for gendec in line 7 20-23.
 NOTE: Invalid data for genderb in line 7 25-28.
 NOTE: Invalid data for sex_o in line 7 30-40.
 NOTE: Invalid data for housing_status in line 7 42-53.
 NOTE: Invalid data for sessiondate in line 7 55-72.
 NOTE: Invalid data for age in line 7 74-82.
 NOTE: Invalid data for condom in line 7 87-88.
 NOTE: Invalid data for risk in line 7 90-103.
 7         Not Received,White,Male,Male,Gay/Lesbian,Not Homeless,West Hollywood MTU,28-Apr-18,27,No,Did use con
      101  dom,Low 107
 rapid_syphilis=. race=. gendec=. genderb=. sex_o=. housing_status=. sessiondate=. age=. druguse=27 condom=. risk=. _ERROR_=1 _N_=6
 NOTE: Invalid data for rapid_syphilis in line 8 1-12.
 NOTE: Invalid data for race in line 8 14-35.
 NOTE: Invalid data for gendec in line 8 37-40.
 NOTE: Invalid data for genderb in line 8 42-45.
 NOTE: Invalid data for sex_o in line 8 47-58.
 NOTE: Invalid data for housing_status in line 8 60-71.
 NOTE: Invalid data for sessiondate in line 8 73-90.
 NOTE: Invalid data for age in line 8 92-100.
 NOTE: Invalid data for condom in line 8 105-106.
 NOTE: Invalid data for risk in line 8 108-125.
 8         Not Received,Black/African American,Male,Male,Heterosexual,Not Homeless,West Hollywood MTU,28-Apr-18
      101  ,39,No,Did not use condom,High 130
 rapid_syphilis=. race=. gendec=. genderb=. sex_o=. housing_status=. sessiondate=. age=. druguse=39 condom=. risk=. _ERROR_=1 _N_=7
 NOTE: Invalid data for rapid_syphilis in line 9 1-12.
 NOTE: Invalid data for race in line 9 14-24.
 NOTE: Invalid data for gendec in line 9 26-36.
 NOTE: Invalid data for genderb in line 9 38-41.
 NOTE: Invalid data for sex_o in line 9 43-58.
 NOTE: Invalid data for housing_status in line 9 60-71.
 NOTE: Invalid data for sessiondate in line 9 73-90.
 NOTE: Invalid data for age in line 9 92-100.
 NOTE: Invalid data for condom in line 9 105-106.
 NOTE: Invalid data for risk in line 9 108-121.
 RULE:     ----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0                      
 9         Not Received,Multiracial,Transgender,Male,Unknown/Declined,Not Homeless,West Hollywood MTU,28-Apr-18
      101  ,39,No,Did use condom,Low 125
 rapid_syphilis=. race=. gendec=. genderb=. sex_o=. housing_status=. sessiondate=. age=. druguse=39 condom=. risk=. _ERROR_=1 _N_=8
 NOTE: Invalid data for rapid_syphilis in line 10 1-8.
 NOTE: Invalid data for race in line 10 10-14.
 NOTE: Invalid data for gendec in line 10 16-19.
 NOTE: Invalid data for genderb in line 10 21-24.
 NOTE: Invalid data for sex_o in line 10 26-36.
 NOTE: Invalid data for housing_status in line 10 38-49.
 NOTE: Invalid data for sessiondate in line 10 51-68.
 NOTE: Invalid data for age in line 10 70-78.
 NOTE: Invalid data for condom in line 10 83-84.
 NOTE: Invalid data for risk in line 10 86-99.
 10        Received,White,Male,Male,Gay/Lesbian,Not Homeless,West Hollywood MTU,28-Apr-18,29,No,Did use condom,
      101  High 104
 rapid_syphilis=. race=. gendec=. genderb=. sex_o=. housing_status=. sessiondate=. age=. druguse=29 condom=. risk=. _ERROR_=1 _N_=9
 NOTE: Invalid data for rapid_syphilis in line 11 1-12.
 NOTE: Invalid data for race in line 11 14-18.
 NOTE: Invalid data for gendec in line 11 20-23.
 NOTE: Invalid data for genderb in line 11 25-28.
 NOTE: Invalid data for sex_o in line 11 30-40.
 NOTE: Invalid data for housing_status in line 11 42-53.
 NOTE: Invalid data for sessiondate in line 11 55-72.
 NOTE: Invalid data for age in line 11 74-82.
 NOTE: Invalid data for condom in line 11 87-88.
 NOTE: Invalid data for risk in line 11 90-103.
 11        Not Received,White,Male,Male,Gay/Lesbian,Not Homeless,West Hollywood MTU,28-Apr-18,26,No,Did use con
      101  dom,Low 107
 rapid_syphilis=. race=. gendec=. genderb=. sex_o=. housing_status=. sessiondate=. age=. druguse=26 condom=. risk=. _ERROR_=1 _N_=10
 NOTE: Invalid data for rapid_syphilis in line 12 1-12.
 NOTE: Invalid data for race in line 12 14-18.
 NOTE: Invalid data for gendec in line 12 20-23.
 NOTE: Invalid data for genderb in line 12 25-28.
 NOTE: Invalid data for sex_o in line 12 30-40.
 NOTE: Invalid data for housing_status in line 12 42-53.
 NOTE: Invalid data for sessiondate in line 12 55-72.
 NOTE: Invalid data for age in line 12 74-82.
 NOTE: Invalid data for condom in line 12 87-88.
 NOTE: Invalid data for risk in line 12 90-103.
 12        Not Received,Asian,Male,Male,Gay/Lesbian,Not Homeless,West Hollywood MTU,28-Apr-18,21,No,Did use con
      101  dom,Low 107
 rapid_syphilis=. race=. gendec=. genderb=. sex_o=. housing_status=. sessiondate=. age=. druguse=21 condom=. risk=. _ERROR_=1 _N_=11
 NOTE: Invalid data for rapid_syphilis in line 13 1-12.
 NOTE: Invalid data for race in line 13 14-24.
 NOTE: Invalid data for gendec in line 13 26-29.
 NOTE: Invalid data for genderb in line 13 31-34.
 NOTE: Invalid data for sex_o in line 13 36-43.
 NOTE: Invalid data for housing_status in line 13 45-56.
 NOTE: Invalid data for sessiondate in line 13 58-75.
 NOTE: Invalid data for age in line 13 77-85.
 NOTE: Invalid data for condom in line 13 90-91.
 NOTE: Invalid data for risk in line 13 93-110.
 13        Not Received,Multiracial,Male,Male,Bisexual,Not Homeless,West Hollywood MTU,28-Apr-18,27,No,Did not 
 RULE:     ----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0                      
      101  use condom,High 115
 rapid_syphilis=. race=. gendec=. genderb=. sex_o=. housing_status=. sessiondate=. age=. druguse=27 condom=. risk=. _ERROR_=1 _N_=12
 NOTE: Invalid data for rapid_syphilis in line 14 1-12.
 NOTE: Invalid data for race in line 14 14-18.
 NOTE: Invalid data for gendec in line 14 20-23.
 NOTE: Invalid data for genderb in line 14 25-28.
 NOTE: Invalid data for sex_o in line 14 30-40.
 NOTE: Invalid data for housing_status in line 14 42-53.
 NOTE: Invalid data for sessiondate in line 14 55-72.
 NOTE: Invalid data for age in line 14 74-82.
 NOTE: Invalid data for condom in line 14 87-88.
 NOTE: Invalid data for risk in line 14 90-103.
 14        Not Received,White,Male,Male,Gay/Lesbian,Not Homeless,West Hollywood MTU,28-Apr-18,61,No,Did use con
      101  dom,Low 107
 rapid_syphilis=. race=. gendec=. genderb=. sex_o=. housing_status=. sessiondate=. age=. druguse=61 condom=. risk=. _ERROR_=1 _N_=13
 NOTE: Invalid data for rapid_syphilis in line 15 1-12.
 NOTE: Invalid data for race in line 15 14-18.
 NOTE: Invalid data for gendec in line 15 20-23.
 NOTE: Invalid data for genderb in line 15 25-28.
 NOTE: Invalid data for sex_o in line 15 30-40.
 NOTE: Invalid data for housing_status in line 15 42-53.
 NOTE: Invalid data for sessiondate in line 15 55-72.
 NOTE: Invalid data for age in line 15 74-82.
 NOTE: Invalid data for condom in line 15 87-88.
 NOTE: Invalid data for risk in line 15 90-107.
 15        Not Received,White,Male,Male,Gay/Lesbian,Not Homeless,West Hollywood MTU,28-Apr-18,31,No,Did not use
      101   condom,High 112
 rapid_syphilis=. race=. gendec=. genderb=. sex_o=. housing_status=. sessiondate=. age=. druguse=31 condom=. risk=. _ERROR_=1 _N_=14
 NOTE: Invalid data for rapid_syphilis in line 16 1-12.
 NOTE: Invalid data for race in line 16 14-35.
 NOTE: Invalid data for gendec in line 16 37-40.
 NOTE: Invalid data for genderb in line 16 42-45.
 NOTE: Invalid data for sex_o in line 16 47-57.
 NOTE: Invalid data for housing_status in line 16 59-70.
 NOTE: Invalid data for sessiondate in line 16 72-89.
 NOTE: Invalid data for age in line 16 91-99.
 NOTE: Invalid data for condom in line 16 104-105.
 NOTE: Invalid data for risk in line 16 107-124.
 16        Not Received,Black/African American,Male,Male,Gay/Lesbian,Not Homeless,West Hollywood MTU,28-Apr-18,
      101  38,No,Did not use condom,High 129
 rapid_syphilis=. race=. gendec=. genderb=. sex_o=. housing_status=. sessiondate=. age=. druguse=38 condom=. risk=. _ERROR_=1 _N_=15
 NOTE: Invalid data for rapid_syphilis in line 17 1-12.
 NOTE: Invalid data for race in line 17 14-18.
 NOTE: Invalid data for gendec in line 17 20-23.
 NOTE: Invalid data for genderb in line 17 25-28.
 NOTE: Invalid data for sex_o in line 17 30-40.
 NOTE: Invalid data for housing_status in line 17 42-53.
 NOTE: Invalid data for sessiondate in line 17 55-72.
 NOTE: Invalid data for age in line 17 74-82.
 NOTE: Invalid data for condom in line 17 87-88.
 NOTE: Invalid data for risk in line 17 90-107.
 17        Not Received,White,Male,Male,Gay/Lesbian,Not Homeless,West Hollywood MTU,28-Apr-18,55,No,Did not use
      101   condom,High 112
 rapid_syphilis=. race=. gendec=. genderb=. sex_o=. housing_status=. sessiondate=. age=. druguse=55 condom=. risk=. _ERROR_=1 _N_=16
 NOTE: Invalid data for rapid_syphilis in line 18 1-12.
 NOTE: Invalid data for race in line 18 14-18.
 NOTE: Invalid data for gendec in line 18 20-23.
 NOTE: Invalid data for genderb in line 18 25-28.
 NOTE: Invalid data for sex_o in line 18 30-40.
 NOTE: Invalid data for housing_status in line 18 42-53.
 NOTE: Invalid data for sessiondate in line 18 55-72.
 NOTE: Invalid data for age in line 18 74-82.
 NOTE: Invalid data for condom in line 18 87-88.
 NOTE: Invalid data for risk in line 18 90-107.
 RULE:     ----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0                      
 18        Not Received,White,Male,Male,Gay/Lesbian,Not Homeless,West Hollywood MTU,28-Apr-18,21,No,Did not use
      101   condom,High 112
 rapid_syphilis=. race=. gendec=. genderb=. sex_o=. housing_status=. sessiondate=. age=. druguse=21 condom=. risk=. _ERROR_=1 _N_=17
 NOTE: Invalid data for rapid_syphilis in line 19 1-12.
 NOTE: Invalid data for race in line 19 14-18.
 NOTE: Invalid data for gendec in line 19 20-23.
 NOTE: Invalid data for genderb in line 19 25-28.
 NOTE: Invalid data for sex_o in line 19 30-40.
 NOTE: Invalid data for housing_status in line 19 42-53.
 NOTE: Invalid data for sessiondate in line 19 55-72.
 NOTE: Invalid data for age in line 19 74-82.
 NOTE: Invalid data for condom in line 19 87-88.
 NOTE: Invalid data for risk in line 19 90-107.
 19        Not Received,White,Male,Male,Gay/Lesbian,Not Homeless,West Hollywood MTU,28-Apr-18,18,No,Did not use
      101   condom,High 112
 rapid_syphilis=. race=. gendec=. genderb=. sex_o=. housing_status=. sessiondate=. age=. druguse=18 condom=. risk=. _ERROR_=1 _N_=18
 NOTE: Invalid data for rapid_syphilis in line 20 1-12.
 NOTE: Invalid data for race in line 20 14-18.
 NOTE: Invalid data for gendec in line 20 20-23.
 NOTE: Invalid data for genderb in line 20 25-28.
 NOTE: Invalid data for sex_o in line 20 30-40.
 NOTE: Invalid data for housing_status in line 20 42-53.
 NOTE: Invalid data for sessiondate in line 20 55-72.
 NOTE: Invalid data for age in line 20 74-82.
 NOTE: Invalid data for condom in line 20 87-88.
 NOTE: Invalid data for risk in line 20 90-103.
 20        Not Received,Asian,Male,Male,Gay/Lesbian,Not Homeless,West Hollywood MTU,28-Apr-18,26,No,Did use con
      101  dom,Low 107
 rapid_syphilis=. race=. gendec=. genderb=. sex_o=. housing_status=. sessiondate=. age=. druguse=26 condom=. risk=. _ERROR_=1 _N_=19
 NOTE: Invalid data for rapid_syphilis in line 21 1-12.
 NOTE: Invalid data for race in line 21 14-18.
 NOTE: Invalid data for gendec in line 21 20-23.
 NOTE: Invalid data for genderb in line 21 25-28.
 NOTE: Invalid data for sex_o in line 21 30-41.
 NOTE: Invalid data for housing_status in line 21 43-54.
 NOTE: Invalid data for sessiondate in line 21 56-73.
 NOTE: Invalid data for age in line 21 75-83.
 NOTE: Invalid data for condom in line 21 88-89.
 NOTE: Invalid data for risk in line 21 91-108.
 WARNING: Limit set by ERRORS= option reached.  Further errors of this type will not be printed.
 21        Not Received,Asian,Male,Male,Heterosexual,Not Homeless,West Hollywood MTU,28-Apr-18,22,No,Did not us
      101  e condom,High 113
 rapid_syphilis=. race=. gendec=. genderb=. sex_o=. housing_status=. sessiondate=. age=. druguse=22 condom=. risk=. _ERROR_=1 _N_=20
 NOTE: 6981 records were read from the infile '/home/u49152646/EPG194/rapid_syphilis/sample.csv'.
       The minimum record length was 90.
       The maximum record length was 155.
 NOTE: The data set WORK.SAMPLE has 6981 observations and 11 variables.
 NOTE: DATA statement used (Total process time):
       real time           0.03 seconds
       user cpu time       0.01 seconds
       system cpu time     0.00 seconds
       memory              1407.65k
       OS Memory           33452.00k
       Timestamp           08/05/2020 03:52:58 PM
       Step Count                        120  Switch Count  2
       Page Faults                       0
       Page Reclaims                     251
       Page Swaps                        0
       Voluntary Context Switches        20
       Involuntary Context Switches      0
       Block Input Operations            1200
       Block Output Operations           1288
       
 
 77         
 78         OPTIONS NONOTES NOSTIMER NOSOURCE NOSYNTAXCHECK;
 SYMBOLGEN:  Macro variable GRAPHTERM resolves to GOPTIONS NOACCESSIBLE;
 90

Re: Physical file does not exist

KurtBremser — Wed, 05 Aug 2020 16:41:44 GMT

When SAS tells you a file is not there, it's not there.

Did you copy/paste the file path from the navigation pane in SAS Studio?

Mind that the Linux system of SAS ODA is case sensitive, so correct spelling of pathnames is essential.

Re: Physical file does not exist

Kimberly_2020 — Wed, 05 Aug 2020 15:17:18 GMT

So i see that the s drive is not on my computer or on SAS studio...My folder and csv file were the first thing i uploaded into files and folder shortcuts....Can you look at the code and tell me why it keeps saying file does not exist....and I watched the videos that's where I noticed the s drive was missing.

proc import datafile= '/home/u49152646/EPG194/rapid_syphilis.csv'
			DBMS= CSV
			out= work.import replace;
run;

Log:

1          OPTIONS NONOTES NOSTIMER NOSOURCE NOSYNTAXCHECK;
 SYMBOLGEN:  Macro variable _SASWSTEMP_ resolves to /home/u49152646/.sasstudio/.images/df44adc9-fc7c-4f0d-819e-04c0171340b2
 SYMBOLGEN:  Some characters in the above value which were subject to macro quoting have been unquoted for printing.
 SYMBOLGEN:  Macro variable GRAPHINIT resolves to GOPTIONS RESET=ALL GSFNAME=_GSFNAME;
 72         
 73         proc import datafile= '/home/u49152646/EPG194/rapid_syphilis.csv'
 74         DBMS= CSV
 75         out= work.import replace;
 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.
 ERROR: Physical file does not exist, /home/u49152646/EPG194/rapid_syphilis.csv. 
 ERROR: Import unsuccessful.  See SAS Log for details.
 NOTE: The SAS System stopped processing this step because of errors.
 NOTE: PROCEDURE IMPORT used (Total process time):
       real time           0.02 seconds
       user cpu time       0.02 seconds
       system cpu time     0.00 seconds
       memory              8220.50k
       OS Memory           39196.00k
       Timestamp           08/05/2020 03:15:33 PM
       Step Count                        78  Switch Count  5
       Page Faults                       0
       Page Reclaims                     1115
       Page Swaps                        0
       Voluntary Context Switches        26
       Involuntary Context Switches      0
       Block Input Operations            0
       Block Output Operations           40

Re: Physical file does not exist

KurtBremser — Wed, 05 Aug 2020 05:40:38 GMT

The tutorials found here also cover uploading your data.

Did your teacher/tutor not guide you to these pages?

Re: Physical file does not exist

KurtBremser — Wed, 05 Aug 2020 05:33:53 GMT

wrote:

SAS on demand for Academics

This means your SAS runs in the AWS cloud on Linux and does not have access to your desktop environment, which includes the S: drive.

You need to upload your file first with SAS Studio. After that, you can get the correct path to it by right-clicking on it in the SAS Studio navigation pane.

Re: Physical file does not exist

Kimberly_2020 — Wed, 05 Aug 2020 05:20:23 GMT

/*Import a CSV File*/
options Mprint Mlogic SGEN;

%let path=S:\CSV Import;
options validvarname=v7;

proc import datafile= "s:\CSV Import\rapid_syphilis.csv"
			out=syphilis
			dbms=csv replace;
run;

This is my log:

1          OPTIONS NONOTES NOSTIMER NOSOURCE NOSYNTAXCHECK;
 SYMBOLGEN:  Macro variable _SASWSTEMP_ resolves to /home/u49152646/.sasstudio/.images/b114a1e4-9dfe-4060-b4d9-b3e222d0734a
 SYMBOLGEN:  Some characters in the above value which were subject to macro quoting have been unquoted for printing.
 SYMBOLGEN:  Macro variable GRAPHINIT resolves to GOPTIONS RESET=ALL GSFNAME=_GSFNAME;
 72         
 73         /*Import a CSV File*/
 74         options Mprint Mlogic SGEN;
 75         
 76         %let path=S:\CSV Import;
 77         options validvarname=v7;
 78         
 79         proc import datafile= "s:\CSV Import\rapid_syphilis.csv"
 80         out=syphilis
 81         dbms=csv replace;
 82         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.
 ERROR: Physical file does not exist, /pbr/biconfig/940/Lev1/SASApp/s:\CSV Import\rapid_syphilis.csv. 
 ERROR: Import unsuccessful.  See SAS Log for details.
 NOTE: The SAS System stopped processing this step because of errors.
 NOTE: PROCEDURE IMPORT used (Total process time):
       real time           0.02 seconds
       user cpu time       0.02 seconds
       system cpu time     0.01 seconds
       memory              8217.00k
       OS Memory           39452.00k
       Timestamp           08/05/2020 05:14:25 AM
       Step Count                        133  Switch Count  5
       Page Faults                       0
       Page Reclaims                     1183
       Page Swaps                        0
       Voluntary Context Switches        25
       Involuntary Context Switches      1
       Block Input Operations            0
       Block Output Operations           40
       
 83         
 84         
 85         
 86         OPTIONS NONOTES NOSTIMER NOSOURCE NOSYNTAXCHECK;
 SYMBOLGEN:  Macro variable GRAPHTERM resolves to GOPTIONS NOACCESSIBLE;
 98

Re: Physical file does not exist

Kimberly_2020 — Wed, 05 Aug 2020 05:18:08 GMT

SAS on demand for Academics

Re: Physical file does not exist

KurtBremser — Wed, 05 Aug 2020 04:17:47 GMT

Which kind of SAS installation are you using?

University Edition in a downloaded virtual machine
SAS on Demand for Academics
licensed SAS in a local installation
licensed SAS in a client/server installation

All these need different methods for accessing external files and defining libnames, so it is essential for us to know how you use SAS.

Re: Physical file does not exist

Reeza — Wed, 05 Aug 2020 02:27:33 GMT

You need to show your whole code and log. We're seeing bits and pieces that don't make sense.

Re: Physical file does not exist

Kimberly_2020 — Tue, 04 Aug 2020 20:04:49 GMT

libname syphilis "/home/u49152645/syphilis";

Note:

1          OPTIONS NONOTES NOSTIMER NOSOURCE NOSYNTAXCHECK;
 72         
 73         libname syphilis "/home/u49152645/syphilis";
 NOTE: Library SYPHILIS does not exist.
 74         
 75         OPTIONS NONOTES NOSTIMER NOSOURCE NOSYNTAXCHECK;
 87

Re: Physical file does not exist

ballardw — Tue, 04 Aug 2020 20:11:59 GMT

The filename should be in quotes

proc import datafile= "s:\CSV Import\rapid_syphilis.csv"

The only output Proc Import will create is a SAS data set. Not CSV.

So you specify a library name and data set name.

out= libname.dataset

which uses a single dot between the SAS library name and the data set name. Multiple dots are right out. Data set names can only have letters, digits and the _ character.

If you later want to send SAS data out to a CSV file you would use Proc Export.