Date: Tue, 12 Oct 1999 20:00:43 GMT
Reply-To: Andreas Grueninger <grueninger@IBGRUENINGER.DE>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Andreas Grueninger <grueninger@IBGRUENINGER.DE>
Organization: Customer of UUNET Deutschland GmbH, Dortmund, Germany
Subject: Re: WIN2000 TELNET SAS Sessions
To start SAS jobs on a remote NT workstation / NT server / WTS/
WinFrame / MetaFrame
the following can be used.
Without licencing of SAS/IntraNet, SAS/Connect, AppDev etc.
Character based access
1. Remote Command Shell of the NT Resource Kit. You have to use a NT
system as local system. There are two flavours. The older takes the NT
account from the local system to login in the remote system. The newer
fersion gives you the chance to use another NT account.
2. Telnet Server from the NT Resource Kit and a Telnet client from the
local system. Not very stable.
3. A commercial Telnet Server e.g. from Seattle Laboratories. When I
tried it it was very stable. Much more better than the MS tool.
WTS / WinFrame / MetaFrame gives you the GUI from the remote machine
on your local system (like MVS and 3270 screens or Unix and
X-Windows). The disadvantage is that you have to pay for a SAS NT
Job starting without a telnet or command shell
NT schedule service ("AT")
If you have administrator rights you can start batch jobs on a remote
NT machine using the schedule service. All jobs are started under the
account which the schedule service is using (default: SYSTEM). This is
the poor man's RJE system.
BatchJobServer BJS (http://www.camelliasoftware.com)
BJS enables you to start batch jobs on a remote machine with the BJS
engine installed. The jobs are started on your NT account. A job
database and a scheduling is integrated. Very well suited for