About hollandnumerics

hollandnumerics · ‎11-08-2017

mj5, There is a simple correlation you should understand when posting a code-related question: The probability of an answer is proportional to the amount of background information, SAS code, log and output you post with your question!

hollandnumerics · ‎11-08-2017

Aamirkhan, There is a simple correlation you should understand when posting a code-related question: The probability of an answer is proportional to the amount of background information, SAS code, log and output you post with your question!

hollandnumerics · ‎11-03-2017

Maaz, As the whole program is SQL, why can't you recode it to run completely inside Teradata? Teradata is designed to run SQL efficiently, so why not let it get on with it. Currently you are doing the following using PROC SQL: extracting 8 (potentially vast?) tables into SAS merging 4 tables each into 2 other temporary SAS tables joining the 2 temporary SAS tables with UNION into another temporary SAS table storing the final table back into Teradata Doing the same steps all in Teradata using Pass-Thru will take SAS out the equation altogether.

hollandnumerics · ‎11-02-2017

Maaz, There is a simple correlation you should understand when posting a code-related question: The probability of an answer is proportional to the amount of SAS code, log and output you post with your question!

hollandnumerics · ‎10-27-2017

SAS Global Forum is being held in Denver in 2018 from Sunday 8th to Wednesday 11th April, and I’ve been invited to present “The Art of Defensive Programming: Coping with Unseen Data” there. Click here for information about my free book draw at SASGF18!

hollandnumerics · ‎04-21-2017

Unfortunately SYSPROD() is only a programmatic way to check the SAS setinit. I was looking for a function to give me the SAS product from a PROC name, e.g. XXPROD('lifetest') => 'STAT', or a number or string meaning SAS/STAT

hollandnumerics · ‎04-20-2017

Format catalogs are dependent on platform AND bit, so catalogs created using Windows and UNIX are not compatible, AND Windows 32-bit and Windows 64-bit create incompatible catalogs too! Much better to specify formats in programs for whatever platform you are using, because that way they are always compatible!

hollandnumerics · ‎04-20-2017

Format catalogs are dependent on platform AND bit, so catalogs created using Windows and UNIX are not compatible, AND Windows 32-bit and Windows 64-bit create incompatible catalogs too! Much better to specify formats in programs for whatever platform you are using, because that way they are always compatible!

hollandnumerics · ‎04-20-2017

I vaguely remember a Data Step function I used a long time ago to match a PROC with a SAS module licence. I think it was something like TSPRD(). Does such a function still exist?..............Phil

hollandnumerics · ‎02-28-2017

Jared, I can see 2 copies of the WORK folder (/SASWork/SAS_work064400005256_pwauslsasgap09) in the error message. I would look at what you are actually providing to the EG Task in &download_from and &download_to, because I don't think what you have in &download_from.&delim.*.csv is "folder/*.csv". .............Phil

hollandnumerics · ‎02-23-2017

Jt1, I suspect you are being impacted by macro variable "scope", because, unless you have defined both &download_from and &download_to outside of the macro, it won't exist outside. Therefore I suggest you add a single statement at the top of your program outside of the macro to make sure the macro variables are available everywhere: %GLOBAL download_from download_to; ..............Phil

hollandnumerics · ‎02-22-2017

JT1, The problems lies in the following SAS statement: %let download_from = %sysfunc(getoption(work))&delim.&datafile...csv; which points to a single file, and gets overwritten by each macro call. My solution, however, depends on your CSV filenames being the only CSV files present in a &download_from folder: %let download_from = %sysfunc(getoption(work)); filename src "&download_from.&delim.&datafile...csv"; You should then be able to use the following text in the Source files box: &download_from.&delim.*.csv Hope this makes sense...........Phil

hollandnumerics · ‎02-16-2017

I've just updated my Windows SAS environment from SAS 9.4M3 64-bit to SAS 9.4M4 64-bit and Enterprise Guide 7.13 HF2, and every time I ran a program I've started seeing 3 warning messages at the top of the SAS Log: WARNING: 'def' was compiled using a different version of SAS. This might result in unexpected behavior. WARNING: 'stat' was compiled using a different version of SAS. This might result in unexpected behavior. WARNING: 'htmlblue' was compiled using a different version of SAS. This might result in unexpected behavior. I don't like seeing error and warning messages in my SAS Log at any time. So I thought I'd help you, so you don't have to search any further, by providing this very easy fix, which is complicated to do in SAS, but easy in Windows Explorer: Open the My SAS Files folder in your My Documents folder, which is actually your SASUSER library. Delete the templat.sas7bitm file, which contains the def, stat and htmlblue style templates. The warning messages should now have gone! 🙂

hollandnumerics · ‎04-06-2016

Will your talk include information for Android app developers too? ........Phil Holland

hollandnumerics · ‎04-06-2016

The Attendee badge was my 13th! Is that unlucky? 😉

Online Status	Offline
Date Last Visited	‎11-20-2025 06:07 AM