Some features of SAS^®9 software use Java, and your installation must be configured correctly to be able to use Java successfully. If SAS has not been configured correctly, you will see one of the following messages in your SAS log:

ERROR: Could not create Java VM.

ERROR: proc javainfo did not run correctly

If you submit code from SAS^® Enterprise Guide^® or SAS^® Information Map Studio to a z/OS server tier, you might see an error similar to the following in your SAS Enterprise Guide log:

The SAS MVA interface to the Java API could not be initialized.

There are several files and option settings that contribute to configuring SAS to use Java:

• Available memory—Under z/OS, your job or your UNIX System Services (USS) session requires at least 512 MB of memory to run. In a batch job or TSO session, this is controlled by the REGION parameter. In a USS session (such as a spawned workspace server), the user ID must have ASSIZEMAX set to a minimum of 536870912 (512 MB). For a stored-process session, the user ID that is associated with the stored-process server must have an ASSIZEMAX value of at least 512 MB.



• Contents of your TKMVSENV file—The location of Java and other required settings are located in the files that are allocated to the TKMVSENV DD name.



• Other Java options—The JREOPTIONS SAS system option in your SAS configuration file includes many other Java options required for SAS to run successfully.

If you receive one of the errors above, here is a step-by-step debugging guide. Save the logs from any test code that you execute, because if you need assistance from SAS Technical Support they will provide valuable information about your Java configuration.

1. Ensure that the steps referenced in the section "Configuring SAS Software for Use with the Java Platform" of the Configuration Guide for SAS^® 9.1.3 Foundation for z/OS^® were performed.



2. Double-check all options in the JREOPTIONS string in your SAS configuration file to make sure there are no typographical errors, that everything was entered in the proper case, and that all UNIX System Services path names and files exist as entered. Note that the options are case-sensitive and must be entered exactly as shown in the documentation, although path names will vary at each site. Also remember that the string must break exactly at column 72 (with no blanks in column 72) and be continued in the first column of the next line.



3. SAS uses the TKMVSENV data set to provide values that would otherwise be stored in environment variables. Verify that the location of the directories and files specified in the PDS members, TKMVSENV and AJPROXY, stored in the prefix.TKMVSENV installation data set exist and are properly set.
   
   Note: Unlike the JREOPTIONS settings, entries must set the options on each line without any continuations.
   A colon (:) is used as the delimiter on each line to denote multiple directories or files.

   At a minimum, you should have the following options in your TKMVSENV file (path names will vary by site):

       set TKJNI_OPT_PROXYPATH=/usr/lpp/SAS/SAS_9.1/BI/jproxy
       set TKJNI_OPT_LEOPTS='XPLINK(ON)'
       set TKJNI_OPT_LIBPATH=/java/bin/classic:/java/bin
       set TKJNI_OPT_DISPLAY='xservermachine:0'
       

   Note: Be very careful about using the statement RESET in any file concatenated in the TKMVSENV dd name, because if it is not the first line in the concatenated files, it might nullify prior statements and cause unexpected results!

4. Depending on whether you are executing your code from a batch job, TSO session or client such as SAS^® Data Integration Studio or SAS Enterprise Guide, you might be using different memory or options settings. Test by running the following code from the environment where you are receiving the error to check all of these settings.

   * Display value of MEMSIZE and how it was set ; PROC OPTIONS OPTION=MEMSIZE VALUE DEFINE; RUN; * Display available memory and is it enough? ; %let memory = %sysfunc(getoption(memsize)); data _null_; x=&memory; put '*** AVAILABLE MEMORY IS: ' x comma19.0 ' *** ' @ ; if x < 512 * 1024 * 1024 then put / '*** INSUFFICIENT MEMORY ***' ; else put / ' AVAILABLE MEMORY IS GREATER OR EQUAL TO 512M. ' / ' MEMORY IS SUFFICIENT'; run; * Display value of JREOPTIONS ; PROC OPTIONS OPTION=JREOPTIONS VALUE DEFINE; RUN; * Display the entire CONFIG DDname in the SAS log. ; * This helps check the alignment of the lines. ; DATA _NULL_; INFILE CONFIG; INPUT; LIST; RUN; * Display the contents of the TKMVSENV DDname in the SAS log. ; DATA _NULL_; INFILE TKMVSENV; INPUT; LIST; RUN; * Try to create a java VM ; PROC JAVAINFO; RUN;

5. If you still cannot successfully create a Java virtual machine, you can enable some additional debugging.

   Important: Make sure you have a working backup and a copy of your SAS configuration and TKMVSENV files before making the modifications described below. You will need to revert to your original copies of these files once the optional data step and %RMVINST macro are run.

   1. Insert the value -verbose at the end of the JREOPTIONS SAS System option

      Update your configuration file by inserting the value -verbose at the end of the JREOPTIONS SAS system option. You might need to realign the JREOPTIONS value string. As when you coded these values originally, keep in mind that no part of the JREOPTIONS value string can go beyond column 72; that there must be a non-blank character in column 72; that continuations must start in column 1 of the next line; and that method must be continued for as many lines as needed.

   2. Set tracing environment variables in TKMVSENV

      Add the following statements to the TKMVSENV member of the &prefix.TKMVSENV data set. Note: The values for the physical paths and file names used for these environment variables shown below are set for illustration purposes.

           set TKJNI_OPT_TRACE=y asis
           set TKJNI_OPT_TRACEOUT=/tmp/trace.log asis
           set TKJNI_OPT_STDOUT=/tmp/stdout.txt asis
           set TKJNI_OPT_STDERR=/tmp/java.err asis
           

   With the -verbose value added to the JREOPTIONS setting, you might get additional files created in your home directory named tkjni.err and tkjni.out that will have additional messages from the attempt to start Java. The file paths set in TKMSVENV tracing options will determine where the trace files will be written. You can browse all of these files with SPF, or read them by submitting the following code:

   PROC JAVAINFO; RUN; * Display TKJNI.ERR and TKJNI.OUT files on the SAS log; FILENAME CMD pipe "pwd; cat tkjni.err;cat tkjni.out"; DATA _NULL_; INFILE CMD LENGTH=LEN END=LAST; LENGTH LINE $2000.; INPUT LINE $VARYING2000. LEN; PUT _INFILE_; RUN; * Display TRACE.LOG, STDOUT.TXT, JAVA.ERR files on the SAS log; FILENAME CMD pipe "cd /tmp; pwd; cat trace.log; cat stdout.txt; cat java.err"; DATA _NULL_; INFILE CMD LENGTH=LEN END=LAST; LENGTH LINE $2000.; INPUT LINE $VARYING2000. LEN; PUT _INFILE_; RUN;

   Note: Be sure to revert back to the original SAS configuration and TKMVSENV files that do not have the -verbose option and trace environment variables, once you have a chance to review the files generated.

6. SAS^® IT Resource Management 3.1.1 sites might consider executing the code below, which tests specifically whether SAS has been configured to access the additional ITRM Java classes. If you have not applied hot fix 311IS03, you might receive the warning :
   WARNING: Apparent invocation of macro RMVINST not resolved.

   *PROVIDES INFORMATION ABOUT ITMSCORE DIR AND OMIL JAR FILE; *VERIFY LOCATION OF itmscore DIRECTORY; FILENAME CMD pipe "pwd; cd /usr/lpp/SAS/SAS_9.1/USERID.ITRMW0/itmscore; pwd; ls -l; jar -tvf sas.solutions.itms.omil.jar"; DATA _NULL_; INFILE CMD LENGTH=LEN END=LAST; LENGTH LINE $2000.; INPUT LINE $VARYING2000. LEN; PUT _INFILE_; RUN; *DATA STEP TESTJAV TESTS ACCESS TO JAVA OBJECTS; *NOTE: IF TESTJAV FAILS, PLEASE COMMENT TO ENSURE; *EXECUTION OF MACRO RMVINST; DATA TESTJAV; *Make sure we can load a basic java object; DCL JAVAOBJ STRING("java/lang/String"); *Make sure we can load anything from sas.core.jar; DCL JAVAOBJ LOADER("com/sas/RB"); * Now try the FoundationDispatcher; DCL JAVAOBJ DISPATCH("com/sas/solutions/itms/omil/FoundationDispatcher"); RUN; * SAS IT Resource Management sites should uncomment this macro RMVINST, * invocation only if hot fix 311IS03 has been applied; %*RMVINST; * SAS IT Resource Management sites should uncomment this macro RMVINST, * invocation only if hot fix 311IS04 has been applied; %*RMVINST( metaserver=mybox.subdomain.domain.com, metaport=port, metauser=username, metapass=password);

   For more information about the RMVINST macro, see SAS Note #31327

Operating System and Release Information