topic Re: Error message about a missing physical file in SAS Studio

Error message about a missing physical file

wmjklein — Fri, 03 Sep 2021 20:30:46 GMT

I have an error message that has completely stumped me. The pertinent chunk of code is shown below. The message states that a physical file does not exist, named /pbr/bi ... etc. Could someone help me out please? Thank you.

I am running SAS Studio release 3.8 (Enterprise Edition) in Google Chrome, Version 93.0.4577.63 (Official Build)(64-bit). The SAS Studio has the following characteristics:
Build date: Sep 1, 2020 11:12:26 AM
SAS release: 9.04.01M6P11072018
SAS platform: Linux LIN X64 3.10.0-1062.9.1.el7.x86_64

Log chunk begins here

1 OPTIONS NONOTES NOSTIMER NOSOURCE NOSYNTAXCHECK;
NOTE: ODS statements in the SAS Studio environment may disable some output features.
69
70 /*===============================================================+
71 | c:\sys\sas\weight\movingaverage02.sas |
72 | March 15, 2019 |
73 +===============================================================*/
74 /*==================================================================+
75 | |5 |
76 | Initial input. |
77 +==================================================================*/
78 libname home '/home/u57995729';
NOTE: Libref HOME was successfully assigned as follows:
Engine: V9
Physical Name: /home/u57995729
79 libname sasuser2 '/home/u57995729/sasuser.v94';
NOTE: Libref SASUSER2 refers to the same physical library as SASUSER.
NOTE: Libref SASUSER2 was successfully assigned as follows:
Engine: V9
Physical Name: /home/u57995729/sasuser.v94
80 libname weight '/home/u57995729/Weight';
NOTE: Libref WEIGHT was successfully assigned as follows:
Engine: V9
Physical Name: /home/u57995729/Weight
81 filename in '/home/u57995729/Weight/weight01.dat';
82 title;footnote;
83 options nodate number; /* Suppress the date and display page numbers in upper right corner. */
84 data weight;
85 infile in;
86 informat day date7.;
87 format day date7. weight 5.2;
88 input day Weight @@;
89 label weight='Weight'
90 day='Date';
91 run;

ERROR: Physical file does not exist, /pbr/biconfig/940/Lev1/SASApp//home/u57995729/Weight/weight01.dat.
NOTE: The SAS System stopped processing this step because of errors.
WARNING: The data set WORK.WEIGHT may be incomplete. When this step was stopped there were 0 observations and 2 variables.
WARNING: Data set WORK.WEIGHT was not replaced because this step was stopped.
NOTE: DATA statement used (Total process time):
real time 0.00 seconds
user cpu time 0.00 seconds
system cpu time 0.00 seconds
memory 670.65k
OS Memory 24228.00k
Timestamp 09/03/2021 08:06:30 PM
Step Count 34 Switch Count 0
Page Faults 0
Page Reclaims 104
Page Swaps 0
Voluntary Context Switches 0
Involuntary Context Switches 0
Block Input Operations 0
Block Output Operations 8

Re: Error message about a missing physical file

Reeza — Fri, 03 Sep 2021 20:34:55 GMT

Did you create/upload the weight01.dat file?
Can you show a screenshot of Servers Files and Folders pane, specifically under the WEIGHT folder showing your weight01 file?

Re: Error message about a missing physical file

Reeza — Fri, 03 Sep 2021 20:35:46 GMT

FYI since it's unix I also think your paths, folders and file names needs to be lower case not upper cased. Weight vs weight.

Re: Error message about a missing physical file

Kurt_Bremser — Fri, 03 Sep 2021 21:38:55 GMT

filename in '~/Weight/weight01.dat';

Try this.

Re: Error message about a missing physical file

Kurt_Bremser — Fri, 03 Sep 2021 21:42:04 GMT

And make sure that your slashes are simple ASCII slashes, and not some funny UTF characters. And check if some undisplayable character ended up at the beginning of the path, causing it to be mistaken for relative.

Re: Error message about a missing physical file

Tom — Fri, 03 Sep 2021 21:45:49 GMT

That is a very strange error message:

ERROR: Physical file does not exist, /pbr/biconfig/940/Lev1/SASApp//home/u57995729/Weight/weight01.dat.

It is prefixing the current working directory as if your filename did not start with a /.

Are you sure that the character that looks like a / is actually a / and not some strange other character that happens to look like a /?

Are you sure there is not some invisible character between the opening quote and /? Try re-typing that line of the code.