10-05-2017 08:38 PM
I suspect this behaviour is due to your SASUSER library being set to read-only so customisations can't be saved.
To confirm if this is the case run: PROC OPTIONS and check if the RSASUSER option is set.
10-05-2017 09:08 PM
Look at the message in the log, right behind your pop up. When you make this change make sure it's in the only SAS instance running so the options can be saved.
10-05-2017 10:11 PM
The option to disable may have been applied to your original (first sas session). Any new session, sas will revert to default. And log says something about your settings too.
10-05-2017 10:28 PM
I probably should have updated in detail how I get this pop-up screen. This screen is disabled in my initial screen when I start SAS for the first time but when another SAS session is triggered ( e.g. when a local SAS ODBC connection is invoked), then I get this pop-up screen on my second SAS session.
10-05-2017 11:00 PM
This is a "feature" of opening a second SAS Windowing Environment session. Your first session has locked the SASUSER.PROFILE catalog where your preference is stored, so the second session is unable to open it.
If you started BOTH of your sessions with the -RSASUSER option I think it will disable the pop-up. You could test this from the Windows Run box by running SAS -RSASUSER twice.
10-06-2017 12:23 AM
I used that option on my startup sas but it did not work. My code starts up a separate SAS session for an ODBC connection as it's refreshing a pivot table from a SAS table and that SAS session still has the pop-up.
If I run multiple SAS sessions on my PC, it does not show the pop-up for each session.
10-06-2017 02:49 AM
- Start a SAS session with norsasuser
- disable the popup
- close the SAS session
- change the option in the configuration to rsasuser
After that, all concurrent SAS sessions should have read access to your sasuser.profile and respect the setting.
10-08-2017 07:39 PM
I tried your suggestion but it still shows the pop-up screen only when the main sas session triggers another SAS screen e.g. the ODBC connect session.
Need further help from the community? Please ask a new question.