SAS Management Console may appear to be in a wait state or may appear to
hang as a result of being out of memory.  An out of memory error will be
written by the Java Virtual Machine to the SAS Management Console
errorlog.txt file located in your user profile directory.

To circumvent the problem, set the maximum memory allocation for the
JAVA Virtual Machine using the JVM argument:  -Xmx512m in the SASMC
scripts.

On Windows add -Xmx512m to the CommandLineArgs= in the SASMC.INI file
located in C:\Program Files\SAS\SASManagementConsole\9.1.


For example:

    CommandLineArgs=-Xmx512m
   -Djava.system.class.loader=com.sas.app.AppClassLoader
   -Dsas.app.class.dirs="C:\Program Files\SAS\SASManagementConsole\9.1"
   -Dsas.app.class.path=sas.smc.jar;. -cp sas.launcher.jar
   -Djava.security.auth.login.config=security/login.config
   -Djava.security.auth.policy=security/auth.policy
   -Dcache.auth.policy=true com.sas.console.visuals.MainConsole


On UNIX, add the same JVM argument to the SASMC script file located in
the !SASROOT directory.  The argument can be added to
$CommandToExecute.

For example:

   exec $CommandToExecute -Xmx512m $CommandLineArgs "$@"


Note: The CommandLineArgs options must be on the same line in the
SASMC.ini file.  Line breaks will cause SAS Mangement Console to fail.

Operating System and Release Information