|Date: ||Thu, 12 Jun 2003 15:03:18 -0700|
|Sender: ||"SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>|
|From: ||"David L. Cassell" <cassell.david@EPAMAIL.EPA.GOV>|
|Subject: ||Re: Systask not closing|
|Content-type: ||text/plain; charset=us-ascii|
Mek Simon <sas_geek@YAHOO.COM> wrote:
> I am executing this command in SAS Batch on a Windows 2000 machine
> systask command 'copy c:\junk\ecorates.xml c:
> I am getting the following message
> NOTE: Task "task0" produced no LOG/Output.
> This does not cause the SAS job to end till I click on the OK
> which is difficult since this job runs multiple times overnight.
If you are running multiple instances of external tasks at night,
then you ought to consider putting in more error-handling. What if
one of the files is locked, or in use at the time? While you can KILL
your systask jobs, you can also skip using systask at all.
My personal recommendation would be to use Perl to do the sysadmin
tasks all in one job, using error-handling to record any problems
and send off an email to you about the success or failure of these
However, you could just as easily compile all of these files to
be checked in SAS (look at the fopen() call and related functions) and
then copied all at once. You could even use a data step to build the
list of commands to be pumped out to a sysadmin task.
David Cassell, CSC
Senior computing specialist