About ChrisHemedinger

ChrisHemedinger

Oh yeah, sure does! Thanks @JimLoughlin and way to write an app with staying power, @RichardDeVen

ChrisHemedinger

In 2008, SAS programmer Mark Paschalidis made this announcement on the SAS-L mailing list: For a while now I've been working on an interesting side project in my spare time, \ and it has reached a stage where I think it's worth showing to the SAS world at \ large. It's called Wolfensas; yes, it's a game, and the name is a complete giveaway! It's \ even multi-player over a network. It has been developed in and for SAS 8.2 under \ WinXP, although it should work fine with newer versions of both. Based on the popular first-person shooter game Wolfenstein 3D, it's fair to say that this SAS application pushed the boundaries of SAS in new ways. Here's a screenshot provided by Mark: The game assets include over 5,000 lines of SAS code over 14 files, plus dozens of graphics and sound files. The SAS code has fun-sounding macro routines such as %addwallsmoke and %drawprojectiletracers. It would take me a long time of studying this code to understand it, but it's fun to look through and admire the effort. Wolfensas project code Running Wolfensäs today Recently I installed SAS for Windows on a new machine, but I accidentally selected the 32-bit version of SAS instead of the 64-bit version. Realizing my mistake, it occurred to me that this gave me the unexpected opportunity to test whether the game still works 15 years later using SAS 9.4 on Windows 11. See the results for yourself: Ironically, the graphics don't look quite as good on my modern machine with a 16:9 screen ratio and high resolution, but the mechanics still work (and the sound too!). As of this writing the code for Mark's game is still available on his website, http://wolfensas.subshock.net/. The instructions are clear and easy to follow; however, I suspect that very few of today's SAS users will be able to run it. The game code has many architecture-specific elements, including direct access into application memory using CALL POKE and some system calls via CALL MODULEN. These techniques were coded to work only in the 32-bit version of SAS on Windows. Most SAS for Windows users today are running 64-bit SAS. (And if you're using SAS Studio or SAS Enterprise Guide...well, that's a non-starter. The game relies completely on the SAS windowing interface, available only with a local install of SAS.)

ChrisHemedinger

I wonder if "proactively added" is code for "we wrote a Python script". Instead of "we automated Excel to open and alter the file in a supported way."

ChrisHemedinger

If you don't mind watching a little video, this segment covers how EG Import Data works and how you can control it.

ChrisHemedinger

Actually, in reviewing the original error I think you should try adding the FROM= option to your code. See How to send email using SAS for simple examples.

ChrisHemedinger

This might depend on your email server setup and authentication. If you have single-signon or two-factor authentication (common in cloud-based email), then a simple password might not be enough to authenticate. See tips here (specific to Gmail) and see if you need to adapt accordingly.

ChrisHemedinger

I added a link from that older topic back to here for those who need it.

ChrisHemedinger

A-ha, I see that the keyboard method for moving this window in SAS 9.4 is interrupted by another interaction. Well, in that case, let's just delete the "memory" of that window location. Close SAS application, then in a command prompt window try: reg delete "HKEY_CURRENT_USER\SOFTWARE\SAS Institute Inc.\Enhanced Editor\9.4\Search History" This deletes a key that affects just your preferences/history for the Find window, not anything to do with the core application.

ChrisHemedinger

See if this topic helps: SAS EG - lost search window

ChrisHemedinger

@bnawrocki Libraries/data set viewing is not yet supported for local connections but it is being worked on! The output theme is tied to ODS styles. The extension will try to match an ODS style to your editor theme, but of course it's not 1-to-1 and you can override by adjusting your ODS HTML5 statement to include the style= value of your choice.

ChrisHemedinger

See the documentation for the XML libname engine. If you assign your PROC HTTP output to resp, then this should work: libname resp xmlv2; proc datasets lib=resp; quit;

ChrisHemedinger

If this is indeed a sample of the response, it's XML content. You can use the XML libname engine to view this as data. Try this to get started: libname data XMLv2 resp; proc datasets lib=data; quit;

ChrisHemedinger

Lex, I don't know this for certain but I suspect Python is not generally available for SAS code in this environment. With over a quarter million active users, the SAS OnDemand for Academics environment has to limit the ability to call out to external processes, including things like Python. In an environment where you had some control, you could set these environment variables in your SAS program to known values: options set=MAS_PYPATH="path-to-python" set=MAS_M2PATH="your-sas-root/SASFoundation/9.4/misc/tkmas/mas2py.py"; But then you would also need to be able to install (or ask for) the Python packages you need. numpy, pandas, etc are likely not in a vanilla environment, so an admin needs to make those packages available in order for you to do anything useful. Given the governance needed for SAS OnDemand for Academics, I'm thinking these use cases are out of scope.

ChrisHemedinger · ‎11-07-2023

I recommend looking at PROC JSON to see if it can create the simple JSON you need. Good reference in this paper. Also, you can "validate" the JSON you create by using the JSONPP function (JSON pretty print). See more in Using JSON Data With SAS .

ChrisHemedinger · ‎10-26-2023

@Quentin Good questions and requests. The best way to get the attention of the developers is to add a GitHub issue on the project. It's very active there.

Online Status	Online
Date Last Visited	7 hours ago