I get the same effective maximum (~2.5MB).  I do get a warning, saying that my maximum (2g) is higher than the allowable limit (around 1g).  Do you get the same?  That's with a memsize of 6g, which doesn't surprise me - from other evidence I can see that SQL uses around 5x as much space (1g * 5) as it needs. ... View more

Thanks! ... View more

Hi, nohup writes an output file, nohup.out, do you have the input SAS-files in one folder? Your Solaris-admin should be able to tell you the reason of the locks. (prstat -mL, plockstat, mount options) In the command line, together with the input file (-sysin), -noterminal, -nonews I would define logfiles (-log) and outputfiles (-print) , too. SAS Help: Optimizing SAS I/O can give you some hints, too. ... View more

Thanks to all of you Helped us a lot. ... View more

@emsmpa. Your logical requirements are not clear, please describe them. For the major approach Eguide Metadataserver Objectspawner etc. is not making any use of SSH actually SAS is replacing that by their own approach. Passwordless SSH is known at SAS, They are using it with a clustered SAS-VA environment to fulfill synchronization of the OS-layer for several accounts that can be high priviledged or having a dedicated role as data-administrator.  The high-level security awareness of SAS is not aligned to common used approaches. SSH is one of those, SSH does everal things. - If you need encryption over the wire the SAS replacement is coming with SAS/Secure. - If you need to eliminate passwords as common requirement with high priviledged accoutns there is challenge. SAS is putting every users/passwords in files/databases.   As you are using Unix you could try to replace the involved scripts using sudo. - Eguide is not really positioned for automated usage as it main usage is interactive.   It has the option to have let stored the password (hashed) in the user-profile environment. That is close to the ssh public key approach.   It has the option to have stored external connection user/passwords in a local file (credentials.xml)  30917 - Scheduling projects in SAS® Enterprise Guide® this option only is applicable when doing scheduling.  For normal users you will close down this option as scheduling is focussed to be done central. Never now if you want to use this in your situation.         @sagarthalwar. Building a .Net application is not building a WEB application, they are different. When you build something that way you are building a Eguide verion on your own,  Eguide is a .Net application. There are functions within Windows to get the credentials. Chris give that hint and it could become tricky Five strategies to eliminate passwords from your SAS programs - The SAS Dummy. When you are needing encryption over the wire or a automatic login you could solve that in the same way Eguide does.  ... View more