LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (May 2001, week 2)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Tue, 8 May 2001 15:05:04 +0200
Reply-To:     Andrea Magatti <magatz@YAHOO.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Andrea Magatti <magatz@YAHOO.COM>
Subject:      Was: SAS and Samba...again

This time i'm trying to be more clear:

The architecture "now":

Compute Server: on a Sun Solaris server (E6500)

Client: Win NT 4, using client SAS from a local File Server. that means: each time a client calls SAS.EXE this has to be retrieved from the local file server, the same appens for each DLL pointed by a SAS module (AF, GRAPH, EIS etc...). This way each client has a pure "SAS client installation".

I would be pleased to know wheter: 1) can i put the SAS executable on a Samba network drive. This way i can point a logical drive to the Samba share on th Sun Solaris machine, avoiding this way to use the File Server (too busy for "real" file sharing) 2) has anyone tested this kind of architectural, with an heavy SAS application (AF developed) , with a lot of client server interaction ?

Thanks in advance (first to Kasten....)


Back to: Top of message | Previous page | Main SAS-L page