topic Re: Error using proc download while downloading a PDS with sas datsets from mainframe to windows. in SAS Procedures

Error using proc download while downloading a PDS with sas datsets from mainframe to windows.

mnjtrana — Fri, 10 Mar 2017 05:52:45 GMT

Hi,

I am trying to download a PDS using proc download with sas datsets from mainframe to windows.

However the PDs contains sas datasets with sepcial characters and spaces like:

tilsys karatner.sas7bdat

Driftspåvirkning.sas7bdat

So I am not able to download these to windows. Renaming the same is not an options, as they are being updated in mainframe, every now and then. Any help in here is highly appeciated.

I have also tried, options validvarname = all; but it didn't work.

Thanks for the help,

Manjeet

RSUBMIT;
proc download inlib =cxxx.abc.bbc.sas outlib =cxxx.abc.bbc.sas V6TRANSPORT;
RUN;
ENDRSUBMIT;

Re: Error using proc download while downloading a PDS with sas datsets from mainframe to windows.

Kurt_Bremser — Fri, 10 Mar 2017 07:07:51 GMT

Start with setting a strict policy for the naming of server files (and of variables in them), so everything adheres to validvarname=v7.

No blanks, characters of the 26 of the western alphabet, digits and underlines.

This simple measure will make your problems go away in one easy sweep. Everything else is just a time-wasting kludge, as non-standard names will always cost you extra (starting with having to use totally unnecessary quotes)

Re: Error using proc download while downloading a PDS with sas datsets from mainframe to windows.

LinusH — Fri, 10 Mar 2017 08:25:23 GMT

Been a while since I worked on the mainframe, but having this 4 level names i the inlib and outlib options doens't look right. I would suspect a libanme statement, and just that in the inlib=.

Also, why are you using V6TRANSPORT?

Re: Error using proc download while downloading a PDS with sas datsets from mainframe to windows.

Kurt_Bremser — Fri, 10 Mar 2017 08:43:28 GMT

That unicode (vomits, cleans keyboard) character (c3 a5) in the second filename looks quite Scandinavian to me, and I can only imagine what that can cause on machines running with an Indian locale (how would you type such a character?).

If you really get your files from Scandinavia, the people there should be aware that they are working in an international environment and refrain from using locale-specifics in their data. Apart from getting rid of the *@$#!§? blanks.