topic Re: Autocall Library Setup in SAS Procedures

Autocall Library Setup

mmd12 — Mon, 10 Sep 2012 18:07:11 GMT

Hello --

I'm looking for some advice on setting up an autocall library correctly. I've been going through my company's current setup and it seems to be a bit messy, and in fact some SAS autocall macros are currently not working (%CMPRES is one example).

First, some specs:

SAS 9.2

Enterprise Guide 4.3

UNIX Server

Here is a highlight of the current configuration:

opt/SAS/SASFoundation/9.2/nls/en/sasv9.cfg:

-insert sashelp !SASROOT/nls/en/sascfg

-insert helploc !SASROOT/X11/native_help

-SET SASAUTOS ("**unix/macro/path/location**")

opt/biserver/Lev1/SASApp/sasv9.cfg:

/* Set Options */

-metaautoresources "SASApp"

-insert sasautos "SASEnvironment/SASMacro"

-set APFMTLIB "SASEnvironment/SASFormats"

-insert fmtsearch APFMTLIB

-rsasuser

-emailsys SMTP

-emailhost mailrelay.XXX.com

-emailport 25

-metaserver "XXX"

-metaport 8561

-metarepository "Foundation"

-metaprotocol BRIDGE

-workperms 700

/* Include autoexec files */

-autoexec "/opt/biserver/Lev1/SASApp/appserver_autoexec.sas"

opt/biserver/Lev1/SASApp/sasv9_usermods.cfg: (not sure why there is not a space between these two paths, seems incorrect)

-APPLETLOC "http://XXX.com:8080/sasweb/graph"

-SET SASAUTOS ("**unix/macro/path/location**""SASEnvironment/SASMacro")

opt/biserver/Lev1/SASApp/StoredProcessServer/sasv9_usermods.cfg:

-APPLETLOC "http://XXX.com:8080/sasweb/graph"

-SET SASAUTOS ("**unix/macro/path/location**")

Kind of messy unfortunately. Any suggestions as to how to get on solid ground?

Re: Autocall Library Setup

Ksharp — Tue, 11 Sep 2012 02:03:56 GMT

One more thing you need to confirm is that your site has these autocall macro ?

Talk to your SAS representative . Make sure of it.

Re: Autocall Library Setup

mmd12 — Tue, 11 Sep 2012 02:47:04 GMT

I'm not sure what you mean, I'll try to clairify. Yes, we have a directory of macros which are all .sas files named the same name as the macro itself. And yes, we do have the autocall macro that I was talking about (%cmpres) I know this because we have old code that has worked in the past which no longer works.

Re: Autocall Library Setup

Cynthia_sas — Tue, 11 Sep 2012 02:58:40 GMT

Hi:

I'd recommend that you work with Tech Support. The autocall macros are generally stored in a separate (and different) location for the BI servers than for your Foundation install. The BI Platform has a Lev1 subdirectory entitled SASMacro, which is where the Platform autocall macros should live. If you want your production or older macros to be available in Platform programs, then you would have to alter the search option to include that location.

However, the location for the autocall macros that you are adding to the BI search path MUST be in a location that is accessible to the BI servers. For example, you can't have your autocall macros on a Windows shared drive, also used by the BI Platform servers if that Windows location is not known to and available to the BI servers.

That's why I think you should work with Tech Support. Too many factors and too many unknowns to really give you constructive help.

cynthia

Re: Autocall Library Setup

mmd12 — Tue, 11 Sep 2012 03:18:36 GMT

I will do that. Thank you Cynthia.

Re: Autocall Library Setup

SASKiwi — Tue, 11 Sep 2012 04:09:57 GMT

Just a thought - have you checked the SAS option MAUTOSOURCE is set to ensure you can call AUTOCALL macros?

Re: Autocall Library Setup

mmd12 — Tue, 11 Sep 2012 12:59:13 GMT

SASKiwi wrote:

Just a thought - have you checked the SAS option MAUTOSOURCE is set to ensure you can call AUTOCALL macros?

Actually it doesn't look like it. Here is the entire contents of the opt/SAS/SASFoundation/9.2/nls/en/sasv9.cfg file:

This config file contains the default SAS configuration option settings

which are defined during the SAS Foundation Installation process. This file

gets recreated during SAS Installation Upgrade process therefore user

specified settings added to this file will be lost during an upgrade. With

this in mind, we strongly discourage editing this file, as the edits will

be lost on upgrade. A new configuration file named sasv9_local.cfg has

been created in the !SASROOT directory to store user specified settings.

Settings in this file will remain in place during upgrades to this SAS

Installation and will override the default options values when the same

options are contained in both places.

Default options:

-insert sashelp !SASROOT/nls/en/sascfg

-insert helploc !SASROOT/X11/native_help

-SET SASAUTOS ("**unix/macro/path/location**")