I don't recall seeing any documentation on what can be saved and how. That ought to be documented somewhere, perhaps in a user group paper or perhaps by Tech Support. If you have a session open and RSASUSER isn't set, you can save some settings with the WSAVE ALL command. The documentation says only "saves all command settings that can be saved with the WSAVE command in all currently open windows." Not very helpful - I certainly wouldn't expect it to save settings that can't be saved. The settings it can save are generally (probably not always) settable by SAS commands (as opposed to statements) , and commands are documented under base SAS and also in the SAS Companion for your operating system. If there's a Display Manager setting I always want, and WSAVE doesn't save it, I put it in my sasauto.sas program, e.g. dm 'log; zoom on; autopop on;' log; ... View more

The profile (which is actually several different files) is located in the directory specified by the SASUSER system option; see the results from the PROC OPTIONS you ran earlier.  There are three .sas7bcat files whose names start with "prof".  Close SAS, rename those files so SAS won't find them, and start SAS back up.  You may have to open and close SAS and open and close some program files to build up a file history.  You might also need to rename the regstry.sas7bcat file. This documentation is from 9.2 but I think it's all still valid: https://support.sas.com/documentation/cdl/en/lrcon/62955/HTML/default/viewer.htm#a001050172.htm   ... View more

I was hoping there were non-default settings. Another possibility is that your profile has simply gotten corrupted somehow, and you can fix that by just deleting it and letting SAS generate a new one. You'd lose your current settings. Are you by any chance running two SAS sessions at once? ... View more

Perhaps RSASUSER is set, or SASUSER is not writable. What do you see with this? proc options option=(sasuser rsasuser); run; ... View more

It would be interesting to see the geographical distribution of the participants.  Judging by the hour, your target audience in not in the Pacific Rim, but in Europe (4pm Paris, 7am California, 4am Honolulu, 10pm Singapore and Beijing). ... View more

It sounds like a default file permission is being set wrong somewhere.   But really, you left out a lot of information that might be helpful:   - What operating system is the desktop? - What operating system is the server? - What file sharing protocol is being used? - What program is being used to save files?  SAS for Windows?  SAS Enterprise Guide, SAS Studio?  An external editor? - Does it affect only SAS program files, or other kinds of files as well? - Does it affect all users, or only some? ... View more

The SAS Bowls at SUGI were organized by the SAS-L BOF committee.  SAS-L was at the time the world's largest SAS user group outside of SUGI itself.   I was on the committee and helped review the questions, so I never participated.  Also like so many things at user group meetings, it always managed to be held at the same time as something else that was higher on my priority list.    From what I hear, the Bowl started getting risque after a few years.  A SAS employee came by and noticed the off-color nature of the proceedings, and that was that - no more SAS Bowls.  It might have been revived later in a different format.    Here's a trivia question for you: What base SAS statement is not ended by a semicolon?  (Hint: It's a legacy statement, not in the current documentation.)  Bonus question:  What current SAS product uses this statement?   ... View more

This is not the first "SAS Bowl".   There have been at least two at PharmaSUG, at least two at SUGI, and at least one at NESUG and MWSUG.  It might be the first one run by SAS Institute instead of SAS users. ... View more

The Statistical Analysis System's roots in agriculture are mostly unknown nowadays.  It would be interesting to see a presentation on SAS's use in Ag now vs. then.  Is there a completely different set of users, perhaps different crops or different farm sizes?   Graphics are much better now, and there's much more variety and power in modeling procedures, but I think box plots have been around for a long time. ... View more

You also put fmtsearch in your autoexec.sas. You can set Windows environment variables to specify either an autoexec.sas or sasv9,cfg file without needing to write into a protected directory. You probably have access to user environment variables even if you don't have admin rights. See: https://www.mwsug.org/proceedings/2018/SP/MWSUG-2018-SP-100.pdf https://documentation.sas.com/?docsetId=hostwin&docsetTarget=p0bmj7wjme32ayn1h4wim7trkhp6.htm&docsetVersion=9.4&locale=en#p1f8pahglb6jz0n18i9bd3xxl84r The logic SAS uses to find configuration files in Windows is complicated, and I find setting SAS_USER_CONFIG and SAS_OPTIONS to be the easiest to understand. ... View more