Thank you for your help.   I checked all environment setup files in etc and, as I thought, there was nothing since it's a server shared among 5 groups and the policy is to define everything locally. I used the command you suggested and it revealed the ins users were the ones responsible for calling the object spawner as I supposed at the beginning looking at the PATH values. So I'm now 90% sure I have to edit those files, which is a thing I can't do by myself because of authorization issues and I will unfortunately know only in 3-4 weeks if it's right (still, I have to provide authorized people, who know nothing about what I'm doing, with locations and new versions of the files to be edited... smart policy).   There's still however one thing that bugs me. That missing 10% is due to the fact that the whoami command from SAS EG returned srv users instead of ins ones, under every login user I tried, even the same ins ones. Why? ... View more

I'm a bit confused now.   First of all, along with the "echo $PATH" command, I passed to pipe "whoami" and the answers corresponded to what I expected (srv users). Moreover, I tried to log on SAS EG with different users and I still got the same result, so my educated guess is that the users that run the object spawners are the one whose profile I've looked at.   Second, there is no difference, at least for what concerns me, in environment setup between the two servers (at least this is what appears to my very limited knowledge of Linux). On the server B, the one working, the srv user .profile file doesn't set any environment variable which comes into play. All the setup for SAS is done in bash_profile. On the other server, the .profile file does nothing and a limited amount of setup, the one not showing up in PATH from SAS EG, is done in bash_profile.   Third, to confuse me even more, both PATH include the home of a different standard sas user (ins), and this is nowhere to be found even on server B. This suggest me I'm clearly not looking at the right configuration files. ... View more

Thank you. I sneaked in the bad string again when nobody was working on that server and tested what you said. I got the same error message this colleague of mine mailed me. ... View more