How are you verifying that UserB can access DirA? ... View more

The only reason UserB should be able to access DirA, with the permissions as they are, is because UserB is in GrpA. You need to check the groups of UserB. If you issue "groups UserB" is GrpA in the list? ... View more

Can you show me current permissions for DirA and then issue the following commands send me the ouput? id UserA id UserB ... View more

If I understand you correctly, I think it would be something like the following. You need to have the Linux groups created (GrpA/GrpB) and then have each user added to their respective group (presumably their GID, primary group, would be either GrpA or GrpB). Then you need to create DirA and DirB and change the group ownership of the DirA and DirB to GrpA and GrpB. So something like: "chgrp GrpA /DirA" So long as the user is a member of the appropriate group and the directory has execute permissions for the group that owns it they should have access to those directories. ... View more

Excellent! Glad you got it fixed. ... View more

Can you verify that the Oracle database supports utf-8? Also, can you create a test dataset with the value you're trying to insert? If it looks correct in the SAS datasets but not the Oracle database, I would assume that the Oracle database needs to be configured to support utf-8 encoding as well, ... View more

Here's the SAS documentation regarding session encoding and how to change it:   http://support.sas.com/kb/51/586.html   Alternativley, you should be able to just add a parameter to the sasv9_local.cfg file in <sashome>/SASFoundation/9.4.   You would add an option in this file. It should look something like this:  -ENCODING utf-8   In my environment, we originally configured as utf-8, but then I realized that alot of people that would be migrating from old servers to the new servers had all of their datasets encoded with latin1. So we added "-ENDODING utf-8" to the sasv9_local.cfg file.   ... View more

It looks like your workspace server is configured for LATIN1, not UTF-8. UTF-8 can accommodate most non-Roman characters, as it looks like you're doing. You should be able to override the default locale in you config file. I will give you more details once I am able to log into work. ... View more

It looks like there is an issue with your Oracle client. Is the Oracle client installed on the SAS server? If so, was it recently changed? Do you have SAS/Access to Oracle licensed? When did your Oracle connections last work? Can you show what's in your sasenv_local file? ... View more

Sounds good. You could test by shutting down Object Spawner on node 1 and then see if you can still connect to the app server through EG. ... View more

My pleasure. Good luck! ... View more

Yea, I'm not sure there is any way to sync the two without either having some third-party software that does it or just using alternate authentication method. The whole point of such alternate methods is to bypass having to manage the local /etc/passwd. Setting up PAM is pretty easy. The SAS documentation is very precise. If you have a Test environment then it might be worth reading over the SAS documentation and testing it out. Sorry I can't be of more help. ... View more