57183 - Viewing the SID files in metadata via code submission for SAS® 9.4 (TS1M1) and earlier or via SAS® Management Console for SAS® 9.4 (TS1M2) and later

Usage Note 57183: Viewing the SID files in metadata via code submission for SAS® 9.4 (TS1M1) and earlier or via SAS® Management Console for SAS® 9.4 (TS1M2) and later

SAS 9.4 Enterprise BI and other SAS solutions, such as SAS^® Activity-Based Management, SAS^® Enterprise Miner™, and SAS^® Visual Analytics, put SAS installation data files (SID files) in metadata at the time of installation. (For a list of SAS solutions, see SAS KB0036256, "To extend the expiration date for particular SAS^® solutions, you must perform the 'Update SID File in Metadata' task.") The SID file contains the setinit, which contains product authorization that identifies products and expiration dates.

Now, beginning with SAS 9.4 (TS1M2), you can use SAS Management Console to view the setinit in metadata.

If You Are Using a Release Prior to SAS 9.4 (TS1M1), Submit Code

Note: This code also works for SAS 9.4 (TS1M2) and later.

Click the Full Code tab in this SAS Note.
Copy the code.
Paste into a SAS session.
Modify the code as noted in the code.
Submit the SAS code.
In the metasetinit.xml file that is generated, view the PROC SETINIT sections for the SID files currently in metadata.
For assistance with questions or error messages, send the metasetinit.xml file to SAS Technical Support.

If You Are Using SAS 9.4 (TS1M2) or Later

Use the code noted above or follow these steps to view the SID files in metadata:

Open SAS Management Console 9.4.
Connect with an unrestricted account, such as sasadm@saspw.
Click to expand Environment Management.
Click to expand Metadata Manager.
Click to expand Metadata Utilities.
Right-click Metadata Utilities and select View metadata setinit details.

The Setinit details in metadata dialog box appears, containing a tab for each SAS site number in metadata, including product IDs and expiration dates. If needed, click the Save to File button to save the contents of the dialog box. Note: If this dialog box does not appear, then submit the code from the Full Code tab in this SAS Note. Alternatively, if SAS 9.4 (TS1M4) is installed, then one option is to apply the hot fix on the Hot Fix tab of this SAS Note, in order for the dialog box to appear.

For assistance with questions or error messages, make a screen shot of each site number tab. On each site number tab, click the Save to File button and provide a unique filename. Send all screen shots and files created to SAS Technical Support.

If You Need to Update the Existing SID Files

Microsoft Windows Operating Environments

Locate the SID file(s) with the same SAS site number(s) and then perform steps D and E below. These steps are from SAS^® 9.4 Software License Renewal Instructions for Microsoft Windows and Windows for x64 Planned Deployment.

D. Update the SID File in Metadata for Applicable SAS Solutions.

E. Restart SAS Servers and SAS Spawners.

UNIX Operating Environments

Locate the SID file(s) with the same SAS site number(s) and then the perform steps in Software License Renewal Instructions: SAS^® 9.4 for UNIX Environments Planned Deployment.

Operating System and Release Information

Product Family	Product	System	Product Release		SAS Release
Product Family	Product	System	Reported	Fixed*	Reported	Fixed*
SAS System	Base SAS	Microsoft® Windows® for x64	9.4_M2		9.4 TS1M2
		Microsoft Windows 8 Enterprise 32-bit	9.4_M2		9.4 TS1M2
		Microsoft Windows 8 Enterprise x64	9.4_M2		9.4 TS1M2
		Microsoft Windows 8 Pro 32-bit	9.4_M2		9.4 TS1M2
		Microsoft Windows 8 Pro x64	9.4_M2		9.4 TS1M2
		Microsoft Windows 8.1 Enterprise 32-bit	9.4_M2		9.4 TS1M2
		Microsoft Windows 8.1 Enterprise x64	9.4_M2		9.4 TS1M2
		Microsoft Windows 8.1 Pro	9.4_M2		9.4 TS1M2
		Microsoft Windows 8.1 Pro 32-bit	9.4_M2		9.4 TS1M2
		Microsoft Windows Server 2008	9.4_M2		9.4 TS1M2
		Microsoft Windows Server 2008 R2	9.4_M2		9.4 TS1M2
		Microsoft Windows Server 2008 for x64	9.4_M2		9.4 TS1M2
		Microsoft Windows Server 2012 Datacenter	9.4_M2		9.4 TS1M2
		Microsoft Windows Server 2012 R2 Datacenter	9.4_M2		9.4 TS1M2
		Microsoft Windows Server 2012 R2 Std	9.4_M2		9.4 TS1M2
		Microsoft Windows Server 2012 Std	9.4_M2		9.4 TS1M2
		Windows 7 Enterprise 32 bit	9.4_M2		9.4 TS1M2
		Windows 7 Enterprise x64	9.4_M2		9.4 TS1M2
		Windows 7 Home Premium 32 bit	9.4_M2		9.4 TS1M2
		Windows 7 Home Premium x64	9.4_M2		9.4 TS1M2
		Windows 7 Professional 32 bit	9.4_M2		9.4 TS1M2
		Windows 7 Professional x64	9.4_M2		9.4 TS1M2
		Windows 7 Ultimate 32 bit	9.4_M2		9.4 TS1M2
		Windows 7 Ultimate x64	9.4_M2		9.4 TS1M2
		64-bit Enabled AIX	9.4_M2		9.4 TS1M2
		64-bit Enabled Solaris	9.4_M2		9.4 TS1M2
		HP-UX IPF	9.4_M2		9.4 TS1M2
		Linux for x64	9.4_M2		9.4 TS1M2
		Solaris for x64	9.4_M2		9.4 TS1M2

* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.

Sample program to pull any TextStore object from metadata that contains setinit info. Before running this code, be sure you modify the initial OPTIONS statement to provide values that are appropriate for your metadata server and edit the FILENAME statement to reference a valid path. For Linux operating systems, to use NODMS, see instructions in the comment section.

      /***************************************************/
      /*** Sample program to pull any TextStore object ***/
      /*** from metadata that contains setinit info.   ***/
      /***                                             ***/
      /*** IMPORTANT:  Before running this code, be    ***/
      /***        sure you modify the initial OPTIONS  ***/
      /***        statement to provide values that are ***/
      /***        appropriate for your metadata server ***/
      /*** IMPORTANT: edit the FILENAME statement to   ***/
      /***        reference a valid path where your    ***/
      /***        USERID has rights to create a file.  ***/
      /*** Example Unix path:                          ***/   
      /*** "/home/sasinstall/METASETINIT.XML";         ***/
      /***                                             ***/
      /*** RESULT: This code creates a METASETINIT.XML ***/ 
      /***      file with *all* the SID files/setinits ***/  
      /***      currently in Metadata.                 ***/
      /***************************************************/

      /***************************************************************************/
      /*** For Linux operating systems, to run SAS in NODMS mode               ***/
      /*** do the following:                                                   ***/
      /***                                                                     ***/
      /*** 1. Create SAS program file from the code below, or use              ***/
      /*** ftp://ftp.sas.com/techsup/download/blind/SASCodeToRetrieveSIDs.sas  ***/
      /*** 2. Modify code for metadata server, file location, and so on.       ***/
      /*** 3. Put the SAS program in /tmp                                      ***/
      /*** 4. Navigate to (SASHome)/SASFoundation/9.4                          ***/
      /*** 5. Run  ./sas -nodms                                                ***/
      /*** 6. When screen opens enter:                                         ***/
      /***     %include "(path to the .sas code)";                             ***/
      /***     Hit Enter.                                                      ***/
      /*** 7. Look for metasetinit.xml in /tmp                                 ***/
      /*** 8. To get out of nodms, type:                                       ***/
      /***      endsas;                                                        ***/
      /***************************************************************************/


options metaserver="your.metadata.server.host"  /*change to your metadata server name*/
        metaport=8561              /* if needed, change port  */         
	metauser="sasadm@saspw"    /* if needed, change user  */  
	metapass="sasadmpw"        /* change password */
	metarepository="Foundation"
	metaprotocol=BRIDGE;

filename setinit "c:\metasetinit.xml";  /* if needed, change drive and add folder(s) */
               /* Your USERID must have rights to create files in folder specified */
               /* On Unix operating systems, you might use "/tmp/metasetinit.xml" */
proc metadata in=
"<GetMetadataObjects>
   <Reposid>$METAREPOSITORY</Reposid>
   <Type>TextStore</Type>
   <NS>SAS</NS>
   <Flags>2441</Flags>
   <Options>
      <XMLSelect search=""*[@Name ? 'setinit']""/>
   </Options>
 </GetMetadataObjects>"  out=setinit;
run;

Date Modified:	2016-08-24 17:28:36
Date Created:	2015-12-03 10:36:26

Type:	Usage Note
Priority:

Support