don't hijack a thread that's two years old. Almost nobody will see your question. Open your own thread in SAS Programming. in this new thread, post your whole log (from the filename statement to the ERROR message), using the {i} button. ... View more

@jjames1 wrote: But how can I read it as a text when all the mapping is done automatically?   I believe the previous time you asked this question the suggestion was to save the map file, edit it for the problem variables to create text variables and then parse the resulting text. Did you try that approach?   Or is this an endemic problem where you are getting many different structured xml files with the same data problem? In which case it may well be worth working up the chain of the data to find out what is putting invalid dates into a "date" field. It will help if you have worked through one example of correcting the xml map , importing the data and correcting the issue. Record the time involved to point out to managment the costs involved in fixing something that IMHO is a "shoot yourself in the foot" type of error. ... View more

Here is link to SAS page with links to documentation on XML processing in SAS. http://support.sas.com/rnd/base/xmlengine/   The little XMLMAP editing I have done is pretty straight forward, but it depends a lot on the complexity of the XML.  If you change your code like this then you are creating permanent file with the XMLMAP instructions.     filename ABC '/folders/myfolders/temp.xmlmap'; libname ABC xmlv2 '/folders/myfolders/temp.xml' automap=replace xmlmap=ABC ; proc copy in=ABC out=work noclone; run; Once you have fixed the map file then use this code to re-read the XML file. filename ABC '/folders/myfolders/temp.xmlmap'; libname ABC xmlv2 '/folders/myfolders/temp.xml' xmlmap=ABC ; proc copy in=ABC out=work noclone; run; ... View more

The idea is still the same. Wrap your current code into a macro, in my example it's called IMPORT_FILE. The other macro LIST_FILES (first one) creates a list of files. The last data step then uses the file paths to import the files.   I updated some comments in the program that may help you work through it on your side. ... View more

I have an addition to @Astounding's outline, before permanently deleting files perform some verification that you may have the data correctly read/ processed.   If you are contemplating using Proc Import 10K times expect to spend a lot of time getting variable types and lengths aligned afterwards. ... View more

Also the second,  SELECT cats('a.', name) I should be SELECT cats('b.', name) I   ... View more

So you need something like this? data WANT; set TABLEABC; FILEVAR='/users/smith/decrypt.sh '||VAR1; infile DUMMY pipe filevar=FILEVAR; input; put _infile_; run; where your script reads an ecrypted value and writes back a decrypted value.     ... View more

If the final order of the variables in the table is that critical, the solution is going to get more complicated/convoluted. Splitting into two separate queries to separate those variables will cause issues when one of them returns a null value. What I would do is use my last approach and then use the metadata on your final table to pull all the variables into a single macro variable ordered as you want. But again, this is going to get fairly convoluted to get the exact ordering you want. ... View more

What you are attempting is not going to be a one line of code operation though after you get something working without macro code then something can be done. Steps would be 1) verify the existence of the dataset 2) verify the existence of the variable in that data set if both of those conditions are met then you can start looking for specific values.   For instance: proc sql noprint; select * from dictionary.columns where Libname='SASHELP' and Memname=('CLASS') and upcase(name)='SEX' ; quit; %put &sqlobs; The select examines you SAS metadata which has libraries (LIBNAME), data sets (MEMNAME) and variables (NAME) plus characteristics of the variables. The macro variable SQLOBS is an automatic variable that contains the number of records returned by the latest Proc SQL query. &sqlobs will be 0 if no records were returned. Note that the Libname and Memname are stored as upper case in the dictionary table, variablenames may be mixed case so be careful on syntax using those.   So you could run that SQL snippet and and then use %if &sqlobs > 0 %then %do.   If I were doing this frequently might create function or small macro to return the value of sqlobs when passed a library (which could default to WORK) , a data set name and a variable name as parameters. I'll leave that as a small exercise for the intersted reader at this time. ... View more