Outpath issue

[Tom]

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?

[Patrick · Accepted solution]

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