TS-344

General Signon Steps for SAS/CONNECT's TCP/IP Access method

1) OPTIONS REMOTE=remote_hostname COMAMID=TCP;

where REMOTE_HOSTNAME is:

• - the REMOTE node name, if 8 or less characters,
  OR
• - a macro variable, which was created using the %LET statement,
  that contains the remote IP address or node name.

%LET MYNODE=remote_internet_address;

            example:  %LET MYNODE=XXX.XX.XX.XX;
                       (where mynode can be any name of your choice)
                       (and xxx.xx.xx.xx is the actual remote IP address)
                       (NOTE: There are no quotes around the IP address)

            Then submit:
	    
            OPTIONS REMOTE=MYNODE COMAMID=TCP;
                       (where mynode is the macro variable name created)
                       (with the %let statement)

            (NOTE: Do NOT insert an ampersand before the macro variable.)

2) FILENAME RLINK '!SASROOT\CONNECT\SASLINK\TCPxxx.SCR';

          where !SASROOT is the SAS directory and
          TCPxxx.scr is the TCP script file being used.

          Sample script files are located in the !SASROOT\CONNECT\SASLINK
          subdirectory.

            EXAMPLE: FILENAME RLINK 'C:\SAS\CONNECT\SASLINK\TCPVMS.SCR';
		
		Sample scripts are: 
			For windows remote hosts - TCPWIN.SCR
			For mvs remote hosts - TCPTSO.SCR
 			For unix remote hosts - TCPUNIX.SCR

3) SIGNON;

II) If the SAS/CONNECT Signon fails perform the following steps:
1) Invoke SAS and submit the following statements:

              OPTIONS REMOTE=MYNODE COMAMID=TCP SET=TCPDEBUG 30;
              FILENAME RLINK '!SASROOT\CONNECT\SASLINK\TCPxxx.SCR';
              SIGNON;

2) A TCPDEBUG.DAT file will be created in the SAS directory. In order to determine the problem area in the SAS/CONNECT session, please send the SAS log and TCPDEBUG.DAT file via email to support@sas.com.