The street method proc geocode functionality was highly recommended to me by someone else in the industry.  I've read through all of the documentation and believe I've done all of the correct prep before actually executing this method against a dataset.  I've done the following: Loaded the most recent Tiger Data files Loaded the most recent SAS zipcode file Feeding geocode only US based addresses that have been standardized and delivery point validated per the USPS by using 3rd party address cleansing / verificaton software Providing all address fields that geocode will accept at the street method level (address1, city, state, zip5) and converting zip5 from char to num (to equal the sashelp.zipcode format) Loading sashelp.usm and sashelp.zipcode into memory using SASFILE to reduce the number of I/O operations as much as possible As far as confirming that the Tiger Files, zipcode table, and SAS install are working properly, I have seen this proc successfully execute and return the desired results.  If I limit the above specified address subset to obs=1000, proc geocode successfully finishes in under 45 seconds.  However, if I incease the obs to 5000, proc geocode will just hang and never complete.  The odd part here is that it certainly looks like SAS is attempting to do something the entire time the process is "hung."  The memory is a flat line at ~2.18 GB which I would expect as I've loaded what I can (and what I think are being used the most) into memory.  The CPU usage is steady at 49/50 percent with one CPU pegged and the other CPU with nothing. Again, I'd expect this as I don't think proc geocode would use mutli-threading in any way and this would appear to be a CPU expensive proc. I guess my short version of the question is the following.  Has anyone had any success pushing a large number of obs through proc geocode?  I honestly can't think of anything else to try and it's very frustrating to see the proc work like it should with a small number of obs and then see it consistently fail as I increase the number of obs being pushed through.  I have seen this repeatedly happen with different datasets and the fact that it succeeds with an obs=1000 should rule out a corrupt dataset or bad data in general.  To me, it almost looks lke geocode is getting "stuck" on attepting to match an address at the street level and not falling back to a zip or city match.  To support this point, if I increase my obs to 5000 or even 500000 but specify a zip method instead, it completes with no issue. Thanks for your time in reading this and I appreciate any feedback even if it's just confirmation of larger datasets successfully being pushed through this relativel new method. ... View more

I have several EG 4.1 and 4.2 projects currently scheduled without any issue. These projects include mutiple programs, links to create a production process flow, etc. However, I just recently started playing around with the conditional logic feature (macro variables specifically) in 4.3 and I am loving it. It is much easier and more powerful than using the macro facility to control error logic . I've tested my project numerous times by executing the production process flow and everything works as expected. I then scheduled the project to run daily and that's when things went south. It appears that once I've scheduled the same project, it doesn't want to continue executing after it's run the conditional logic code. In my log output, the last thing I see is the EG condition code. The program hangs as soon as it hits this portion of the flow and continues to show as "Running" until it hits the 8 hour scheduled task time cap I set. Has anyone successfully scheduled a project with conditional logic or can point out something I am missing? Once the project has kicked off, I'd expect it to behave the same way as running the process flow manually. Last portion seen in the log output is below. The &download_err. does not resolve to 0 so it should be directed to the else code specified in the GUI and associated with rc = 2. Thanks, Jordan 3 data _NULL_; rc = 0; 4 if &download_err. = 0 then 5 rc = 1; 6 else 7 rc = 2; 8 CALL SYMPUT('_egrc', PUT(rc,1.)); 9 stop; 10 run; NOTE: DATA statement used (Total process time): real time 0.00 seconds user cpu time 0.00 seconds system cpu time 0.00 seconds Memory 2083k OS Memory 6364k Timestamp 4/28/2011 12:58:37 PM Message was edited by: jklein271 ... View more

It runs fine when not using custom formats in the query: proc sql; create table universe_national as select Month, /* PUT(zipcode,$fzipcn.) as Region_Code,*/ /* PUT(zipcode,$fzipcn.) as Region_Name,*/ SUM(universe) as Universe from UNIVERSE.amicount where Month GE '01JAN2000'd and Month LE &current. group by Month/*, Region_Code, Region_Name*/; quit; NOTE: PROCEDURE SQL used (Total process time): real time 38.33 seconds user cpu time 48.38 seconds system cpu time 2.96 seconds However, it takes 30 minutes to execute and bombs if they are included in the select statement and then in the group by statement: proc sql; create table universe_national as select Month, PUT(zipcode,$fzipcn.) as Region_Code, PUT(zipcode,$fzipcn.) as Region_Name, SUM(universe) as Universe from UNIVERSE.amicount where Month GE '01JAN2000'd and Month LE &current. group by Month, Region_Code, Region_Name; quit; ERROR: Sort execution failure. NOTE: The SAS System stopped processing this step because of errors. NOTE: PROCEDURE SQL used (Total process time): real time 26:07.29 user cpu time 35:52.91 system cpu time 10:54.76 ... View more

We recently upgraded to Metadata and have had no luck with the connection found in the subject. The metadata install followed the instructions for IWA so on the EG client side we checked the "Use Integrated Authentication" under my user profile. All of our testing went extremely smooth until I tested a libname connecting to SQL server via SAS/ACCESS to OLE DB. The same exact libname has never had an issue in the old EG 4.1 Repository setup using IWA. However, with IWA checked, the connection fails every time with: ERROR: Error trying to establish connection: Unable to Initialize: Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. ERROR: Error in the LIBNAME statement. It seems the libname is definitely hitting SQL server itself from the looks of that SQL server error. For some reason, my credentials are somehow stripped even with IWA checked. Tech support finally had us try to uncheck IWA and pass our credentials manually via the profile. Even though it's the same u/n and p/w as my network login, it works this way and not via IWA. This is obviously a work around, but we'd rather let IWA drive the credentials. We are waiting for a response from Tech Support, but I thought I'd throw it out there. I can't imagine we are the only EG 4.2 / Metadata setup that is trying to use IWA and SAS/ACCESS to OLE DB to SQL Server. Thanks. ... View more