topic Re: ERROR: Physical file does not exist in SAS Programming

ERROR: Physical file does not exist

astha8882000 — Thu, 10 Jan 2019 02:22:35 GMT

Hello,

The aim of this code is just to get create a log file in the unix location but I've been getting this error.

These are the steps I've taken so far:

1. I checked the shared unix path to make sure I have access

2. Made sure the unix path is written correctly

3. made sure the folders were created and had read write rights.

4. I even created a dummy document but nothing seems to get rid of this error and the log displays nothing useful, just the below statements all over again.

All the posts in this forum regarding this error were mainly due to its usage in infile statement, so I couldn't find anything similar.

Would appreciate some help

filename pswrdfile "some password file location" ;
data _null_ ;
           infile pswrdfile truncover;
           input line :$50.;
           call symputx('dtbspswrd',line);
     run ;
 

      %put & dtbspswrd ;

%let unix_path = some unix path location;
proc printto log = "&unix_path./log/prjname_log.txt"; 
run;


options nocenter source2 mlogic symbolgen nomprint;

Proc SQL;
CONNECT TO teradata (user="%sysget(USER)" password="& dtbspswrd." tdpid=aprtera mode=teradata); 
CREATE TABLE def as
Select * From connection to teradata
(SELECT top 10 * FROM some_table);
DISCONNECT FROM TERADATA;
QUIT;

proc contents data= def;
run;

proc printto; run;

Adding log:

GOPTIONS ACCESSIBLE;
filename pswrdfile "some password file location" ;
data _null_ ;
           infile pswrdfile truncover;
           input line :$50.;
           call symputx('dtbspswrd',line);
     run ;
 
NOTE: The infile PSWRDFILE is:
Filename = some password file location,
Owner Name = [my user id], Group Name = sasuser2,
Last Modified = 06Dec2018;11:36:54,
File Size (bytes) = 40

NOTE: 1 record was read from the infile PSWRDFILE.
The minimum record length was 40.
The maximum record length was 40.
NOTE: DATA statement used (Total process time): 
real time  0.01 seconds
cpu time   0.01 seconds

      %put & dtbspswrd ;
SYMBOLGEN: Macro variable DTBSPSWRD resolves to {Encrypted password}

%let unix_path = some unix path location;

proc printto log = "&unix_path./log/prjname_log.txt"; 
SYMBOLGEN: Macro variable UNIX_PATH resolves to 'some unix path location'

run;

ERROR: Physical file does not exist, some unix path location/log/prjname_log.txt
NOTE: The SAS System stopped processing this step because of errors.
options nocenter source2 mlogic symbolgen nomprint;

Proc SQL;
CONNECT TO teradata (user="%sysget(USER)" password="& dtbspswrd." tdpid=aprtera mode=teradata); 
CREATE TABLE def as
Select * From connection to teradata
(SELECT top 10 * FROM some_table);

NOTE: Table WORK.DEF created, with 13 rows and 700 columns

DISCONNECT FROM TERADATA;
QUIT;

NOTE: PROCEDURE SQL used (Total process time):
real time  15.30 seconds
cpu time   0.04 seconds

proc contents data= def;
run;

proc printto; run;

Re: ERROR: Physical file does not exist

VDD — Thu, 10 Jan 2019 01:42:33 GMT

Did you post your log with the errors?

you have a space after your ampersand

My first sujestion would be to change this:

password="& dtbspswrd."

to this:

password="&dtbspswrd."

Re: ERROR: Physical file does not exist

astha8882000 — Thu, 10 Jan 2019 02:23:26 GMT

Space was a typo, I removed it, thanks. That didn't help with the error sadly. Also updated the logs. Thank you for your help.

Re: ERROR: Physical file does not exist

Patrick — Thu, 10 Jan 2019 03:40:53 GMT

@astha8882000

Make sure that the path....

some unix path location/log

....exists and is accessible out of the server context where your program executes from.

Re: ERROR: Physical file does not exist

astha8882000 — Thu, 10 Jan 2019 03:48:05 GMT

Yes, this path exists and I can access it through winscp. Is there a way to check if or not I can access it through my code?

Re: ERROR: Physical file does not exist

r_behata — Thu, 10 Jan 2019 03:49:34 GMT

Try inserting the "/" to before the macro variable , in case it does not resolve it along with "&unix_path"

proc printto log = "/&unix_path./log/prjname_log.txt"; 
run;

Re: ERROR: Physical file does not exist

SASKiwi — Thu, 10 Jan 2019 03:53:06 GMT

Where is your SAS program running? On the same server as the Unix file paths or some other computer?

Re: ERROR: Physical file does not exist

Patrick — Thu, 10 Jan 2019 06:53:49 GMT

@astha8882000

If you execute the following code..

%put &unix_path./log;

...and then copy/paste the resolved path from the log 1:1 into WinSCP: Does this work?

Is the user you use with WinSCP the same than the one under which the SAS program executes?

Re: ERROR: Physical file does not exist

astha8882000 — Thu, 10 Jan 2019 15:59:11 GMT

It's running on the same server. All the other codes run the same way too so I feel okay about that part.

Re: ERROR: Physical file does not exist

astha8882000 — Thu, 10 Jan 2019 16:04:38 GMT

that didn't work either. 😞

Re: ERROR: Physical file does not exist

astha8882000 — Thu, 10 Jan 2019 16:09:05 GMT

This is what I get when I try that: WARNING: Apparent symbolic reference UNIX_PATH not resolved.

Re: ERROR: Physical file does not exist

Tom — Thu, 10 Jan 2019 16:31:51 GMT

A couple of things to double check.

1) That you have specified the path exactly right. Unix paths are case sensitive. If you do not start the path with / then it will be relative to the current working directory for your SAS process.

2) That the path exists on the machine where SAS is running. The machine that SAS runs on might not be the machine that you connect to with your FTP tool to look at the files.

3) That you have permission to read (or write if needed) to the file. The userid that is used to run the SAS code might not be the same as the userid you used in your FTP tool to look at the files.

If your SAS session allows you to execute shell commands then you can do some of the testing yourself. For example this little data step will run an ls and pwd command and dump the output to SAS log.

%let unix_path = some unix path location;
data _null_;
  infile 
"ls -ld &unix_path 
; /bin/pwd
" pipe ;
  input;
  put _infile_;
run;

Re: ERROR: Physical file does not exist

r_behata — Thu, 10 Jan 2019 16:30:13 GMT

Are you running the code from SAS EG ?

If you are running from SAS EG there is an option of selecting a Server : SASAPP from a list. Make sure the SASAPP associated to the target server is selected.

Re: ERROR: Physical file does not exist

astha8882000 — Thu, 10 Jan 2019 17:01:12 GMT

Took care of that, thank you.

Re: ERROR: Physical file does not exist

astha8882000 — Thu, 10 Jan 2019 17:02:04 GMT

What can I do to sort out this warning?

Re: ERROR: Physical file does not exist

r_behata — Thu, 10 Jan 2019 17:04:40 GMT

Great. If it resolves the issue select the correct response and close the thread.

Re: ERROR: Physical file does not exist

astha8882000 — Thu, 10 Jan 2019 19:57:12 GMT

Ok so this warning is sorted. But the issue is still there 😞

Re: ERROR: Physical file does not exist

Patrick — Fri, 11 Jan 2019 00:30:01 GMT

@astha8882000 wrote:
Ok so this warning is sorted. But the issue is still there 😞

So have you tried:

...and then copy/paste the resolved path from the log 1:1 into WinSCP: Does this work?

Re: ERROR: Physical file does not exist

astha8882000 — Fri, 11 Jan 2019 00:39:32 GMT

yes, I did the copy paste and it's accessible that way.

I tried another method, creating the log file on a temporary sasmart location and then do a x "cp command. The log file did get created but it's not copying over to the unix_path location.

Re: ERROR: Physical file does not exist

Patrick — Fri, 11 Jan 2019 00:45:41 GMT

@astha8882000

Read through what @Tom wrote. He's covering pretty much the possible root causes of why that's not working for you.

For testing: Instead of redirecting the log why don't you just first try with a simple filename statement writing "something" to the desired location. If that works then redirecting the log to such a location should work as well.