About AndrewHowell

AndrewHowell · ‎03-07-2018

I'd have to strongly recommend against storing user credentials in macros, even (so called) masked passwords. If you are running on a metadata platform, rather than define user & password, instead use "authdomain=MyAuthDomain" and set up the authentication domain in metadata (or have your platform admin do it for you). Doesn't directly resolve your macro issue, but since you brought up credentials, thought it worth mentioning. That aside, can you supply code & logs, even if you mask any sensitive information? Also, do the macro variables contain any special characters - an individual quote, an individual bracket, a keyword like OR, IN, etc?

AndrewHowell · ‎03-07-2018

If one of these suggestions helped you fix your problem, please return to this page and select "Accept as Solution" for that suggestion.

AndrewHowell · ‎03-06-2018

Even thought fiscal_date is displayed as a year (format), it is actually still a SAS date value (i.e, a count of the number of days since 01Jan1960). Your SAS date value 2014 is actually 07July1965, which means most if not all of your data will pass the test. Your filter should be: if fiscal_year GE "01Jan2014"d; /*anything starting from 2014 */

AndrewHowell · ‎03-06-2018

So, attempting to handshake from one program to another.. Presumably you'd kick of both EG sessions, and have #2 wait for the handshake from #1. (Also means these two can run on different EG clients, and could even run on different SAS servers/environments, as long as they have access to the common data set - nice touch!) In some sites, the EG connection will timeout after a period of inactivity - what then? EG is really there for interactive sessions, not batch (or triggered) tasks - why interactively run 2 interconnected EG sessions? Would #1 calling a stored process be an alternative in this case? [Also, personal comment from my C & Pascal days - was never a fan of "Goto" statements, much prefer loops, but that's me..]

AndrewHowell · ‎03-06-2018

Ice hockey game Sat 7th - Colorado Avalanche v. St Louis Blues.

AndrewHowell · ‎03-06-2018

Suggestions (to help us help you): If you can , please post the autoexec_usermods.sas file so we have a better idea of what you mean. Plus the statement which causes the reference error. Can you follow the statement with %put _ALL_; and post the results (although remove/mask anything sensitive)

AndrewHowell · ‎03-06-2018

First thoughts - use symputx instead of symput. This removes any leading & trailing blanks which may be invalidating the macro name.

AndrewHowell · ‎03-04-2018

Elliott, once you're done, can you please select the solution you found most helpful & flag it as "Accepted as solution"? Thanks.

AndrewHowell · ‎03-01-2018

@ballardw - agree, but could not tell from the email where these dates needed to be calculated - in a stand-alone data step, in the middle of a PROC SQL, etc. Assuming the date value is preset earlier, I used macros which can effectively be embedded (almost) anywhere. Another alternative is to use FCMP functions?

AndrewHowell · ‎03-01-2018

(See above)

AndrewHowell · ‎03-01-2018

There's more efficient code, but the simplest solution to your existing code is to just change all the symput() functions to symputx() which will remove any embedded leading or trailing spaces. Alternative: data _null_; call symputx("INITIAL_DT",put(today()-1,date9.)); run; %put &=Initial_DT; %let d2=%sysfunc(day("&INITIAL_DT"d),z2.); %let m2=%sysfunc(month("&INITIAL_DT"d),z2.); %let y2=%sysfunc(putn("&INITIAL_DT"d,year2.)); %let y4=%sysfunc(putn("&INITIAL_DT"d,year4.)); %put &m2. &d2. &y2. &y4. ;

AndrewHowell · ‎02-27-2018

This is an exercise from chapter 10 of @Ron_Cody's book Learning SAS(R) by Example:: A Programmer's Guide (The bicycle reference is also a dead giveaway.) Can you not get the answer you are looking for in the book?

AndrewHowell · ‎02-26-2018

We did this YEARS ago (9.2), so it predates Environment Manager, but it was still platform SAS alerting using SMS. Simplest solution was to leverage existing email capability and send small email messages to 5559991234@phonecompany.com. That was a simple enough solution for us. Other companies had an SMS gateway that you could message. The solution really isn't "SAS" per se, but integration with 3rd party solutions. Caveat: of course, this assumes that whatever is causing your platform failure is also NOT causing your alerting capability to fail as well.. (I have found through bitter experience that lack of bad news does not automatically mean good news..) If alerting is that time-critical, then I'd suggest a combination of SAS alerting and non-SAS alerting (Tivoli, BMC Patrol, etc) should a critical SAS service fail.

AndrewHowell · ‎02-22-2018

Really? Are Administrators suddenly obsolete in the new age of SAS Viya?!? (I doubt it.. I mean there's no Metadata Server any more, but there still needs to be someone to keep it all running..) Yes, Admin is a must-have.

AndrewHowell · ‎02-22-2018

They're actually rather savoury, @ChrisHemedinger.. and quite stringy.. [Runs for cover..]

Online Status	Offline
Date Last Visited	‎04-30-2023 01:46 PM