topic Re: Unable to call a SAS Code through Batch command in Developers

Unable to call a SAS Code through Batch command

dpullarkat — Tue, 15 Mar 2016 14:01:37 GMT

Hi,

I have already seen the following post on the SAS communities regarding this issue and othes as well, but none of the solutions are working for me:

https://communities.sas.com/t5/SAS-Stored-Processes/Batch-Process-Throwing-Error/m-p/188757/highlight/true#M2912

This is the code which I am using:

"C:\Program Files\SAS93\x86\SASFoundation\9.3\sas.exe" –sysin "C:\Users\pullarkd\Documents\Work\SAS Models\Models 1.5\SAS_Models_Macros.sas" -nosplash -icon

And this is the error I am getting -

Would be helpful if some can tell me where I am going wrong.

I am sure that the SAS code is accurate, since it runs and when I right click the code and select "Batch Submit", it works.

Thanks,

Deepthi

Re: Unable to call a SAS Code through Batch command

JuanS_OCS — Tue, 15 Mar 2016 14:06:17 GMT

Hi,

just a wild guess, but I can see a different "minus sign"on the sysin and the nosplash and icon parameters, which I could see many times on copy and paste from windows.

If you run this from the command line, try to type it by hand, replacing the "-" signs by your keyboard's "-" sign.

Re: Unable to call a SAS Code through Batch command

Timmy2383 — Tue, 15 Mar 2016 14:07:08 GMT

I'm not as familiar with Windows installations, and maybe this is just a typo in the post, but is there a reason you're using the M-dash (long dash/hyphen) instead of the n-dash (single/short dash/hyphen) for the SYSIN option?

Re: Unable to call a SAS Code through Batch command

TomKari — Tue, 15 Mar 2016 22:08:37 GMT

And as one more follow-up to the previous two, I've seen a LOT of problems from any code associated with SAS that has been edited in MS-Word. Word tends to use "pretty" punctuation symbols, which SAS doesn't recognize. In addition to the dashes, watch out for single and double quotes.

Tom

Re: Unable to call a SAS Code through Batch command

dpullarkat — Thu, 17 Mar 2016 12:12:19 GMT

Juan and Timmy,

Thanks for your suggestions, but it wasn't the hyphen or dash. Instead it was the quotes. I ended up replacing the double quotes with single quotes.

Thanks again!