Consider using an ATTRIB statement:   data MIRA_RED_ACCOUNTS_2016;       attrib mortgage format=z10. ;       input mortgage : 10.; cards; 123 4567 ; run;   I rarely have a data step w/o an attrib. Define the variables for the data step before creating them so your final dataset is exactly as you want.   ... View more

The best way, IMO, to learn regex is to use RegexBuddy.   https://www.regexbuddy.com/   Worth every penny and then some. ... View more

Use a regular expression. Find a valid pattern here:   http://www.regexlib.com/Search.aspx?k=street+address&c=-1&m=-1&ps=20   That is the simplest and most powerful way of handling it.Split the address into groups and then just assign the groups to the correct variable.     ... View more

There are ways other than VBA script (for example, I use C# and read Excel using a library, but VBA is probably an easy option for you). Alternatives probably abound with stuff such as Python and R.    Loop the tabs and structure in VBA. Should be pretty easy to do.    Another alternative is to use Excel as an ODBC source if you have SAS/Access to ODBC.It doesn't save you from the table names but you can get that by reading the xlsx files as a zip and extracting out the pertinent metadata in the Excel XML files.   Take one of your xlsx files, copy it, then rename it to a .zip extension. You can see the structure.   There are also probably command line tools, for free, that will do this for you. It is a fairly common task to export Excel to CSV. ... View more

It is hard to understand what is happening on a system w/o more information. In a system, they normally operate on a round robin sort of flow so some things may be waiting for a system to free up. With loads of processes, and SAS jobs (in general), you are I/O bound. Normally SAS is I/O bound. The trick is to separate the I/O channels but that may not be your issue w/o more info.   Can you split the jobs so that they are reading from different I/O channels? You indicate no issues on RAM or CPU but that is normally not what slows SAS down.   Too many jobs actually can hurt a system since it will constantly buffer in and out. You are normally better off finding the optimal level vs picking a random number, like 300, and shooting them all at the same time. Do 10, then 50, then 100, so on. Find a balance.   In general, the issue is 'normally' not a system issue but the code logic for what you are trying.   Hip shooting here, just what I have seen.   ... View more

I wrote a blog post a ways back on using Bing and the REST APIs. It might shed some light.   http://savian.blogspot.com/2013/12/sas-and-bing-maps-api.html   Sorry, haven't looked at this in a long time.  ... View more

Try executing a PROC SOAP;RUN; and see what the log says. i bet it will throw an error but say that you didn't supply enough parameters.  ... View more

Is it a license issue (you are not supposed to run Base SAS)? From what I can quickly tell, Base SAS is there. I quickly looked at some documentation and some of the supporting files are *.sas files. You can try and run a command-line for a simple sas program and see if it works. ... View more

I can't test for you right now but have you considered using PROC SOAP then doing the manipulation once it is a dataset? ... View more

http://www2.sas.com/proceedings/sugi30/135-30.pdf ... View more