Using the ViewRegistry Report and other methods to determine the software releases and hot fixes that are installed


ViewRegistry Report

Introduction

The installation of SAS® products is logged in the SAS Deployment Registry. ViewRegistry (sas.tools.viewregistry.jar) is a reporting utility that processes the deployment registry to generate the DeploymentRegistry.html report. This report identifies all SAS® 9.2 and later software that is installed in the current SASHOME location. Installed hot fixes are also logged in the SAS Deployment Registry and reported in DeploymentRegistry.html.

Beginning with SAS® 9.4M3 (TS1M3), the default output will report only the current release of product components that are installed in the current SASHOME. Duplicate product component entries will appear only for products that support side-by-side deployment, for example SAS® Enterprise Guide and SAS® Add-in for Microsoft Office. The -all option can be used to report on all product components that have been installed in SASHOME; see the Report Options section below.

Preparing to Run the ViewRegistry Report

This utility is installed by default with SAS® 9.2M2 (TS2M2) and later in SASHOME/deploymntreg.

If you are running a SAS 9.2 release earlier than SAS 9.4M2, you can download sas.tools.viewregistry.jar. The file must be saved to the SASHOME/deploymntreg directory, and it must be saved with a .jar extension.

Requirements:

Generating the ViewRegistry Report

sas.tools.viewregistry.jar must be executed from the SASHOME/deploymntreg directory.

Two output files are produced by the reporting utility, DeploymentRegistry.html and DeploymentRegistry.txt. The HTML and TXT output files are written in the SASHOME/deploymntreg directory.  The DeploymentRegistry.txt or DeploymentRegistry.html files can be viewed with a method of your choosing.

Windows:

Double-click on sas.tools.viewregistry.jar to run the file.

Alternatively, the JAR file can be executed from a command prompt:

(For SAS 9.2): C:\Program Files\SAS\deploymntreg> java -jar sas.tools.viewregistry.jar

(For SAS 9.3 or 9.4 installed with no other SAS release): C:\Program Files\SASHome\deploymntreg> java -jar sas.tools.viewregistry.jar

(For SAS 9.4, with SAS 9.3 installed as well): C:\Program Files\SASHome2\deploymntreg> java -jar sas.tools.viewregistry.jar

UNIX:

Execute the JAR file,

       SASHOME/deploymntreg> java -jar sas.tools.viewregistry.jar

where SASHOME is the directory where SAS is installed. In the examples below, SASHOME is /apps/sas92m3.

Host-specific examples:

HPUX (64-bit), HPUX IPF:
/apps/sas92m3/deploymntreg> ../jre1.5.0.08/bin/java -jar sas.tools.viewregistry.jar

Linux, Linux for x64:
/apps/sas92m3/deploymntreg> ../jre1.5.0_14/bin/java -jar sas.tools.viewregistry.jar

AIX (64-bit):
/apps/sas92m3/deploymntreg> ../jre1.5_SR5/jre/bin/java -jar sas.tools.viewregistry.jar

Solaris (64-bit), Solaris for x64:
/apps/sas92m3/deploymntreg> ../jre1.5.0_12/bin/java -jar sas.tools.viewregistry.jar

SAS 9.4 - all Unix platforms

/apps/sas94m5/deploymntreg> ../SASPrivateJavaRuntimeEnvironment/9.4/jre/bin/java -jar sas.tools.viewregistry.jar

Note: In order to run the reporting utility on UNIX systems, you must have Write permission to the SASHOME location because the resulting reports are written to this location. See Report options for information about using the -out option.

VMI:

Execute the JAR file.

java -jar sas.tools.viewregistry.jar

Note: In order to run the reporting utility on VMI, you must first set the following logicals and process attribute:

$ set process/parse=extended
$ DEFINE DECC$ARGV_PARSE_STYLE ENABLE
$ DEFINE DECC$EFS_CHARSET ENABLE
$ DEFINE DECC$EFS_CASE_PRESERVE ENABLE
$ define JAVA$FILE_OPEN_MODE 3
$ define java$filename_controls 0

z/OS:

Execute the JAR file from UNIX System Services (USS) by issuing the following commands in omvs:

cd SASHOME directory/deploymntreg 
java -jar sas.tools.viewregistry.jar

where SASHOME directory is the directory where SAS is installed. If you do not know where your SASHOME directory is, it is the directory specified in the "set SASHOME=" statement in your TKMVSENV data set. If you do not have java defined in your PATH environment variable, you may need to put the entire java path in the second command, for example:

/usr/lpp/java/J6.0/bin/java -jar sas.tools.viewregistry.jar  

if java was installed at /usr/lpp/java/J6.0

Report Options

java -jar sas.tools.viewregistry.jar -hotfix

java -jar sas.tools.viewregistry.jar -out /u/myuserid/output

java -jar sas.tools.viewregistry.jar -all

Sample Output


Deploy Registry Report

* Note: This report output has been modified for the demonstration purposes.

Troubleshooting Problems with the ViewRegistry Report

Using PROC PRODUCT_STATUS to Determine SAS Software Installation Information

Another way to determine maintenance levels is to submit this code and inspect the log window:

      proc product_status;
      run;

This code generates information for SAS® Foundation products only; it does not generate information for web applications, other Java based products, or hot fixes. This code is available on all operating systems.

Note:
proc product_status; output might not reflect the same content as the SAS Deployment Registry report for z/OS.

Sample Output:

Product Status

More Information about Product Release and Maintenance Numbers

To learn more about maintenance product release numbers, see the following resources: