About ChrisHemedinger

ChrisHemedinger

Try: %let scope = manage:all; in="grant_type=client_credentials%str(&)scope=&scope."

ChrisHemedinger

If you want the &scope macro variable to be resolved, the IN= value must be in double quotes. Using single quotes will prevent the macro processor from resolving the value.

ChrisHemedinger

Any chance that you are running this in EG or SAS Studio? And if so, have you turned off all of the other output destinations? If you had ODS HTML5 set, for example, with its own style, this could influence the look of your RTF content when that's used at the same time. You can use EG or SAS Studio options to turn off all of the other destinations, or use ODS _ALL_ CLOSE before your code.

ChrisHemedinger

The IOM connection is for the Workspace (compute) server -- bypasses the metadata server. The SAS extension is not metadata-aware (at this point, not sure if that's something we'll pursue). If you can use IOM that will give you more features than SSH. See the matrix of connection capabilities here.

ChrisHemedinger

Hi All, I have updated the article to include a note that other SAS software is needed to support the connection due to encryption protocols. SAS for Windows, SAS Enterprise Guide, or a few other options will include this. Note that SAS EG is available for free to some SODA users if you're enrolled in a course that uses it.

ChrisHemedinger · ‎05-30-2024

Here's some logic lifted from one of my processes that I had to guard against network issues like this. It does not produce a clean log but it does allow the process to continue gracefully. The first trick is to check for the existence of the SYS_PROCHTTP_STATUS_CODE macro before checking for a value. In my case I built in some retry logic, but if it fails again then I fall through and give up. %if %symexist(SYS_PROCHTTP_STATUS_CODE) %then %do; %if &SYS_PROCHTTP_STATUS_CODE. ne 200 or &syserr. ne 0 %then %do; %put WARNING: Expected 200, but received &SYS_PROCHTTP_STATUS_CODE., SYSERR = &syserr.; %put Waiting 20 seconds to retry...; %if &SYS_PROCHTTP_STATUS_CODE. eq 403 %then %do; %put Refreshing auth token; %refreshAuthToken; /* special case where I might need to reauth */ %end; data _null_; rc=sleep(20,1); run; /* call macro that retries here */ %if &SYS_PROCHTTP_STATUS_CODE. ne 200 or &syserr. ne 0 %then %do; %put WARNING: Failed again. Expected 200, but received &SYS_PROCHTTP_STATUS_CODE., SYSERR = &syserr.; %let msgerr = Process stopped after 2 consecutive failures: &SYS_PROCHTTP_STATUS_CODE., see log; %end; %end; %else %do; %put HTTP result: &SYS_PROCHTTP_STATUS_CODE. &SYS_PROCHTTP_STATUS_PHRASE.; %end; %if &syserr. = 0 %then %do; /* Process Result Here */ %end; %end; /* SYMEXIST SYS_PROCHTTP_STATUS_CODE */ %else %do; %put ERROR: PROC HTTP failed! %superq(syserrortext); %let msgerr = Errors in fetching data - see log.; %end;

ChrisHemedinger · ‎05-30-2024

The tcperror condition -- when it happens -- is at a lower level than what PROC HTTP can catch/detect and report in the status macro variables. As a very frequent user of PROC HTTP, I see it only when there are network glitches or issues that might be triggered by a firewall or other environmental conditions. My only advice is to make sure you are up-to-date on SAS maintenance/hotfix releases, and ensure your network environment is stable/available during your SAS job run.

ChrisHemedinger · ‎05-29-2024

Are you using SAS Visual Analytics for this? I'm guessing that's the case given the steps you've described so far. I'll move this topic to the SAS VA forum.

ChrisHemedinger · ‎05-29-2024

@PaigeMiller I think it's more mundane than that. I think it's simply a way to get spurious commercial links into other websites to boost SEO for those outfits. I also think it's ineffective at achieving that outcome, but that doesn't stop people from trying.

ChrisHemedinger · ‎05-24-2024

You'll need to make a similar change for the SAS.DataSet entries in the Windows Registry: HKEY_CLASSES_ROOT\SAS.DataSet.701\shell\BrowsewithEG.8\command Remove the "/openfile" part of the commands. The /openfile directive will reuse an existing EG session if one is running.

ChrisHemedinger · ‎05-18-2024

It looks like you are using SAS Enterprise Miner within the SAS OnDemand environment. I've moved this discussion to the SAS Software for Learning discussion board.

ChrisHemedinger · ‎05-17-2024

Excellent approach by @FreelanceReinh. It reminds me of a challenge I had years ago in validating NPI (national provider identity) numbers, which relies on the Luhn algorithm. I also created an FCMP version!

ChrisHemedinger · ‎05-16-2024

Your query is comparing a date value -- which is essentially a number -- to a range defined by two other values. Since your example value (01/01/2024) is just a series of characters that SQL won't resolve as a date, you have to take a step to convert it to a number. Maybe that value is coming to you from somewhere else and that's why you don't want to use the '01Jan2024'd date literal format. Instead you could convert it "inline" with a function that will yield a number: %sysfunc(inputn(01/01/2024,mmddyy10))

ChrisHemedinger · ‎05-16-2024

"DEV/TEST/PROD": If that term means something to you, then you are probably among our many customers that use SAS software across different environments. You might have one SAS environment for playing around ("dev" for "development"), another for testing candidate changes ("test"), and yet another for production processes ("prod"). SAS Enterprise Guide "Connections" window Or, you might work with different environments that are segregated across business units: one for Finance, for example, and another for Human Resources. You can also create different profiles for a single environment, but with different user accounts -- for example, one account with admin privileges, and another as a "mere mortal" end user. Wouldn't it be convenient to have different shortcuts on your desktop so that you can launch SAS Enterprise Guide and point directly to the environment that you want to use? We thought so, and so we added some command-line options to make this easy to do. (These were added way back in version 4.2 and they still work the same way today!) Two shorcuts for two environments The command-line option is /profile:"ProfileName", where "ProfileName" is the friendly name you used to label your SAS profile definition. (The quotes are optional unless the profile name contains spaces or special characters, in which case the quotes are necessary.) Here is an example command that you can use in a desktop shortcut to connect to the "prod" environment: "C:\Program Files\SAS\EnterpriseGuide\8\seguide.exe" /profile:prod Here is a variation with a space in the profile name ("My Server"): "C:\Program Files\SAS\EnterpriseGuide\8\seguide.exe" /profile:"My Server" And finally, if you want to run with no profile: that is, without connecting to a SAS metadata server at all (using just your local SAS installation), you can run: "C:\Program Files\SAS\EnterpriseGuide\8\seguide.exe" /noprofile Regardless of which profile you launch with, SAS Enterprise Guide will always show any additional "ad hoc" servers that you've defined, including connections to SAS Viya or to other SAS Workspace servers outside of SAS metadata connections.

ChrisHemedinger · ‎05-16-2024

The TODAY() function might be stopping this from passing through to the database. Try using the more standard SQL function DATE() and see if that passes through.

Online Status	Online
Date Last Visited	4 hours ago