How to create/define SAS/CONNECT Signon script?

[apolodor]

How can I create/define SAS/CONNECT Signon script to connect to SAS 9.2?

I was told that first I have to install SAS/CONNECT and SAS/BASE utilities on the local workstation (Windows).

Thank you!

[Peter_C]

when SAS is licensed with /Connect the install creates sample scripts  on your system

[apolodor]

Could you please tell me where can I find it and how can I test it?

[Peter_C]

In a standard sas session run

%PUT %SYSGET(SASSCRIPT);

The log should show the path where the example SAS/Connect scripts are stored

Each script is designed for a particular server type and connection type. These are desxribed in the fileheaders.

[apolodor]

Thanks!

Is there a sample script file I could re-use?

Where can I find SAS/Connect scripts? Do I need to install SAS/CONNECT software? Does it come as a separate package?

[Haikuo]

In my default CFG file, SASSCRIPT was set as a SAS option instead of environment variable. In that case, you can use:

%put %sysfunc(getoption(SASSCRIPT));

You do need to install SAS/Connect. No, it is usually included in your deployment depot, you just need to check it to have it included.

Haikuo

[apolodor]

Thanks Haikuo!

Well, I don't know how I could check that option.

I just installed SAS Drivers for JDBC and SAS/CONNECT for Windows so now I have some jar files under C:\Program Files\SAS\SASDriversforJDBCandCONNECT\9.1 but no script files.

[Haikuo]

To check the licensing info:

PROC SETINIT;RUN;

To check the installed components  :

PROC PRODUCT_STATUS;RUN;

You will need SAS/CONNECT both licensed and installed.

HTH,

Haikuo

[apolodor]

It looks that SAS/CONNECT is both licensed and installed.

PROC SETINIT;RUN;

Product expiration dates:

---Base Product                                                            ...

---SAS/CONNECT                                                             ...

---SAS OLAP Server                                                         ...

...

PROC PRODUCT_STATUS;RUN;

For SAS/CONNECT ...

   Custom version information: 9.21_M2

Where should I find the (sample) scripts?

Thanks!

[Haikuo]

Have you run the statement suggested by Peter or me?

I have asked you to run:

%put %sysfunc(getoption(SASSCRIPT));

This will hopefully give you the location of the sample script.

[apolodor]

I ran the ones mentioned by you

Now I executed the last command and I got:

.....

15	%put %sysfunc(getoption(SASSCRIPT));

(!SASROOT/misc/connect)

.....

However, there is no /misc/connect folder under C:\Program Files\SAS on my workstation. Should I look on the server?

[Haikuo]

Ok, so you have nested variable here, run the following to figure out what is SASROOT:

%put %sysget(SASROOT);

Please provide more details on your SAS version, OS etc on both of your PC and your SAS server.

UPDATE: Also, did you run it straight, or did you run it using rsumbit?

[apolodor]

Running %put %sysget(SASROOT) I got:

....

15	%put %sysget(SASROOT);

/sas/sas92/SASFoundation/9.2

....

There is no such folder on my workstation so I'd guess I have to look on the server.

Those commands were executed using SAS Enterprise Guide -> Program.

SAS version: 9.2

Server OS: AIX

Workstation OS: XP

[Haikuo]

Your conclusion makes sense.

If you are using EG, make sure which machine you are running on. It could be local, which in your case, it is Windows XP, if remote, depends on how many different platforms involve, for now, at least you have one server that is AIX.

BTW, out curiosity, since you already running EG, why bother resort to SAS/Connect script? EG is taking care of everything in the background without your knowing, so is there anything that 'Rsubmit' can do, while EG can't?

Haikuo

[FriedEgg]

There are still times in EG when using rsubmit makes sense as part of processes that take advantage of the MPCONNECT methods in SAS/CONNECT.  There are other reasons as well but I refrain from listing them here.