topic Re: Syntax Error 22-322 and ERROR: Physical file does not exist, /opt/sas/config/Lev1/SASApp/ in SAS Enterprise Guide

Syntax Error 22-322 and ERROR: Physical file does not exist, /opt/sas/config/Lev1/SASApp/

jon8 — Fri, 15 Jul 2022 13:48:17 GMT

Hey!

I just started an internship and I have to code on SAS. But I have two problems that i didn't heard about on the internet and may be connected to my company network when I try to launch that test script:

DATA WORK.test;

INFILE "C:\Users\Documents\test.txt";

INPUT Column1 Column2;

RUN;

The first one is that error:

ERROR: Physical file does not exist, /opt/sas/config/Lev1/SASApp/C:\Users\Documents\test.txt.

I don't know why the root "/opt/sas/config/Lev1/SASApp/" is there and am I the only one to have that error? I didn't saw it anywhere.

So I have been told to put an 'n' after the path (nobody knows why) just like that:

DATA WORK.test;

INFILE "C:\Users\Documents\test.txt"n;

INPUT Column1 Column2;

RUN;

And now the error is:

ERROR 22-322: Syntax error, expecting one of the following: String, Quoted Chain.

ERROR 200-322: The symbol is not recognized and will be ignored.

What's wrong with the code?

I would really appreciate someone to help me with that case because I'm block if I can't even import a table.

Thanks a lot.

Have a good day!

PS: I'm on 7.1 Version

Re: Syntax Error 22-322 and ERROR: Physical file does not exist, /opt/sas/config/Lev1/SASApp/

PaigeMiller — Fri, 15 Jul 2022 13:54:00 GMT

Your SAS ... most likely SAS Studio ... is running on a server and it cannot access files on your computer's C: drive. The file has to be uploaded to the server first, and then accessed via the proper INFILE statement using the server location of the file.

Something like this:

infile "/opt/sas/config/Lev1/SASApp/test.txt";

but of course, you must use the exact server folder name and what I gave in the example may not be right.

Re: Syntax Error 22-322 and ERROR: Physical file does not exist, /opt/sas/config/Lev1/SASApp/

jon8 — Fri, 15 Jul 2022 14:54:04 GMT

First thanks,

But, just by importing CSV files (File>New>Data>...) I can access to my computer's C: drive. Why can I reach it out in that case ?

Thanks

Re: Syntax Error 22-322 and ERROR: Physical file does not exist, /opt/sas/config/Lev1/SASApp/

jon8 — Fri, 15 Jul 2022 14:56:24 GMT

And also why in the second case have I a Syntax Error ?
Thanks a lot

Re: Syntax Error 22-322 and ERROR: Physical file does not exist, /opt/sas/config/Lev1/SASApp/

PaigeMiller — Fri, 15 Jul 2022 15:02:24 GMT

@jon8 wrote:

First thanks,

But, just by importing CSV files (File>New>Data>...) I can access to my computer's C: drive. Why can I reach it out in that case ?

Ok, first let's establish what SAS interface are you using. Are you using SAS Studio, or something else? If you're not sure, show us a screen capture (click on the "Insert Photos" icon, do not attach files).

Re: Syntax Error 22-322 and ERROR: Physical file does not exist, /opt/sas/config/Lev1/SASApp/

PaigeMiller — Fri, 15 Jul 2022 15:04:15 GMT

@jon8 wrote:
And also why in the second case have I a Syntax Error ?
Thanks a lot

Second case is not valid syntax. You can't use anything that looks like

infile "C:\Users\Documents...

and get it to work from SAS on a server.

Re: Syntax Error 22-322 and ERROR: Physical file does not exist, /opt/sas/config/Lev1/SASApp/

jon8 — Fri, 15 Jul 2022 15:13:56 GMT

Okay

It’s getting clearer for me !
Have a nice week-end!

Re: Syntax Error 22-322 and ERROR: Physical file does not exist, /opt/sas/config/Lev1/SASApp/

jon8 — Fri, 15 Jul 2022 15:19:56 GMT

[image0.jpeg]
Does that image helps you ?

Re: Syntax Error 22-322 and ERROR: Physical file does not exist, /opt/sas/config/Lev1/SASApp/

PaigeMiller — Fri, 15 Jul 2022 15:21:23 GMT

Repeating: click on the "Insert Photos" icon

Re: Syntax Error 22-322 and ERROR: Physical file does not exist, /opt/sas/config/Lev1/SASApp/

jon8 — Fri, 15 Jul 2022 15:34:18 GMT

Sorry

Re: Syntax Error 22-322 and ERROR: Physical file does not exist, /opt/sas/config/Lev1/SASApp/

PaigeMiller — Fri, 15 Jul 2022 15:36:56 GMT

You did not click on the "Insert Photos" icon.

I never download attachments, so please click on the "Insert Photos" icon.

Re: Syntax Error 22-322 and ERROR: Physical file does not exist, /opt/sas/config/Lev1/SASApp/

jon8 — Fri, 15 Jul 2022 15:56:33 GMT

Re: Syntax Error 22-322 and ERROR: Physical file does not exist, /opt/sas/config/Lev1/SASApp/

PaigeMiller — Fri, 15 Jul 2022 16:12:28 GMT

Thanks. I am not all that familiar with how Enterprise Guide interacts with your Windows file system. I think others (perhaps @ChrisHemedinger ) can give a better explanation.

Re: Syntax Error 22-322 and ERROR: Physical file does not exist, /opt/sas/config/Lev1/SASApp/

jon8 — Fri, 15 Jul 2022 16:21:56 GMT

Okay Thanks a lot.
So i Hope he will be able to help me.
Have a good day

Re: Syntax Error 22-322 and ERROR: Physical file does not exist, /opt/sas/config/Lev1/SASApp/

ChrisHemedinger — Fri, 15 Jul 2022 16:30:03 GMT

While SAS Enterprise Guide runs on your local Windows machine, your SAS session is remote (on Linux, most likely) and cannot "see" your local C: drive. So you cannot use SAS syntax to reach your local files on your C drive.

Instead, you must place the data file in a location where your SAS session can read it. For some users that might be on a shared network location that can be accessed by both Windows and Linux -- if you're lucky to have a setup like that in your org. We do here. For example:

Windows: \\netshare\user\myid\data.csv
Linux (and for SAS): /u/myid/data.csv

If you don't have that, you can use the Copy Files task in SAS Enterprise Guide to copy the local data file from SAS to a known location on your remote SAS session. That step can be captured as part of your process flow in a project. I have a video tutorial for this here.

Re: Syntax Error 22-322 and ERROR: Physical file does not exist, /opt/sas/config/Lev1/SASApp/

jon8 — Mon, 18 Jul 2022 10:26:50 GMT

Thanks a lot for your help and your tutorial it's a lot clearer for me!

But on the import data part of the tutorial it seems that you can import data from your C: drive(see attached). Is it because you are not working on a company server ?(*)

Besides, why when I am quoting something it automatically generates that root at the beginning of the quote: "/opt/sas/config/Lev1/SASApp/" and can I get rid of it ? You don'tseem to you have this problem and it may be for the same reason than the first question(*).

Jonathan

Re: Syntax Error 22-322 and ERROR: Physical file does not exist, /opt/sas/config/Lev1/SASApp/

Kurt_Bremser — Mon, 18 Jul 2022 12:00:42 GMT

Your SAS session runs on a Linux server. UNIX systems use a single file navigation tree into which all storage is mounted. The character used to separate directories is the forward slash (and not the backward slash as in Windows). So the root of the whole filesystem is a single slash, and all your pathnames have to start with that, or the system will assume you use a relative path from the current working directory (which is /opt/sas/config/Lev1/SASApp, the place from where the server session was started).

After uploading the file in question to your server (you can use the Copy Files task for this), you need to use the target path in your code.

Re: Syntax Error 22-322 and ERROR: Physical file does not exist, /opt/sas/config/Lev1/SASApp/

jon8 — Wed, 20 Jul 2022 09:52:21 GMT

Hey!

I have a little question after using your tutorial.

Can I create as many Sas Tables as I have csv files(in one code) or it has to be concatenate in one Sas Table ?(just like your four Netflix files were concatenate in one Sas Table)

Thanks for your help.

Jonathan

Re: Syntax Error 22-322 and ERROR: Physical file does not exist, /opt/sas/config/Lev1/SASApp/

Kurt_Bremser — Wed, 20 Jul 2022 10:12:47 GMT

You can create multiple datasets in one data step like this:

data
  a
  b
  c
;
/* further code */
run;

As you see, all datasets need to be named explicitly in the DATA statement.

And you would have to code explicit OUTPUT statements for each of the datasets.

If you want to create X datasets of identical structures for X csv files, you should first evaluate if separate datasets are really needed. You may be better off creating a single dataset, and keeping the name (or part of the name) of the csv file in a separate variable.

If you really need separate datasets, first create a macro that reads a single csv file into a single dataset (both names being macro parameters), and then call this macro repeatedly from a list of the csv files.