If you want to simulate another's "SAS licence combination" either use their licence, or get your SAS supplier to provide a licence to match. [I leave the commercial and legal rules to another discussion].

There is a macro function, used like %sysprod(connect) which is the official way to test for the existence of a product. It uses the setinit information. If you don't change that, the SAS components expect to be able to use facilities that might not be available to the other environment.

OK, with no pointer to the executables by removing the paths from the config file, the calls will fail, but it might be "cleaner" to get the normal message in the SASlog that the component is not licensed.

PeterC

I haven't tested this, but I'm fairly certain you can emulate a complete removal or absence of a particular module but editing the SASv9.CFG (or version appropriate version). Or, probably a safer bet, would be to create your own custom config file and invoke sas with that as a -config option.

There is a PATH config option that is set in the SASV9.cfg where each of the individual sasexe directories for the products is included in the path statement. I'm pretty certain you could remove one or more of those to completely remove that module's binary libraries from availability. See below:

/* Setup the SAS System load image search paths definition */
-PATH          (
                "!sasroot\core\sasexe"
                "!sasext0\accelmva\sasexe"
                "!sasext0\dquality\sasexe"
                "!sasext0\inttech\sasexe"
                "!sasext0\mddbserv\sasexe"
                "!sasext0\tablesrvtk\sasexe"
                "!sasext0\access\sasexe"
                "!sasext0\af\sasexe"
                "!sasext0\assist\sasexe"
                "!sasext0\connect\sasexe"
                "!sasext0\eis\sasexe"
                "!sasext0\ets\sasexe"
                "!sasext0\fsp\sasexe"
                "!sasext0\graph\sasexe"
                "!sasext0\iml\sasexe"
                "!sasext0\insight\sasexe"
                "!sasext0\intrnet\sasexe"
                "!sasext0\lab\sasexe"
                "!sasext0\or\sasexe"
                "!sasext0\qc\sasexe"
                "!sasext0\share\sasexe"
                "!sasext0\stat\sasexe"
                "!sasext0\toolkt\sasexe"
                "!sasext0\spdsclient\sasexe"
               )

So, for example, you could "disable" ETS by completely removing the line that says:

"!sasext0\ets\sasexe"

Test it out and see if it works.