Outpath issue

[A-junamu_-]

I keep running into this error every time I run the outpath and can't figure out the problem. I tried removing and adding the space but it's not working. 

The message "the data file " " is in a format that is native to another host, or the file encoding does not match the session encoding" keeps prompting. 

What is the issue?

Outpath code: 

LIBNAME PG1 "S:/WORKSHOP/EPG1V2/DATA";

%let outpath = "S:/WORKSHOP/EPG1V2/OUTPUT";

[SASKiwi]

Change your OUTPATH macro variable value to not include quotes, as there are quotes already where it is being used:

%let outpath = S:/WORKSHOP/EPG1V2/OUTPUT;

[A-junamu_-]

Yes, I just realized this a minute ago. Thanks!

[A-junamu_-]

But what about the encoding issue? I see this in almost all of my logs. 

[SASKiwi]

Please post your SAS session encoding by running this:

proc options option = encoding;
run;

SAS is simply reporting that the encoding on your SAS dataset does not match the session encoding. Where did the data come from?

[A-junamu_-]

From the sas essentials training program

[SASKiwi]

Run this to compare session and dataset encoding and post the results:

proc options option = encoding;
run;

proc contents data = pg1.storm_final;
run;

[Tom]

---

@A-junamu_- wrote:

But what about the encoding issue? I see this in almost all of my logs. 

---

That is just an informational message that means exactly what it says.  That the dataset was created with a different version of SAS or perhaps even the same version but with different settings such as the character encodings.  It can convert it but the job might run a little slower because it has to do more work than if you were reading a dataset you created with the same version of SAS.

If you have some datasets you are using a lot then copy them over using your current version of SAS and then use the copies instead. 

libname PG1 'path where the foreign datasets live';
libname LOCAL 'some other path where you want the copies to live';
proc copy inlib=pg1 outlib=local noclone;
run;

[A-junamu_-]

I did that, still seeing that message. 

[SASKiwi]

Yes, but only for the PG1 source library version not for the copied LOCAL library version which has had its encoding changed.

[A-junamu_-]

Here's the result. What exactly are you stating "Yes, but only for the PG1 source library version not for the copied LOCAL library version which has had its encoding changed." ?

[Tom]

So to SAS it looks like you are trying reference some type of literal that uses S after the quoted string.

Like TIME literals use a T and DATE literals use a D.

That is because you ran this code:

file = ""S:....

So you have an empty string followed by the letter S.

Why did you include quotes in the macro variable and then add more quotes in the SAS code? 

Either leave the quotes out of the macro variable

%let outpath = S:/WORKSHOP/EPG1V2/OUTPUT ; 

or make sure to double them up when adding more quotes around the outside.  For example by calling the QUOTE() function.

file = %sysfunc(quote(&outpath/pressure.pdf)) 

[A-junamu_-]

There are no quotes on the macro variable. Where do you see the quotes?

[Tom]

---

@A-junamu_- wrote:
There are no quotes on the macro variable. Where do you see the quotes?

---

In the code you posted.

%let outpath = "S:/WORKSHOP/EPG1V2/OUTPUT";

[A-junamu_-]

I don't see what you are seeing. This is what I recently posted.