• Print |
• E-mail  |
• Bookmark

Multiple SAS/CONNECT PC Spawners can be installed as a Service on the
same Windows host machine.

To be able to run multiple PC Spawners as a service, they must be
installed on different available TCP ports.  For example, you must
initiate the spawners from a DOS command prompt at the !  sasroot
directory using the following commands.

   !sasroot>  spawner.exe -i -c tcp -service 5010

   !sasroot>  spawner.exe -i -c tcp -service 5011

   !sasroot>  spawner.exe -i -c tcp -service 5012

In Services, you must then Start these spawner services in order to
connect to them.  Refer to TS-638 for more information on 'Installing
the PC Spawner Program'.

Once these spawners are installed and started as a Service, they will be
listed in Services as:

   SAS Job Spawner
   SAS Job Spawner #2
   SAS Job Spawner #3

To SIGNON to a SAS Job Spawner that is installed on a TCP port other
than 23 (which is default), you must use the following syntax:

options remote=hostname.port#;

For example,

options remote=hostname.5010;

If you are using a %let statement to define a macro variable to a
hostname or IP address that is longer than 8 characters, then the
syntax would be:

%let mynode=xxx.xxx.xxx.xxx 5010;
options remote=mynode;

To delete these spawners you must issue the following statements from a
DOS command prompt at the !sasroot directory:

   !sasroot> spawner.exe -d

The above statement will delete the service labelled SAS Job Spawner.

   !sasroot> spawner.exe -d -instance 2

The above statement will delete the service labelled SAS Job Spawner
#2.

   !sasroot> spawner.exe -d -instance 3

The above statement will delete the service labelled SAS Job Spawner #3


A Technical Support hot fix for Release 8.2 (TS2M0) for this
issue is available at:

http://www.sas.com/techsup/download/hotfix/82_sbcs_prod_list.html#010003

For customers running SAS with Asian Language Support (DBCS), this
hot fix should be downloaded from:

http://www.sas.com/techsup/download/hotfix/82_dbcs_prod_list.html#010003

Operating System and Release Information

A fix for Release 8.2 (TS2M0) for this issue is available at:

A fix for Release 8.2 (TS2M0) with Asian Language Support (DBCS) for this issue is available at: