To enable SAS Enterprise Guide to access remote data from a SAS/CONNECT spawner or server, follow these steps:

1. Execute the SAS/CONNECT signon code from a code node/code window on either a local SAS session or a WORKSPACE server (IOM server) on a host that has SAS/CONNECT licensed.


2. The SAS/CONNECT signon code might need to be altered, because you cannot be prompted for a remote user ID and password.



Here is an example:

OPTIONS COMAMID=TCP; SIGNON remotehost.spawner USER=xxxxxx PASS=yyyyyyy;


If you are performing a scripted SIGNON, the CONNECT script can be altered to either use macro variables that are previously set to the remote user ID and password or to hardcode the remote user ID and password in the CONNECT script:
OPTIONS COMAMID=TCP; FILENAME RLINK 'connect\scriptile.scr'; SIGNON;
3. As an alternative to hardcoding remote user IDs and passwords, you can create a custom SAS Enterprise Guide add-in task to handle prompting of the remote user ID and password and building the CONNECT Signon code. For details about creating a SAS Enterprise Guide Custom Add-in, see the following documentation:


• SAS Enterprise Guide documentation page
• Creating Custom Add-In Tasks for SAS Enterprise Guide
4. If you are using SAS Enterprise Guide 4.1, there is another way to handle the prompting for a remote user ID and password. With SAS Enterprise Guide 4.1, the Parameter Manager (new in SAS Enterprise Guide 4.1) can handle the prompting for the user ID and password and other parts of the Signon code.

From SAS Enterprise Guide 4.1, complete these steps to use the Parameter Manager:
Select Tools ► Parameter (Macro Variables) Manager ► Add ► General Tab Display name: Remote Userid Code name: ruser Description: <optional> Data Type: String Select Data Type and Values Tab Data Type: String Data Value Types: Any String value is allowed Defalut Value: blank Options: make sure "Prompt for Values" is checked
5. You can then add additional parameters for the password and even the host name or TCP portno. For the password, you can set the options not only to prompt but also to mask the value on input. You can add that the prompts must be required. For remote host names, you can specify that for the Data Value Type, the value must be selected from a list of values (such as for PROD and TEST systems).


6. After creating the parameters, you should do the following:
1. From the code node window, right-click.
2. Select Properties.
3. Select Parameters in the left frame, and add any parameters that you want to apply to the code node window.
4. Rearrange the prompts with the arrows on the right side when selecting parameters to apply.
5. Return to your code node/window and substitute the macro variables such as &ruser for the USER= parm. So the end result code for CONNECT Signon might look similar to the following:
SIGNON &rhost USER=&ruser PASS=&rpass;
6. When you save the code node, the parameters are not saved. The parameters ARE saved with the code node when you save the project.




Operating System and Release Information

Product Family	Product	System	Product Release		SAS Release
			Reported	Fixed*	Reported	Fixed*
SAS System	SAS Enterprise Guide	Microsoft Windows XP Professional	3.0		9.1 TS1M0
		Microsoft Windows NT Workstation	3.0		9.1 TS1M0
		Microsoft Windows 2000 Professional	3.0		9.1 TS1M0
		Microsoft Windows 2000 Advanced Server	4.1
		Microsoft Windows 2000 Datacenter Server	4.1
		Microsoft Windows 2000 Server	4.1
		Microsoft Windows Server 2003 Datacenter Edition	4.1
		Microsoft Windows Server 2003 Enterprise Edition	4.1
		Microsoft Windows Server 2003 Standard Edition	4.1
		Windows Vista	4.1
		Microsoft Windows XP 64-bit Edition	4.2
		Microsoft Windows Server 2008	4.2
		Windows 7 Enterprise 32 bit	4.2
		Windows 7 Enterprise x64	4.2
		Windows 7 Home Premium 32 bit	4.2
		Windows 7 Home Premium x64	4.2
		Windows 7 Professional 32 bit	4.2
		Windows 7 Professional x64	4.2
		Windows 7 Ultimate 32 bit	4.2
		Windows 7 Ultimate x64	4.2
		Windows Vista for x64	4.2
		Microsoft Windows Server 2003 Datacenter 64-bit Edition	4.3
		Microsoft Windows Server 2003 Enterprise 64-bit Edition	4.3
		Microsoft Windows 8 Enterprise 32-bit	5.1
		Microsoft Windows 8 Enterprise x64	5.1
		Microsoft Windows 8.1 Enterprise 32-bit	5.1
		Microsoft Windows 8.1 Enterprise x64	5.1
		Microsoft Windows Server 2008 R2	5.1
		Microsoft Windows Server 2012 R2 Std	5.1
		Microsoft Windows Server 2012 Std	5.1
		Microsoft Windows 8 Pro 32-bit	6.1
		Microsoft Windows 8 Pro x64	6.1
		Microsoft Windows 8.1 Pro 32-bit	6.1
		Microsoft Windows 8.1 Pro x64	6.1
		Microsoft Windows Server 2008 for x64	6.1
		Microsoft Windows Server 2012 Datacenter	6.1
		Microsoft Windows Server 2012 R2 Datacenter	6.1
		Microsoft Windows 10	7.1

* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.