About PaulHomes

PaulHomes · ‎11-13-2015

I also meant to ask you which version of SAS are you using? 9.4, 9.3, 9.2, 9.1?

PaulHomes · ‎11-13-2015

Hi Doriana, I can think of 2 possibilities: 1) Are you logged in as an unrestricted admin or a restricted user admin? If you don't see "user@domain as Unrestricted" on the SAS MC status bar it is possible that the read-only user has been protected fromrestricted admin modification through a denial of WM to the PUBLIC group on the users Authorization tab. 2) Are you trying to modify the user through a read-only dialog? For example if you use the SAS MC User Manager plug-in to look at the members of a role, select a user and then click the Properties button a read-only dialog will be displayed for that user (even if you have permissions to modify the user). If you open the Properties dialog for the user directly from the SAS MC User Manager plug-in then you should be able to make changes if you have permissions to do so. I hope this helps. Cheers Paul

PaulHomes · ‎09-12-2015

It had to happen - shortly after posting the above I got a 404 again - so clearing the old cookies was only a temporary solution.

PaulHomes · ‎09-12-2015

Hi Tom, This is how I see SAS Communities via the NewsBlur web site - just quick snippets (title and part of the first line) of unread posts. If I see some thing I'd like to read I click on it and see the full text. If I have something to contribute I can then click on the URL to go to the site itself. I like this view because I get the same consistent experience across a large number of sites/blogs/forums (currently 88 sites). I find RSS readers (the few that don't try to emulate a magazine experience) provide a great format for scanning lots of posts in a short amount of time. I discovered this particular RSS reader after trying a bunch of different ones when Google Reader was shutdown (and have been a very happy customer since). RSS is not for everyone, but I'd be lost without it - having to visit individual sites to get news is too inefficient for me. Cheers Paul

PaulHomes · ‎09-12-2015

I used to get 404's all the time after my session expired. After the move from lithium.com to communities.sas.com I got it once more. At that time I deleted just my sas.com cookies (Control-Shift-I > Resources > Cookies in Chrome) and I haven't seen the 404 since. I'm not saying that's the answer but it seemed to work for me (it could be a coincidence - I haven't tried to repeat it to test it).

PaulHomes · ‎09-09-2015

As Bruno suggested earlier in this thread, RSS provides one possible solution to reviewing all activity regardless of forum. I have been testing some of the communities RSS URLs over the past couple of days and, so far, it seems that the following RSS URL provides all activity across all forums including replies and ideas etc. https://communities.sas.com/kntur85557/rss/Community?feeds.replies=true&count=30 Thanks to Lainie, in one of my previous questions, the count parameter allows some control on the number of items fetched each time. BTW I use NewsBlur as my RSS reader - I like it because it show lots of information in a single view (no excessive use of white space) and it allows me to access it, and maintain the state of what I have and haven't read, across which ever device I have to hand - desktop browser(s), iPad and iPhone etc.

PaulHomes · ‎09-04-2015

Hi Quentin, DI Studio seems to recycle workspace servers more than EG. When I teach SAS platform admin I often show students SAS workspace server processes launching based on SAS client activity (like EG, DI etc). From memory, when you open a table in DI it launches a workspace server process as a conduit to the data. When you close the table the workspace server process is shutdown. Similarly when you open a job and run it, a new workspace server process is used for that job. When you close the job the workspace server process is shutdown. You might want to confirm this using a process viewer on the server (like Process Explorer on Windows) or the Server Manager plug-in in SAS Management Console. So I would suggest a way to force a new workspace server in DI (without restarting DI) is to close and re-open the job. Cheers Paul

PaulHomes · ‎08-22-2015

The <logger name="App.Program"> you posted has a minus sign instead of an equals sign. Additionally it contains an <appender-ref ref="file" />, but you have no <appender> tag with a name="file". You need to either change the ref="file" to point to an existing appender by its name, or add a new <appender> block with name="file".

PaulHomes · ‎08-18-2015

You might be interested in reviewing the responses to the question where posted a logconfig.xml to capture this information.

PaulHomes · ‎08-12-2015

I haven't tried it yet with Unchallenged Portal Access in the SAS Information Delivery Portal, but I did do something similar with SAS VA and described it in a blog post SAS Visual Analytics Guest Access with IWA Fallback (that post has links to other related posts, papers and docs too). I don't know if it will work with IDP, but this is the approach I would follow if I wanted to test it out. I had read in the SAS docs that web authentication was not compatible with anonymous access, but fallback authentication (as described in a very useful paper by Zhiyong Li and Mike Roda from SAS) seems to offer up additional possibilities.

PaulHomes · ‎08-12-2015

That error can indicate a problem with the logconfig.xml file (as pointed to by the logconfigloc system option in sasv9.cfg). I would open the logconfig.xml in Internet Explorer or a good XML editor to make sure it is well-formed and there are no obvious errors. Then check all the references to directory paths and files are valid. Check any available SAS log files for further clues (there is often a fail-safe log created somewhere when the logging facility fails). If that doesn't help, you may want to consider contacting SAS Professional Services or a SAS partner in your local area to see if they can provide some expertise for your project.

PaulHomes · ‎08-08-2015

There is an API available to write a DI Studio version control plug-in, but I'm not aware of anyone who has written one for git (perhaps someone else knows?). See the Prerequisites for Version Control section in the SAS Data Integration Studio 4.9: User's Guide: If you want to use a version control server other than a CVS server or an SVN server, you must create a custom plug-in for that server. There is a documented application programming interface (API) to integrate other versioning systems with SAS Data Integration Studio. See this API documentation at http://support.sas.com/rnd/gendoc/versioncontrol/43/en/. Keep in mind that SAS Data Integration Studio uses only the first plug-in that it finds in the installation path. You must either name your custom plug-in a name that can be found before all other plug-ins, or you must remove other plug-ins from the installation path. If you want integration within DI Studio this would be the way to go, but it is non-trivial (although SAS do provide sample code for SVN and CVS to help you get started). A simple (non-integrated) method would be to export SPK files from DI studio and check those into a git repository from the command line (or TortoiseGit on Windows).

PaulHomes · ‎07-02-2015

Another technique that avoid parsing the single value sysparm system option, at least on Windows and UNIX/Linux, is to use multiple -set command line options and get the values with %sysget Here's an example. The progrtest.sas has: %put %sysget(parm1); %put %sysget(parm2); ... then run it with: sas -set parm1 value1 -set parm2 "value2 has spaces" test.sas;

PaulHomes · ‎07-02-2015

If you configure it for the workspace server it will be effective for all users of that workspace server (i.e. EG and other metadata driven client/web apps that use that workspace server configuration). Anyone who runs SAS code by other mechanisms like non-metadata driven SAS batch jobs, DIsplay Manager etc will not get logged unless you can change the SAS config file used by those other mechanisms too.

PaulHomes · ‎06-26-2015

Yes, it needs to be pre-configured in an XML logging configuration file. If required, the standard platform logging configuration can be modified. As the logging config is a Base SAS feature, even old-style, non-metadata driven, batch SAS programs or DMS can have their logging configured this way too - assuming the appropriate sasv9.cfg has a logconfigloc option set. Of course, if someone has access to a command line, or permissions to modify configuration files or server metadata, they could attempt to access the data and bypass the audit logging. For SAS datasets that might require more control, it could be worth considering audit logging with mediated data access or metadata bound libraries and encrypted tables (and limiting the ability to launch SAS sessions with custom configuration).

Online Status	Offline
Date Last Visited	‎02-11-2025 08:08 PM