Yes, problem was solved only after our UNIX administator has configured /etc/pam.d/sasauth as above (I'm only SAS administrator, so PAM was configured by our UNIX administrators, and I posted above their solution as they answered to my request). ... View more

Here PAM it is a "Pluggable Authentication Modules", not Portfolio asses management PAM should be configurated on your SAS server. It haven't any special relations or connections to SAS, only profile for SAS servise, it used only to authenticate user, because sas programs on Application server are run (and EM projects are stored) under your unix user on sas server , and this user must be defined in your sas user profile (you can edit them in Management Console). PAM settings are storing in /etc/pam.d file. For SAS you can create special settings using servise name option, for example sasauth: etc/pam.d/sasauth Then you should define module types for this service (sasauth) - there are "account", "password" and "session" For each of module types control flag shoul be setted: " requisite" , " required" , " sufficient", " optional" or "Include" (a link to other PAM servise_name, usually - system-auth, a common user authentification) Next option - Module_path (if it's special) Then - may be some othr options So, PAM module can be similar to this: in file /etc/pam.d/sasauth auth    include system-auth account include system-auth password        include system-auth session optional        pam_mkhomedir.so skel=/etc/skel umask=0022 In any case your UNIX administrator should knew. About PAM accounting journals - I don't know about it, unfortunately. If you a telling not about authentification modules, but only about "Portfolio asses management" - what is it (a realisation) - some database? It's another topic, and, i think, related with the connection of SAS to DB, where portfolio asses data stored - Oracle, Teradata, DB2 or something other. ... View more

Autosys - something like advanced scheduler To use it on UNIX a special agent should be installed on server (with separate license) It can easily run some commands in UNIX shell to run sas programs and also to get sas exit code (successfull or not) In sas code you should (if it for EM projects, project must be created before): - directly set the project name of EM project, project folder, name of workspace (to update an existing EMWS, or it will create new each time) - directly assign each library (even pre-assigned) Then, you can face with encoding problem - if encoding of sas in bathch mode is not equal to one's used in project - it solves by setting the encoding in config file, config must be declared in command line To get  sas exit code you can use $? statement. It looks like this ./sas -noterminal -nonews full_name_of_your_program.sas -log full_name_of_log_file.txt -config full_name_of_config_file.cfg (Log file must be created before) echo $? > full_name_of_result_file.txt (this file for sas exit code, file must be created before) Autosys have to run this commands, and then to read result from result_file.txt Result codes are here: http://support.sas.com/documentation/cdl/en/hostunx/63053/HTML/default/viewer.htm#p0h28whoxxvtztn15wqqvv9o41py.htm ... View more

Overall - the problem causes because of incorrect configuration of PAM module on Unix server It should include "session" option - something like this: PAM module in  /etc/pam.d/sasauth auth    include system-auth account include system-auth password        include system-auth session optional        pam_mkhomedir.so skel=/etc/skel umask=0022 Because of incorrect configuration of PAM you may face with such errors: - anybody can login without password (if "password" option is missing) - user hasn't home directory - situation that described in the topic - if "session" option is missing ... View more

I also have faced with such a problem. The reason was with rights of user on the Unix server - there were no user's folder at home directory with configuration files, usually it is generated at the user's first  login to server. We just ask user to login to server via PuTTy once and problem was fixed ... View more