Determine What SAS Version and Components Are Available

Transcription

1 Determine What SAS Version and Components Are Available David D. Chapman, Chapman Analytics LLC, Alexandria, VA ABSTRACT For many reasons a user may not know the version of SAS used or what components of SAS are installed on a particular computer. This paper discusses three different methods for determining what SAS is being used on a particular computer. The three methods discussed include PROC SETINIT, PROC PRODUCT_STATUS, and the SASINSTALLREPORT3.SAS macro. PROC SETINIT shows what is licensed; PROC PRODUCT_STATUS shows what is installed; and the SASINSTALLREPORT macro creates a report describing the complete setup and environment of the machine. Also discussed is the use of SAS system macro variables to determine the version of SAS used. INTRODUCTION Frequently it is important to know what version of SAS and what products of SAS are installed on a computer. This is often needed to manage a program or to solve problems that occur. It is not always clear how to determine this information. DETERMING THE VERSION OF SAS USED There are two relatively simply ways to determine the version of SAS you are using. One is to look at the SAS LOG; the other is to display SAS system macro variables. When SAS starts, basic information on the version is supplied at the top of the SAS log. Normally when SAS starts, a SAS log is created. When interactive SAS is used, the log appears in the LOG window. The first several lines of the log show the version of SAS used and the platform it is running on. This is illustrated in Figure 1. Fig. 1.0 Example SAS LOG showing Version of SAS Used NOTE: Copyright (c) by SAS Institute Inc., Cary, NC, USA. NOTE: SAS (r) Proprietary Software 9.2 (TS2M3) Licensed to JOHN DOE WX6 (64 BIT WNDW), Site NOTE: This session is executing on the X64_VSPRO platform. SAS SYSTEM MACRO VARIABLES An alternative to the SAS LOG is to display the contents of SAS macro variables. SAS creates a set of macro variables containing the parameters or attributes of the SAS installation. Some of these macro variables are static such as the version of SAS; others are dynamic and can be modified such as the page size. When system macro variables are displayed, they are displayed in the SAS LOG. Figure 2 below show parts of the SAS LOG displaying the system automatic macro variables indicating type of operating system and version of SAS currently being used. Fig. 2 Example SAS macro variables containing Version of SAS Used OFTWARE %put _automatic_ WITH MANY ;run; PRODUCTS. ORGANIZATIONS USING SAS COMPONENTS LICENSED {text deleted} AUTOMATIC SYSSCP WIN /* Windows / AUTOMATIC SYSSCPL X64_VSPRO /* 64 bit Professional */ {text deleted} AUTOMATIC SYSVER 9.2 /*SAS version 9.2 */ DETERMINING SAS COMPONENTS LICENSED The components that make up SAS software are licensed and not sold. These components are licensed for a specific length of time and may vary. Software without a valid license generally does not function. A first step in determining whether a SAS component is available is to determine whether it is licensed. 1

2 PROC SETINIT is a procedure that will tell you what parts of SAS are licensed. The procedure is referenced in the SAS knowledge base and there are SAS options and macro variables that deal with related ideas. It is a simple procedure that is run by submitting the code below. Output from the PROC SETINIT is given in Figure 3. PROC SETINIT;RUN; SAS components may be licensed and not installed or installed without a valid current license. 4 PROC SETINIT;RUN; NOTE: PROCEDURE SETINIT used (Total process time): real time 0.00 seconds cpu time 0.00 seconds Original site validation data Site name: 'JOHN DOE WX6 (64 BIT WNDW)'. Site number: Expiration: 01OCT2013. Grace Period: 45 days (ending 15APR2013). Warning Period: 45 days (ending 30MAY2013). System birthday: 01OCT2009. Operating System: WX64_WKS. Product expiration dates: ---Base Product ---SAS/STAT ---SAS/GRAPH ---SAS/OR ---SAS/AF ---SAS/IML {ITEMS DELETED} ---SAS Forecast Studio ---SAS Stat Studio Organizations using base SAS add and subtract installed components as they need them. Most SAS software is licensed and not purchased. This means that it can be used only for a specific length of time. The SAS license information is contained in the installed software. If a SAS license is not valid, the SAS component software generally will not run. A SAS license is often invalid because it has not been renewed. DETERMINING SAS COMPONENTS INSTALLED Just because a SAS component is licensed does not mean it is installed and available. This is particularly true in large organizations. Beginning in SAS 9, SAS introduced a new procedure -- PROC PRODUCT_STATUS -- that shows what is installed. It is not well documented. The code to run PROC PRODUCT_STATUS is given below and its output in Figure 4. PROC PRODUCT_STATUS;RUN; Fig. 3. Example PROC SETINIT output 01MAR2015 2

3 5 PROC PRODUCT_STATUS;RUN; Fig. 4. Example PROC PRODUCT_STATUS Output For Base Product... Custom version information: 9.21_M3 Image version information: M3P For SAS/STAT... Custom version information: 9.22 Image version information: M0P For SAS/GRAPH... For SAS/ETS... Custom version information: 9.22 Image version information: M0P {items deleted} For SAS/SHARE... For SAS/INSIGHT... For SAS/EIS... Custom version information: 9.21 Image version information: M0P For SAS/GIS... NOTE: PROCEDURE PRODUCT_STATUS used (Total process time): real time 1.15 seconds cpu time 0.18 seconds DETERMINING SAS SYSTEM CHARACTERISTICS There are two ways to determine more detail on what SAS release is installed. One is working with the SAS registry; the other is working with SAS code to report the status of the installment of SAS software on a computer. VIEWREGISTRY REPORT The VIEWREGISTRY report identifies SAS software installed by looking at the SAS deployment registry. It is described in SAS Usage Note ( Usage Note 35968, 2012). Use of the SAS registry is not be discussed in detail here. Working with the SAS registry should probably be done by those confident in the ability and knowledge of how SAS works. An extract from SAS usage note is given below. The installation of SAS products is logged in the SAS Deployment Registry. A reporting utility, ViewRegistry processes the deployment registry to generate a report name 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. Implementation and use of the VIEWREGISTRY Report requires a knowledge and understanding of Java and having administrator privileges. This report can be used on both Windows and UNIX flavored operating systems. SAS INSTALLATION REPORT PROGRAM Much simpler to understand and use is the SAS Installation Reporter Program created by SAS Institute. It is functionally similar to the ViewRegistry Report; but, it is created using SAS data step code and procedures. It is described in Usage Note ( Usage Note 20390, 2012). This SAS code creates a report showing which applications, clients, and hot fixes are installed. Version 3, the current version of this report, can be downloaded from support.sas.com through Usage Note It is regular base SAS code run either interactively in the program editor or in batch. The reporting program works for SAS 8 and SAS 9 in both the windows and UNIX flavored environments. The code for this report is in a file associated with this paper in the 2012 NESUG Online Proceedings. This code is a macro with the name %sasinstallreporter. The structure of the six tables that make up the output of this macro is given below in Figure 5. 3

4 Fig. 5. Structure of the Output of SAS Install Reporter Version SAS Install Reporter Version :23 Monday, August 6, SAS 9.2 ( M3P ) SITE: HOST: CHAPMAN-ANNALYTICS OS: WIN (X64_VSPRO) 1: Products, components, or solutions that are licensed 2: Products, components, or solutions that are physically installed 3: Products, components, or solutions that are physically installed 4: Possible Other SAS Institute Applications or Clients Installed 5: Custom Version Information for Selected SAS Institute Products or Components 6: SAS Java Environment Installation Information The SAS Install Report provides current detail information on all SAS installed on the computer. If multiple versions of SAS are installed, reports are provided on each installation. The SAS Install Report creates six separate tables. TABLE 1: PRODUCTS LICENSED The first table of the report provides information similar to PROC SETINIT. The report lists products and components licensed. An extract from table 1 is given in figure 6. Fig. 6.: Table 1 of SAS Install Reporter Version 3 1: Products, components, or solutions that are licensed COMPONENT PRODNUM PRODNUM000 Base Product PRODNUM001 SAS/STAT PRODNUM002 SAS/GRAPH PRODNUM003 SAS/ETS PRODNUM004 SAS/FSP PRODNUM005 SAS/OR {terms deleted} PRODNUM006 SAS/AF PRODNUM007 SAS/IML TABLE 2: PRODUCTS PHYSICALY INSTALLED Table 2 identifies SAS products that are actually installed. Products may be licensed and not installed. It is not clear what happens when a product is installed but with an expired license. Figure 7 show as extract of Table 2. 4

5 Fig. 7. Table 2 of SAS Install Reporter Version 3 2: Products, components, or solutions that are physically installed COMPONENT custver compid Advanced Analytics Common Components 9.22 aacomp Base SAS 9.21 base Base SAS Statistical Procedures 9.22 basestat CGI Tools for the Web Server 9.21 cgitools DataFlux Integration Server 8.1 dfintsvr Java Platform Standard Edition Runtime Environment default javaruntime ODS Templates 9.21 odstemplate Report Fonts for Clients 9.21 ttfontsvert Report Fonts for Servers 9.21 ttfontsmva SAS BI Web Services for.net 23 xmladotnet {items deleted} SAS Table Server Base Components 9.2 tablesrvtk SAS Threaded Kernel Extensions for Advanced Analytics 9.22 tkaa SAS Threaded Kernel Extensions for Econometric Time Series 9.22 tkets SAS Threaded Kernel Extensions for Operations Research 9.22 tkormp SAS XML Mapper 9.21 xmlatlas SAS/ACCESS Interface to PC Files 9.21 pcfile SAS/AF 9.21 af SAS/CONNECT 9.21 connect TABLE 3: HOT FIXES INSTALLED SAS evolves primarily through major (SAS 8 to SAS 9), minor (SAS to SAS 9.2.3), and maintenance (SAS 9.21_M2 to 9.21_M3) releases. Often between these releases problems are identified that need correcting. These corrections are done through Hot Fixes. Hot fixes correct a specific problem. They may be unique to a specific procedure, a specific platform, or both. The list of the available hot fixes is on the SAS support web site. The code and instructions to update your version of SAS and correct the problem can be downloaded from the SAS website. Table 3 of the SAS installation report identifies what hot fixes have been installed to the current release of SAS. Table 3 is not produced when no hot fix has been installed. No example of Table 3 is given in this paper because the version of SAS used to produce this paper did not have any hot fixes installed. TABLE 4: OTHER SAS APPLICATIONS AVAILABLE When many people think of SAS, they think of BASE SAS. Increasingly there are a number of other SAS products available. Table 4 of the installation report lists other SAS related products currently being used. Figure 8 below show an extract of that table. 5

6 Fig. 8. Table 4: Possible Other SAS Institute Applications or Clients Installed These are just folders or file names in the SAS installation path and applications registered in Windows-- EXPECT DUPLICATES!! COMPONENT CGIToolsForTheWebServer Documentation EnterpriseGuide NVWorkshop PCFilesServer ReportFontsforClients SAS Service Configuration Utility SASDriversForSASConnect SASDriversforJDBC SASETSModelEditor { item deleted} These are just folders or file names in the SAS installation path and applications registered in Windows-- EXPECT DUPLICATES!! COMPONENT SharedFiles SharedFiles(32) TSODBC 5: CUSTOM VERSIONS OF SAS PRODUCTS Table 5 summarize the customization of the current version of SAS software installed. The information it presents is quite similar to information presented by PROC PRODUCT_STATUS. Figure 9 shows selected output from Table 5. Fig. 9. Table 5: Custom Version Information for Selected SAS Institute Products or Components COMPONENT Custom version Build version Base Product 9.21_M M3P SAS/STAT M0P SAS/GRAPH 9.21_M2 SAS/ETS M0P {information deleted} TABLE 6: SAS JAVA ENVIRONMENT Java is an important tool and language in making components of the SAS system work together. Table 6 of the SAS Install Reporter lists the JAVA environment for the current installation of SAS. Figure 10 gives an extract of Table 6. 6

7 Fig. 10. Table 6: SAS Java Environment Installation Information java.runtime.name = Java(TM) 2 Runtime Environment, Standard Edition java.runtime.version = 1.5.0_12-b04 java.security.auth.login.config = C:\Program Files\SAS\SASF\9.2\core\sasmisc\sas.login.config java.security.policy = C:\Program Files\SAS\SASF\9.2\core\sasmisc\sas.policy java.specification.version = 1.5 java.system.class.loader = com.sas.app.appclassloader java.vendor = Sun Microsystems Inc. java.version = 1.5.0_12 java.vm.name = Java HotSpot(TM) Client VM java.vm.specification.version = 1.0 java.vm.version = 1.5.0_12-b04 sas.app.class.path = C:\PROGRA~1\SAS\SASVER~1\9.2\eclipse\plugins\tkjava.jar CONCLUSIONS In order to properly understand and maintain SAS software it is important to understand what version of SAS is installed, what products are installed, and the current characteristics of the SAS installation. When problems happen, it is often because products do not work together. Verifying the current installation is often the first step to diagnosing and resolving problems. The tools available depend on the version of SAS being used. The simplest tools are PROC SETINIT and PROC PRODUCT_STATUS. These require minimal knowledge to use them. They will identify the basic problems. Probably the easiest and most comprehensive tool is the %sasinstallreport macro. Every SAS user should download it and try it out. For organizations that maintain a macro library, the %sasinstallreport macro could be maintained centrally in the organizations macro library for all to use. REFERENCES: SAS 9.2 Provides New Product-Specific Release Numbers. (2012). Retrieved August 10, 2012, from Usage Note 35968: Using the View Registry Report and other methods to determine the SAS 9/.2 and SAS 9.3 software releases and hot fixes that are installed. (2012). Retrieved August 10, 2012, from Usage Note The SAS Installation Reporter Program creates a report showing which applications, clients, and hot fixes are installed. (2012). Retrieved August 10, 2012, from ACKNOWLEDGMENTS SAS and all other SAS Institute Inc. product or service names are registered trademarks or trademarks of SAS Institute Inc. in the USA and other countries. indicates USA registration. Other brand and product names are registered trademarks or trademarks of their respective companies. CONTACT INFORMATION Your comments and questions are valued and encouraged. Contact the author at: Author Name David D. Chapman Company Chapman Analytics LLC City, State ZIP Alexandria, VA Work Phone: (703) chapman.analytics.va@gmail.com * * * * * * * * ** * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * 7