Very interesting, crystal clear and comprehensive ! Thanks a lot. This article I wish I'd known long before really fills a gap in (my) SAS knowledge.   When the quantiles to be calculated are equal-sized and not unevenly spaced (the latter being assumed here), as with deciles complete list (P10, P20 ... P80, P90) or even percentiles (P1, P2 ...P98, P99,P100 ), the list of procedures then becomes shorter, it seems - please, correct me if I'm wrong  :   Proc UNIVARIATE (instruction PCTLPTS) Proc STDIZE (id.) Proc HPBIN (instruction NUMBIN) ... View more

Thanks @clmeye, this is a must-have for administrators of all kinds. I've had to devise such scripts/aliases before, this will definitely ensure that the SAS n-tiers platforms are started/stopped/re-started/monitored in a more "graceful" - and technically sound - manner :-). ... View more

I was asked to provide some rational motives for buying the metacoda toolset a few years ago. I agree with  @AndrewHowell, as far as I know there is only one alternative developed in Germany but designed for a somewhat different use case : it's a (reasonably rich) interactive visualisation tool which can be used to make some impact analysis : - who/which group has access to such library, in turn stores which tables ? etc.   http://flitcon.de/en/products/software_en   I guess it looks complementary to Metacoda tools which create tabular reports (among other most useful things.   If by any chance, some people from Flitcon would like to give us some more follow up here about their products, I'll be happy to learn ein bisschen mehr darüber    For a limited span of features, one can also look at the built-in Metadata Security Data Step functions :   https://support.sas.com/documentation/cdl/en/lrmeta/70119/HTML/default/viewer.htm#n0hll9ra1wevzhn1lrrisbjybcjk.htm   This basic framework can be used to create (quickly) some reports wich partially 'overlap' with Metacoda outputs. However, the display interface would not be fully integrated with the SMC, which is a critical feature only Metacoda provides. The (re)developing cost of such Java Interface (SMC JAva Plug-in + OMI Java API) alone would - in my opinion - justify the purchasing order for metacoda own plugins. As a personal note, before Metacoda added the Role/Capacity plugins to their collection, I had tried some years ago to develop independently reports about users/groups and roles/capacities using only Proc Metadata ; the SAS OMI Java interface was absolutely required, and since I don't speak javanese very fluently (to say the least) I postponed indefinitely. Then Metacoda showed me their Role/Capacity reporting tools and I gave up altogether wasting anymore time with my coding.   ... View more

On second glance, I noticed on your screen shot that some of your SAS Foundation folders were dated back to March 2015 (?).   - Is your SAS installation a M2 or a M3 release ? Support of SAS 9.4 on Windows 10 began with M3 release, which was shipped by August/September 2015 if not later (as far as I can remember).   https://support.sas.com/supportos/list   Correspondingly, it seems that JRE 1.7 support on Windows 10 was introduced by Oracle with update release 085 :   http://www.oracle.com/technetwork/java/javase/config-417990.html   FYI, on a SAS M3 release at my office, the SAS Private JRE installed has an update release 076 (gasp!).   Try display yours with   <SAS PRIVATE JRE HOME>\bin\java.exe -version    16th, March UPDATE   a SAS note explaining the recourse to 8.3 short names in this case :   https://support.sas.com/kb/17/004.html     The problem is caused by the spaces that are included in the location of the SAS .jar files. Some of the JRE options in the SAS config file include paths that contain spaces, and these paths do not resolve properly in the JAVA compiler. The -JREOPTIONS uses !SASROOT, which contains a space by default. To avoid the SAS crashes, alter the SASROOT variable as follows: [replace long names with 8.3 short names] ... View more

The Note no. 44853 I mentioned above may give you further hints to go on.   I suppose that the following code issues some errors as well :   Proc JAVAINFO; RUN; Try to test the Private JRE provided with SAS Foundation.   This note gives you the new JAVAHOME used internally with SAS :   https://support.sas.com/kb/48/548.html     SAS Technical Support could be the next one to ask !   PS. a very "sensitive" Firewall/Security software might be reluctant to let SAS process launch Java.exe sub-processes. Please, check also with the corresponding logs/trace if its available. ... View more

  ERROR: The Java proxy is not responding. ERROR: The Java proxy's JNI call to start the VM failed. ERROR: Java failed to start during the SAS startup. As far as I know, this messages relate to a little-known pre-requisite of SAS on Windows : 8.3 short naming must be enabled on the NTFS partition where SAS Foundation is installed.     NOTE: As a SAS system requirement, the 8.3 filename convention must remain enabled.   source : https://support.sas.com/kb/44/853.html   Try running in your sas session :     Proc options option=JREOPTIONS;  run; The Java.class.path is assigned using the old 8.3 (also called "8dot3" in Microsoft plaintalk) convention : 8 characterss max. length with ~ as suffix separator.   display your sasroot : %put %sysget(SASROOT);   then try to run inside a CMD.exe the following command :   C:\users> DIR /X <SASROOT> If the penultimate colum, is empty then 8.3 short names are disabled.   See also : https://support.microsoft.com/en-us/help/121007/how-to-disable-8.3-file-name-creation-on-ntfs-partitions   You must have (local) admin privilege in order to run fsutil. ... View more