LICENSEWARE
Contribute

SAS 9 setinit and license renewal

From the LICENSEWARE WikiLast edited 11 ReferencesCited

This article is about how SAS 9 (SAS 9.4 and earlier) licences are delivered, enforced and renewed through the setinit and SAS installation data (SID) file, including grace and warning periods, temporary licences and CPU-based subcapacity licences. For SAS Viya, see SAS Viya licensing.

On This Page

In SAS 9, which covers SAS 9.4 and earlier releases, a licence is a period of use enforced by data SAS calls the setinit. SAS delivers it in the SAS installation data (SID) file. SAS UK notes that the licence key “may be referred to as a SAS Installation Data (SID), setinit, or authorisation key.”[8] The renewal instructions state: “SAS software is licensed on a periodic basis. In order to run your licensed software, you must apply the SAS installation data file (SID file) to renew your software.”[1] A SAS 9 licence manager must therefore follow a technical renewal cycle as well as the commercial one. See SAS licensing for the overview.

Editions

The setinit covers the products a site has licensed, each with its own expiration date. SAS 9.4 is the current SAS 9 release. SAS 9.4M9 became generally available in June 2025, with Standard Support to 2030-07-01. SAS 9.4M8 has Standard Support to 2028-02-01. SAS 9.4M7 entered Limited Support on 2025-09-01, and SAS 9.4M0 to M6 on 2025-02-01.[10] Licence renewal instructions are published for each operating system (Windows, UNIX, z/OS) and for older releases back to SAS 6.[3] Catalog: SAS 9.4M9 Standard Support until 2030-07-01.

Metrics

SAS term Catalog row In the setinit 
Site number SAS site Part of the SID file name (SAS94_order-number_site-number_host-platform.txt)[1] 
Expiration date License period Per product, with grace and warning periods[9] 
Cores Licensed cores SERIAL field of the CPU line, for example SERIAL=‘+4’[4] 
Computer name Designated machine MODEL and MODNUM fields of the CPU line[4] 

To see a site’s setinit, run proc setinit; run;. SAS UK gives this command in its FAQ.[8]

Counting / floors

When a new SID file is needed. “A SID file must be applied when the license period has expired, and/or there has been a change in the SAS software products that are covered by the license.” Added products need an add-on installation with the new SID file. If products are unchanged or dropped, only a renewal is needed.[1] The designated installation representative receives the SID files by email from SAS Software Orders.[1] Catalog: SAS 9.4 is licensed periodically and renewed by applying a SID file; A SID file is needed on expiry or when licensed products change.

Applying it everywhere. The Renew SAS Software utility must be run “on each machine in your deployment where SAS Foundation is installed”.[1] On UNIX, the renewal must use the SAS installer user ID. Deployments with solutions that depend on a SAS middle tier must also update the SID file in the metadata repository.[2] A machine that misses the update keeps the old expiration date. Catalog: Solutions with a middle tier need the SID file updated in metadata.

Keeping the file. Customers should store SID files where regular backups occur. “Without the data in the SID file, you will not be able to renew your license or add any newly licensed products to your existing SAS 9.4 installation.”[1] Catalog: Keep the original SID file; without it renewal is impossible.

Grace and warning periods. After the expiration date, a grace period and then a warning period apply. The lengths are written into the setinit. SAS UK says that for most products “The length is 30 days grace and 30 days warning and will expire at midnight”. Its warning messages mean “that your licence has expired and payment is due”.[8] SAS’s Viya 3.5 documentation states that as of June 2024 the grace period is zero days and the warning period 15 days, and that SAS does not run once the warning period ends.[9] Because the two sources differ, the PROC SETINIT output for each site is the reliable reference. Some SAS 9.3 and 9.4 solutions “might stop working during the licensing warning period” because of how they validate licences in metadata, so for them the warning period may not give working time.[7] Catalog: SAS UK: 30 days grace and 30 days warning for most products; Some SAS 9.3/9.4 solutions stop during the warning period.

Virtualization & partitioning

Subcapacity licences. Since SAS 9.2, SAS for Windows can be licensed “based on a limited number of cores and a specific machine name or computer name”, which SAS calls subcapacity licensing.[4] The rules are:[4]

  • SAS must be installed on a physical or virtual machine with the designated computer name and “the designated number of cores or fewer cores”.
  • Counting is “based on the total number of cores, not the number of processors”. On a virtual machine, the number of CPUs configured in the VM is the core count.
  • The CPUCOUNT system option is not a workaround. The customer cannot have more cores on the machine and use CPUCOUNT to limit what SAS uses.
  • From SAS 9.3, “hyperthreading is not a factor and can remain enabled”.
  • “You cannot manually modify the SID file.” A different machine name or core count needs a new SID file from SAS Sales or the SAS Contracts Department. SAS can also issue a licence with no core or machine check (SERIAL=”).

On SAS 9.2, hyper-threading doubled the CPU count reported to SAS. This could exceed the licensed count and produce the error “You are licensed to run on a system with a CPU of no more than 1 but the actual CPU count is 2.”[5] On UNIX, a subcapacity installation fails if the hostname does not match the SID file.[6] Catalog: Subcapacity licences bind SAS to a named machine and core count; Subcapacity counts cores, not processors; hyper-threading ignored from SAS 9.3; CPUCOUNT cannot be used to fit a larger machine into a subcapacity licence; SID files cannot be edited; changes need a new SID from SAS; SAS 9.2 subcapacity licences double-count with hyper-threading.

As commentary: unlike most per-core licences, a SAS subcapacity licence is enforced by the software at start-up. Adding vCPUs to a virtual machine above the licensed count stops SAS rather than creating a silent compliance gap. Increasing the count requires a commercial change and a new SID file.

Virtualization support. SAS 9.1.3 and later are supported in hardware virtualization such as VMware, provided the operating environment is supported physically. Dynamic operations on virtual machines with active SAS processes, such as VMware VMotion and VM snapshots, are not compatible.[11] Catalog: SAS is supported in virtualization, but VMotion and snapshots are not compatible.

Cloud / BYOL

SAS 9.4 and later are supported on AWS, Microsoft Azure, Google Cloud and other clouds, under the conditions SAS publishes.[11] Subcapacity licensing for cloud machines such as Amazon “is different from the typical subcapacity licensing”. Such SID files carry MODEL or MODNUM values starting with AM.[4] Catalog: Cloud subcapacity licences differ from standard subcapacity.

Programs

Temporary License Extension. In my.sas.com, the Sites and Licenses page has a Temporary License Extension option for each site number.[3] “For emergency situations, you can download a temporary SID file that will extend the use of your licensed SAS software offerings for 15 days.”[1] SAS UK describes a temporary licence as a way to allow time for payment. On non-payment, a short-term extension setinit is provided only “upon receipt of written proof that the outstanding payment is to be made”.[8] Catalog: Emergency temporary SID file extends use for 15 days; Non-payment: short-term extension only with proof of payment.

Renewal notice. SAS UK sends a pre-renewal notification about 120 days before the renewal date. It lists the licensed software, renewal dates and contacts.[8] The licence key goes to the Main SAS Representative once licence fees have been paid.[8] Catalog: Pre-renewal notice about 120 days before renewal.

Audits and compliance

The setinit makes SAS 9 compliance largely self-enforcing for expiry and, under subcapacity licences, for core counts.[4][9] Practical controls for a licence manager are:

  1. Keep every SID file and the order emails.[1]
  2. Record the PROC SETINIT output of each SAS installation, including site, products, expiration, grace and warning periods, and any CPU line.[8][4]
  3. Check that VM sizes match the licensed cores before resizing.[4]
  4. Start renewal when the pre-renewal notice arrives, about 120 days ahead.[8]

Contractual audit rights are in the SAS contract. See SAS contracts, support and audit.

Out of scope

  • SAS 9 prices and the products in individual orders.
  • z/OS and older platforms’ setinit procedures (PROC SETINIT batch jobs), which follow the same model.
  • SAS Viya, covered in SAS Viya licensing.
  • JMP, which has separate licensing.

References

  1. Software License Renewal Instructions: SAS 9.4 Foundation for Microsoft Windows, Basic DeploymentsDated 23 October 2025. Catalog: SAS 9.4 Foundation for Microsoft Windows: Software License Renewal Instructions (Basic Deployments)Effective 2025-10-23. Retrieved 2026-10-02.
  2. Software License Renewal Instructions: SAS 9.4 Foundation for UNIX Environments, Planned DeploymentDated 4 April 2025. Catalog: SAS 9.4 Foundation for UNIX Environments: Software License Renewal Instructions (Planned Deployment)Effective 2025-04-04. Retrieved 2026-10-02.
  3. Get License Assistance | SAS SupportUndated. Catalog: SAS License AssistanceRetrieved 2026-10-02.
  4. Installation Note 41121: Starting in SAS 9.2, a SAS subcapacity license for a Microsoft Windows operating system is available and includes number of cores and computer nameDate Modified 2013-02-13. Catalog: SAS Note 41121: SAS subcapacity license for Microsoft WindowsEffective 2013-02-13. Retrieved 2026-10-02.
  5. Problem Note 41826: In Windows operating environments, applying a SAS 9.2 subcapacity license reports double the number of processors when hyper-threading is enabledDate Modified 2011-05-05. Catalog: SAS Note 41826: subcapacity license and hyper-threadingEffective 2011-05-05. Retrieved 2026-10-02.
  6. Problem Note 41510: Installation fails if hostname does not match SID file or if hostname is longer than 11 characters on UNIX platformsSAS Note on UNIX subcapacity licencesRetrieved 2026-10-02.
  7. Problem Note 59495: SAS 9.3 and SAS 9.4 solutions might return an error message and stop working during the licensing warning periodDate Modified 2019-07-22. Catalog: SAS Note 59495: solutions may stop during the licensing warning periodEffective 2019-07-22. Retrieved 2026-10-02.
  8. Customer Licensing | SAS UKSAS UK FAQ; undated. Catalog: SAS UK Customer Licensing FAQRetrieved 2026-10-02.
  9. SAS Viya 3.5 Administration: LicensingJune 2024 change to grace and warning periods. Catalog: SAS Viya 3.5 Administration: LicensingRetrieved 2026-10-02.
  10. Support for SAS® 9.4 & Earlier Releases | SAS SupportUndated. Catalog: Support for SAS 9.4 and Earlier ReleasesRetrieved 2026-10-02.
  11. SAS® Product Support for Virtualization Environments | SAS SupportUndated. Catalog: SAS Product Support for Virtualization EnvironmentsRetrieved 2026-10-02.

See also

Catalog Rows Cited

17Rules4Metrics2Programs

Esc