Date: Fri, 19 Apr 2002 08:38:42 -0700
Reply-To: Mark Terjeson <mark.terjeson@NWCSR.COM>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Mark Terjeson <mark.terjeson@NWCSR.COM>
Subject: Re: scheduler command failure
In-Reply-To: <a9lpnp$tse$04$1@news.t-online.com>
Content-Type: multipart/alternative;
Hi Andreas,
Please note the phrase in my commentary: "even if you quote it".
This is no feature, this is a bug! I've seen several true experts
that have had to conceed to it. This problem does exist on NT and
W2000. It is reproduceable. I typically don't make guesses, I
prefer to only post confirmed scenarios. This problem identification
has helped a number of people. Unfortunately, this particular item
doesn't solve Mohandas' problem. Thanks for being on your toes
though.
Dear Mohandas,
We'll keep trying to think of something that might help........
Mark
-----Original Message-----
From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of
Andreas Grueninger
Sent: Wednesday, April 17, 2002 11:40 PM
To: SAS-L@LISTSERV.UGA.EDU
Subject: Re: scheduler command failure
Dear Mark,
that is not a bug, it is a feature...
> "C:\Program Files\SAS Institute\SAS\V8\sas.exe"
> -CONFIG "C:\Program Files\SAS Institute\SAS\V8\SASV8.CFG"
> -sysin
It is clearly stated in the documentation that pathnames/filenames with
embedded spaces must be enclosed in quotes. The parser for the command
line must know when the value of a parameter ends. The delimiter is the
white space. The quotes mark the embedded white spaces as NON-delimiter.
I can't beleive that there is a difference between a batch started on
the console prompt and a scheduled job started via a scheduler program.
I do a lot batch processing with scheduler programs and this would be
very surprising for me. Could you give an example for this?
"Mark Terjeson" <mark.terjeson@NWCSR.COM> schrieb im Newsbeitrag
news:000101c1e65b$c353b560$62a7efc6@bedemere...
> Hi Mohandas,
>
> This may not be your exact problem, but one issue
> very close to this is that there is a bug in the
> Windows operating system when you have scheduled,
> batched jobs. On most Windows operating systems
> (such as Win95, Win98, NT, Win2000, etc.) if you
> invoke a command line that has pathnames containing
> spaces, the command will work fine at the DOS prompt,
> but when you schedule batch jobs, the o/s will have
> a failure when any part of the path contains a space,
> even if you quote it with double quotes. (e.g the
> MS o/s can't even handle it's own "Program Files"!!!)
> You can test for this to see if it is part of your
> situation by copying the .exe,.sas,.cfg into a
> directory path that contains no spaces.
> For example: in your sample command below:
>
> "C:\Program Files\SAS Institute\SAS\V8\sas.exe"
> -CONFIG "C:\Program Files\SAS Institute\SAS\V8\SASV8.CFG"
> -sysin
> D:\Sas\intrnet\pgms\Data_Warehouse\Jdfr_sas\JDFR00_DAILY_MASTER.sas
> -NOSPLASH -ICON
>
>
> copy the sas.exe and your sasv8.cfg and your JDFR00_DAILY_MASTER.sas
> into a directory with no spaces:
>
> mkdir c:\mydir
> copy "C:\Program Files\SAS Institute\SAS\V8\sas.exe" c:\mydir copy
> "C:\Program Files\SAS Institute\SAS\V8\SASV8.CFG" c:\mydir copy
> D:\Sas\intrnet\pgms\Data_Warehouse\Jdfr_sas\JDFR00_DAILY_MASTER.sas
> c:\mydir
>
>
> and then try an adjusted command: e.g.
>
> "C:\mydir\sas.exe"
> -CONFIG "C:\mydir\SASV8.CFG"
> -sysin c:\mydir\JDFR00_DAILY_MASTER.sas
> -NOSPLASH -ICON
>
>
> Just as your source program path contains no spaces
> what I did was create a secondary directory called c:\sasv8 that
> contained sas.exe and SASV8.CFG that were called upon when the
> scheduler command lines run and then everything was happy. This
> served two purposes, 1) no spaces in the path names, and 2) much
> shorter command line lengths so I could stay under the short command
> line lengths of 98 and NT.
>
> Again, your problem may be different, but whenever I hear someone say
> the command line works from the DOS prompt and not from the scheduler,
> this has been the problem 8 out of 10 times.
>
> One additional note: the command line text box in several schedulers
> for 98 and NT are limited to something like 210 characters, (I've
> forgotten the exact number) and in Win2000 the limit of characters is
> much higher. Be careful if you copy/paste between them because the
> command line can get truncated.
>
>
> Food for thought,
> Mark Terjeson
> NWCSR, Inc.
>
>
>
>
>
>
>
>
>
>
> -----Original Message-----
> From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of
> Sundareswaran Mohan
> Sent: Wednesday, April 17, 2002 2:16 PM
> To: SAS-L@LISTSERV.UGA.EDU
> Subject:
>
>
> I was trying to run a Sas file using a .bat file . which contains as
> below "C:\Program Files\SAS Institute\SAS\V8\sas.exe" -CONFIG
> "C:\Program Files\SAS Institute\SAS\V8\SASV8.CFG" -sysin
> D:\Sas\intrnet\pgms\Data_Warehouse\Jdfr_sas\JDFR00_DAILY_MASTER.sas
> -NOSPLASH -ICON
> When i was trying to run the job i was able to invoke sas but was not
> able to run the part -CONFIG "C:\Program Files\SAS
> Institute\SAS\V8\SASV8.CFG" -sysin
> D:\Sas\intrnet\pgms\Data_Warehouse\Jdfr_sas\JDFR00_DAILY_MASTER.sas
> I was using a third party scheduler called maestro to run the same ..
> i was getting the error
> ERROR: Invalid physical name for library SASUSER.
> FATAL: Unable to initialize the options subsystem.
>
> (SASXKINI): PHASE 3 KERNEL INITIALIZATION FAILED.
> UNABLE TO INITIALIZE THE SAS KERNEL
>
> Can any one help me with this
>
> Mohandas
[text/html]
| 
