Date: Thu, 26 Apr 2001 16:21:36 -0400
Reply-To: "Whittier, Sarah" <SWhittier@ISO-NE.COM>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: "Whittier, Sarah" <SWhittier@ISO-NE.COM>
Subject: FW: Problem running jobs from Windows Scheduler
I pasted the wrong section of the log from batch in my original message.
Here is the correct excerpt. Thanks to the reader who pointed this out to
me.
Log excerpt from batch submit:
data WORK.tempcoal;
331 infile 'c:\windows\desktop\fuel price
data\coaldata.csv' DLM=',' DSD
331 ! FIRSTOBS=2 ;
332 length Name $180;
333 length Ticker $10;
334 length RIC $15;
335 informat Flow_Date date.;
336
337 input Name $ Ticker $ RIC $
338 Flow_Date High Low Best_estimate;
339 RUN;
NOTE: The data set WORK.TEMPCOAL has 0 observations and 7 variables.
NOTE: DATA statement used:
real time 0.00 seconds
Sarah Whittier
Wholesale Electricity Markets Analyst
ISO New England
-----Original Message-----
From: Whittier, Sarah
Sent: Thursday, April 26, 2001 3:43 PM
To: 'sas-l@listserv.uga.edu'
Subject: Problem running jobs from Windows Scheduler
We are using 8.1 on Win 98. I am having some problems with jobs that are
run in batch via the Windows scheduler . We run many jobs through the
scheduler, and most of them work fine. But I have two jobs that get errors.
The weird thing is that they work fine when submitted interactively. I can
submit one of the problem jobs interactively and have it work fine and
submit it via scheduler one minute later and get unexpected errors.
I have pasted excerpts from the batch and interactive logs from one of the
problem jobs below. SAS doesn't read any observations from the file when
running in batch. This is the simplest example of our problem -- we have
another case where a macro works fine interactively, doesn't resolve some
variables in batch.
I generally set up the batch jobs using Scheduled Tasks and putting the path
( "C:\Program Files\SAS Institute\SAS\V8\sas.exe" -sysin "C:\WINDOWS\SAS
Files\Fuel Price Data\update_daily_fuelprice.sas") into the run box. I also
tried setting up a .bat file and pointing to that, and had the same
problems.
I called tech support and while they made some suggestions, they weren't
able to solve the problem for me.
I am hoping that someone on the list may have encountered a similar problem
and have some advice for me.
Thanks.
Sarah Whittier
Log excerpt from interactive submit:
data WORK.tempcoal;
331 infile 'c:\windows\desktop\fuel price data\coaldata.csv'
DLM=',' DSD FIRSTOBS=2 ;
332 length Name $180;
333 length Ticker $10;
334 length RIC $15;
335 informat Flow_Date date.;
336
337 input Name $ Ticker $ RIC $
338 Flow_Date High Low Best_estimate;
339 RUN;
NOTE: The infile 'c:\windows\desktop\fuel price data\coaldata.csv' is:
File Name=c:\windows\desktop\fuel price data\coaldata.csv,
RECFM=V,LRECL=256
NOTE: 34 records were read from the infile 'c:\windows\desktop\fuel price
data\coaldata.csv'.
The minimum record length was 32.
The maximum record length was 161.
NOTE: The data set WORK.TEMPCOAL has 34 observations and 7 variables.
NOTE: DATA statement used:
real time 0.00 seconds
Log excerpt from batch submit:
data WORK.MATCH_FILEcoal;
346 infile "c:\windows\desktop\fuel price
data\match_filecoal.csv" DLM=',' DSD
346 ! FIRSTOBS=2;
347 length Fuel_Type $20 ;
348 length Description $126 ;
349 length Ticker $10 ;
350 input Fuel_type Description Ticker;
351 run;
NOTE: The data set WORK.MATCH_FILECOAL has 0 observations and 3 variables.
NOTE: DATA statement used:
real time 0.00 seconds
Sarah Whittier
Wholesale Electricity Markets Analyst
ISO New England
