When you apply a new SAS license (setinit) each year, do you forget to also update it in metadata? @PaulHomes sometimes does and remembers when he gets an email from the SAS platform itself...
Paul wrote a blog post on How to check a SAS Setinit/License in Metadata that you may find helpful and be sure to also read the comments where @GerryNelson shares a link to his excellent video showing how to set up proactive license expiration alert emails with SAS Environment Manager.
I will make a cross reference with @MarkThomas 's contribution: How to quietly automate the application of SAS licenses
@MichelleHomes - thank you very much for posting this. Great to learn a new feature that has been around a while and I didn't even notice!
It is worth pointing out though that for this check to be accurate, you need to have loaded the latest SAS licence into SAS metadata using the SAS Deployment Manager as in the screenshot below.
It is still possible to apply the licence in a SAS session or using the SAS Renewal Utility without loading it into metadata also. This applies to SAS installations where there are no licensed SAS web-based products, so the licence in metadata may not be the current one. Something to be careful about.
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.
Learn how to install the SAS Viya CLI and a few commands you may find useful in this video by SAS’ Darrell Barton.
Find more tutorials on the SAS Users YouTube channel.