Date:         Fri, 23 Apr 2010 10:51:06 -0400
Reply-To:     Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM>
Subject:      Re: Accessing local Windows SAS/Share-server from z/OS
Comments: To: Søren Lassen <s.lassen@POST.TELE.DK>
Content-Type: text/plain; charset=ISO-8859-1

Hi Søren,

Thanks, found the services file and a suitable alias+port. Both spawner and
SAS/Share-server on my PC now works.

One idea is to test whether using the CPU on a local PC instead of the CPU
on the MVS is an option, when data and source-code is on the MVS, that is
when the need for CPU is more important than I/O. The SAS-program on the MVS
is then rsubmitted to the PC etc.

Good to hear from you, by the way.

Regards,
Jesper

On Fri, 23 Apr 2010 01:57:51 -0400, S=?ISO-8859-1?Q?=C3=B8ren?= Lassen
<s.lassen@POST.TELE.DK> wrote:

>Jesper,
>I haven't tried it, but the online help (SAS 9.1) says:
>"To use the TCP/IP access method, you must verify that a SAS/SHARE server
>ID has been added to the TCP/IP SERVICES file. To find the location of the
>SERVICES file for your operating environment, see Communications Access
>Methods for SAS/CONNECT and SAS/SHARE and the documentation for your TCP/IP
>software."
>
>In other words, you need to find the TCP/IP services file on the
>z/OS machine, and add the TCP/IP address of the Windows server
>there (I seem to remember that the file has a prefix of
>SYS1.TCP or SYS1.TCPIP or maybe something with SYS2 - it may depend
>on the actual system setup).
>
>You will probably not have authourization to do this yourself,
>so you will have to contact the system guys.
>
>Hope this is helpful,
>Søren
>
>
>On Thu, 22 Apr 2010 04:14:41 -0400, Jesper Sahner Pedersen
><jespersahner@HOTMAIL.COM> wrote:
>
>>Hi,
>>
>>I am starting a local Windows SAS/Share-server like this:
>>libname dat 'c:\dat';
>>options comamid=tcp;
>>proc server id=sasserv authenticate=optional;
>>run;
>>
>>From another local Windows SAS-session I can then access data like this:
>>libname x slibref=dat server=sasserv;
>>
>>My question now is how I can access data from a z/OS SAS-session?
>>
>>Regards,
>>Jesper