Remove encoding when using dictionary.columns

[jenim514]

Hi,

I'm reading in many datasets and only extracting the vars I need using dictionary.colums.  However, these datasets have some encoding that I deed to remove as I'm getting some warnings in my log.  Here is my code:  Is there any place in my sql code I can pop in (encoding =ascii)?

proc sql noprint;
select distinct memname
into :var1 - :var9999
from dictionary.columns
where upcase(libname) = "DB" & index(name, strip(memname)||"DAT")^=0 and index(memname,'CODE')=0 & index(name,"IG2")=0 & index(name,"PTT")=0 & index(name,"SV")=0 ;
%let sets = &sqlobs;
quit;
%put &sets.;

Getting warnings like this in the log

INFO: Data file DB.PFT.DATA is in a format that is native to another host, or the file encoding does not match the session
encoding. Cross Environment Data Access will be used, which might require additional CPU resources and might reduce performance.
INFO: Data file DB.PH.DATA is in a format that is native to another host, or the file encoding does not match the session encoding.
Cross Environment Data Access will be used, which might require additional CPU resources and might reduce performance.
INFO: Data file DB.PK.DATA is in a format that is native to another host, or the file encoding does not match the session encoding.
Cross Environment Data Access will be used, which might require additional CPU resources and might reduce performance.
INFO: Data file DB.PKR.DATA is in a format that is native to another host, or the file encoding does not match the session

Help is appreciated!

[ChrisNZ · Accepted solution]

These are not warnings.

When the dictionary accesses the tables to extract metadata, it encounters data sets that contain data encoded differently than your current session, or maybe these tables where created on a different host (such as UNIX or Linux).

As long as these tables are kept as is, the note will be displayed. nothing to worry about. 

You'd have to re-create them to get rid of that note. Be careful not to lose data.