commands and windows are available through the GUI. In some cases, you select
operations through dialog boxes and various other GUI controls.
SAS launches Java using the Java Runtime Environment (JRE) so that it can run Java
code. Parts of SAS are written in Java. The JRE contains the libraries that are needed to
In SAS 9.3, the ODS graphics procedures moved from SAS/GRAPH to Base SAS.
These procedures that rely on Java are delivered as part of Base SAS, rather than as a
separate SAS product. As a result, a key difference in the SAS 9.4 windowing
environment is that SAS now initializes the Java environment upon SAS invocation.
HTML is now the default output for SAS 9.4 Windowing environment, replacing the
listing destination. The default style has changed from Styles.Default to
Styles.HTMLBlue for the default HTML ODS destination that is generated with the SAS
windowing environment and in batch mode.
Java is implemented as a part of Base SAS in SAS 9.4 because the Graph Template
Language and the SAS/GRAPH procedures such as SGPLOT, SGPANNEL,
SGSCATTER, and SGRENDER have moved to Base SAS from the SAS/GRAPH
procedures. By default, the ODS GRAPHICS statement is set to ON for SAS procedures
that support ODS Graphics when the procedures are executed in the SAS windowing
environment in the Windows and UNIX operating systems. Although ODS Graphics are
enabled for these procedures, you might want to use the ODS GRAPHICS statement to
control the graphical environment.
When you use the Windowing environment of SAS (interactive SAS) in SAS 9.4, you
might encounter error messages similar to the following in the SAS Log window when
you run programs (for example: PROC javainfo; run;):
ERROR: Unable to attach current thread"
ERROR: Unable to load the java virtual machine"
ERROR: Proc javainfo did not run correctly
ERROR: The Java proxy is not responding.
ERROR: The Java proxy's JNI call to start the VM failed.
ERROR: Java failed to start during the SAS startup.
These errors are typically related to issues with the Java Runtime Environment (JRE). To
resolve these issues, follow these steps: http://support.sas.com/kb/48/548.html
Use SAS Interactively or in Batch Mode
When running SAS under Windows, you can start an interactive session to submit
programs and view the resulting output, or you can execute batch SAS jobs, and view
the output later.
By default, invoking SAS begins an interactive SAS session. If you have a SAS program
that you want to submit as a batch job, specify the SYSIN system option with the name
of the SAS program file when you invoke SAS.
When you start SAS in an interactive session for the first time, you are asked if you want
to learn some basic tasks by taking the Getting Started Tutorial. To start the tutorial,