topic Re: Outpath issue in SAS Programming

Outpath issue

A-junamu_- — Wed, 08 Jun 2022 03:24:31 GMT

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";

Re: Outpath issue

SASKiwi — Wed, 08 Jun 2022 03:32:55 GMT

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;

Re: Outpath issue

A-junamu_- — Wed, 08 Jun 2022 03:41:40 GMT

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

Re: Outpath issue

Tom — Wed, 08 Jun 2022 03:42:11 GMT

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))

Re: Outpath issue

A-junamu_- — Wed, 08 Jun 2022 03:44:58 GMT

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

Re: Outpath issue

SASKiwi — Wed, 08 Jun 2022 03:52:20 GMT

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?

Re: Outpath issue

A-junamu_- — Wed, 08 Jun 2022 03:58:05 GMT

From the sas essentials training program

Re: Outpath issue

SASKiwi — Wed, 08 Jun 2022 04:38:44 GMT

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

proc options option = encoding;
run;

proc contents data = pg1.storm_final;
run;

Re: Outpath issue

Tom — Wed, 08 Jun 2022 05:01:54 GMT

@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;

Re: Outpath issue

A-junamu_- — Wed, 08 Jun 2022 23:51:30 GMT

I did that, still seeing that message.

Re: Outpath issue

A-junamu_- — Thu, 09 Jun 2022 01:09:07 GMT

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

Re: Outpath issue

SASKiwi — Thu, 09 Jun 2022 01:13:53 GMT

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

Re: Outpath issue

Tom — Thu, 09 Jun 2022 04:14:29 GMT

@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";

Re: Outpath issue

A-junamu_- — Fri, 10 Jun 2022 00:46:15 GMT

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

Re: Outpath issue

Tom — Fri, 10 Jun 2022 02:19:23 GMT

And there is nothing in those photographs that says there was any trouble with the libname statement.

In fact the libname statements are not even using any macro variables.

In fact there are not even any errors at all that are visible in those photographs.

The original message posted this code:

Which caused this error message:

So what is that you are you asking about now?

Re: Outpath issue

Patrick — Fri, 10 Jun 2022 07:58:19 GMT

@A-junamu_- May-be next time ask one question at a time.

So for your 2nd question it's exactly as the SAS log tells you:

The session encoding under which you run your SAS session is not the same like the encoding that has been used when creating your source table.

You see such messages for example when you copy a SAS table created under Windows SAS to an environment under Unix SAS. It's just a Note informing you so nothing bad will happen. Such CEDA reading (Cross Environment Data Access) will impact on performance - but that's it.

Re: Outpath issue

A-junamu_- — Sun, 12 Jun 2022 14:54:08 GMT

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." ?