Introduction

The installation of SAS^® products is recorded in the SAS Deployment Registry. ViewRegistry (sas.tools.viewregistry.jar) is a reporting utility that processes the SAS Deployment Registry to generate the ViewRegistry report. This report identifies all SAS^® 9.4 software that is installed in the current SASHome location. Installed hot fixes are also logged in the SAS Deployment Registry and reported in the ViewRegistry report.

Generating the ViewRegistry Report

This utility is installed by default in <SASHome>/deploymntreg. The 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 by default. 

Windows

Run the Command Prompt as Administrator.

cd to <SASHome>\deploymntreg

Example:

cd C:\Program Files\SASHome\deploymntreg

Invoke sas.tools.viewregistry.jar using the SAS Private Java Runtime Environment.

Example:

"C:\Program Files\SASHome\SASPrivateJavaRuntimeEnvironment\9.4\jre\bin\java.exe" -jar sas.tools.viewregistry.jar

UNIX

cd to <SASHome>/deploymntreg

Example:

cd /opt/sas/SASHome/deploymntreg 

Invoke sas.tools.viewregistry.jar using the SAS Private Java Runtime Environment.

Example:

/opt/sas/SASHome/SASPrivateJavaRuntimeEnvironment/9.4/jre/bin/java -jar sas.tools.viewregistry.jar

Note: To run the ViewRegistry utility on UNIX systems, you need Write permission for the SASHOME directory because the generated reports are saved there. For details about using the -out option to specify an alternative output directory, see Report Options.

z\OS

cd to <SASHome>/deploymntreg

Example:

cd SASHome/deploymntreg

Invoke sas.tools.viewregistry.jar using Java.

Example:

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

Note: This example assumes Java is installed at /usr/lpp/java/J6.0

Report Options

The ViewRegistry utility provides several command-line options to customize the content and location of your ViewRegistry report. You can use these options to tailor your ViewRegistry report to your specific needs.

• -hotfix
  Report only the product components to which hot fixes have been applied, including the hot fix IDs.
  
  Caution: Do NOT use the -hotfix option if you are generating the ViewRegistry Report to be used with the SAS Hot Fix Analysis, Download and Deployment Tool (SASHFADD).
  
  Example:

"C:\Program Files\SASHome\SASPrivateJavaRuntimeEnvironment\9.4\jre\bin\java.exe" -jar sas.tools.viewregistry.jar -hotfix

• -out <parameter>
  Specify an alternative output directory for DeploymentRegistry.html and DeploymentRegistry.txt. Use this option if you do not have Write access to SASHOME, which is the default output directory.
  
  Example:

"C:\Program Files\SASHome\SASPrivateJavaRuntimeEnvironment\9.4\jre\bin\java.exe" -jar sas.tools.viewregistry.jar -out “C:\Output”

• -all
  Valid beginning with SAS^® 9.4M3; report all product components that have been installed, which might include multiple releases of a product component that has been upgraded.
  
  Caution: Do NOT use the -all option if you are generating the ViewRegistry Report to be used with the SAS Hot Fix Analysis, Download and Deployment Tool (SASHFADD).
  
  Example:

"C:\Program Files\SASHome\SASPrivateJavaRuntimeEnvironment\9.4\jre\bin\java.exe" -jar sas.tools.viewregistry.jar -all