Providing software solutions since 1976

• Log in
• Create profile
• Welcome
  [Log out]
• Edit profile
• My SAS

• Print  |
• Feedback  |
• Share

  • E-mail
  

  E-mail This Page

  Your Name:*
  Your E-mail:*
  Recipient E-mail:*
  Send a copy to me
  Personal Message:
  
  

  * indicates a required field

ViewRegistry Report

1. Introduction
2. Preparing to run the ViewRegistry Report
3. Generating the ViewRegistry Report
4. Report options
5. Sample output
6. Troubleshooting problems with the ViewRegistry Report
7. Using PROC PRODUCT_STATUS to determine SAS software installation information
8. More information about product release and maintenance numbers

1. Introduction

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

2. Preparing to run the ViewRegistry Report

   This utility is installed by default with SAS 9.2 TS2M2 or later in SASHOME/deploymntreg.

   If you are running a SAS 9.2 release prior to TS2M2, 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:

   • You must be running Java 5 Update 12 or later.
   • You must have administrator privileges.

3. 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.

   
   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): C:\Program Files\SASHome\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

   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 on using the -path 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):

   cd sashome/deploymntreg then execute jar command java –jar sas.tools.viewregistry.jar

4. Report options

   -hotfix

   reports only the product components to which hot fixes have been applied, including the hot fix ids. No parameter is accepted.

   Example: java –jar sas.tools.viewregistry.jar -hotfix

   -out <parameter>

   specifies an alternative output directory for DeploymentRegistry.html and DeploymentRegistry.txt. This option should be used if you do not have write access to SASHOME, which is the default output location.

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

   
   

5. Sample output

   
   

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

6. Troubleshooting problems with the ViewRegistry Report

   • How to troubleshoot problems when running the sas.tools.viewregistry.jar tool to see what products you have installed

     See Problem Note 38551 for more details.

7. 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 will generate information for SAS® Foundation products only; it will 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 may not reflect the same content as the SAS Deployment Registry report for z/OS.

   
   Sample output:

   

8. More information about product release and maintenance numbers

   To learn more about maintenance product release numbers, see

   • Understanding Product Release Numbers in Planning for Maintenance Releases and Product Upgrades for SAS® 9.2
   • Determining the Product Release Numbers for Products at Your Site in SAS® 9.3 Guide to Software Updates
   • SAS® 9.2 Provides New Product-Specific Release Numbers.

Operating System and Release Information