Date: Wed, 7 Oct 1998 11:08:23 -0400
Reply-To: Tom.Slack@FIRSTUNION.COM
Sender: "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>
From: Tom Slack <Tom.Slack@FIRSTUNION.COM>
Subject: Scheduler problems was Re: Client/Server problems
David Collins of First Union National Bank gave me this solution to the
scheduler problem. He called SI and they sent him usage notesB859 and E613 as
follows:
Tom Slack
>------------------------------------------------------------------------------
--
> Usage Note: B859
>------------------------------------------------------------------------------
--
>
>V6-SYS.SYS-B859 USAGE NOTE
>
>Windows NT AT command not working with SAS for Windows or Windows NT
>
>Product: BASE
>
>
> Many of our users are reporting that they want to run SAS for Windows
> or Windows NT in the background with the Windows NT AT command. The
> AT command is used to schedule background processes to be run at a
> particular time. The basic syntax of the command is:
>
> AT time Job to run
> where time is the time the job should run and "Job to run" is the
> command to execute with all parameters. An example might be:
> AT 02:30 /I C:\SAS\SAS.EXE -SYSIN C:\SAS\JOB.SAS
>
> The above command will be accepted by Windows NT, but the SAS job
will
> not run, the time will elapse but SAS will not be invoked. An
> additional parameter must be used to execute SAS, the \\machinename.
> This parameter tells Windows NT which machine to run the command on.
> Without this parameter being set, SAS will never be invoked. For
> example, if the NT machine name is "NTSERVER" (this name is given
when
> NT is installed) the example given above can be modified this way:
> AT \\NTSERVER 02:30 /I C:\SAS\SAS.EXE -SYSIN C:\SAS\JOB.SAS
> and SAS should run as expected, in batch mode.
>
>
>Keywords:
> NT WNS WNT WNC AT COMMAND WINDOWS BATCH PROCESSING NONINTERACTIVE
>
>SAS Note Revised On: 25MAR98
>
>
>System Release Reported Release Fixed
>
>WIN/NT 6.09 TS027
>Windows 6.10 TS019
>Windows 6.11 TS020
>
>
>No Zaps Available
>
>------------------------------------------------------------------------------
--
> Usage Note: E613
>------------------------------------------------------------------------------
--
>
>V6-SYS.SYS-E613 USAGE NOTE
>
>NT Scheduler service unable to access remote files
>
>Product: BASE
>
>
> If a user attempts to access a remote file in a job started by the
> Scheduler service, the job will terminate abnormally. By default,
the
> Scheduler service uses the system account, and the system account
only
> has access to the local workstation. Here are some general errors
that
> may be received:
>
> OS Error 53 -
> ERROR_BAD_NETPATH; The network path was not found
> OS Error 1317 -
> ERROR_NO_SUCH_USER; The specified user does not exist
> <or>
> If the user is capturing return codes he will receive a negative
> value as the return code.
>
> Perform the following to circumvent the problem:
> - Go to "Control Panel" -> "Services" -> "Schedule" -> "Startup"
> - Change the account from "System Account" to "This Account" and
> type in the LAN logon id and password.
>
>
>Keywords:
> NT SCHEDULER SERVICE UNABLE ACCESS REMOTE FILES OS53 OS1317ERRO BAD
> NETPATH NO SUCH USER
>
>SAS Note Revised On: 06FEB98
>
>
>System Release Reported Release Fixed
>
SAS-L@UGA.CC.UGA.EDU on 10/06/98 10:06:31 AM
Please respond to Darran_Slator@NEXT.CO.UK @ INTERNET
To: SAS-L@UGA.CC.UGA.EDU @ INTERNET
cc:
Subject: Re: Client/Server problems
--------------- cc:Mail Forwarded ---------------
From: Darran Slator AT NEXT-LEEDS-PO1
Date: 10/06/98 02:48 PM
To: sas-l@uga.cc.uga.edu AT INTERNET-MAIL
Cc:
Subject: Re: Client/Server problems
--------------- cc:Mail Forwarded ---------------
From: Darran Slator AT NEXT-LEEDS-PO1
Date: 10/02/98 04:20 PM
To: sukmjs@suk.sas.com AT NEXTPLC
Cc: Ian Chambers,Mario McDonnell
Subject: Re: NT server requirments
I have forwarded a message I have sent to someone in the SAS office in
Manchester, England.
I wonder if anyone on this list could help me with my search for an NT
scheduler.
I am also having trouble remote submitting SAS X statements to kick on the
AT scheduler that comes with the server.
My PC is Windows 95 and SAS 6.12 TS level 45
The server is Windows NT 4.0 and the same SAS version.
Thanks,
Darran
______________________________ Forward Header _____________________________
_____
Subject: Re: NT server requirments
Author: Darran Slator at NEXT-LEEDS-PO1
Date: 02/10/98 16:20
Mark,
Thanks for the info.
I am sending you this message to tell you exactly what we are wanting to
do.
We need to remote submit SAS jobs, from an AF application on the PC, to an
NT server to either:
i) run straight away, if no other job is running.
ii) if a job is already running, to queue to run after current job and
other queued jobs have finished.
iii) or, the user can specify that the job doesn't need to run until 5pm
that evening. If there are multiple jobs these need to be queued and run
sequentially after 5pm.
We would also like the following facilities:
i) the server sends a message back to the user when a job has completed.
ii) the PC user can look at the server batch queue.
I am assuming we need a scheduler for some or all of these requirements but
I would appreciate any suggestions from you.
We need this information urgently, as we need to know if the above is
possible before next Friday, because our trial period for the NT server and
software expires then.
Thanks,
Darran
