topic Re: Issue running a .cmd file using %sysexec. in SAS Programming

Issue running a .cmd file using %sysexec.

KJ_SAS — Thu, 19 Jan 2017 17:23:54 GMT

I have a file called outer.cmd. That file calls inner.cmd. I use the %sysexec command to call outer.cmd. However I recieve the error "inner.cmd is not recognized as an internal or external command" when SAS 9.3 runs the outer program. Is there a way around this?

Re: Issue running a .cmd file using %sysexec.

LinusH — Thu, 19 Jan 2017 19:24:37 GMT

Does it work if call outer outside SAS (from the same directory/user/etc)?

Re: Issue running a .cmd file using %sysexec.

KJ_SAS — Thu, 19 Jan 2017 20:11:51 GMT

The outer.cmd file calls and runs the inner.cmd file correctly if I run it outside SAS.

Re: Issue running a .cmd file using %sysexec.

Kurt_Bremser — Thu, 19 Jan 2017 21:12:33 GMT

My first guess would be to use fully qualified path names in the outer.cmd. inner.cmd is probably in a place not included in your %path%.

Re: Issue running a .cmd file using %sysexec.

KJ_SAS — Fri, 20 Jan 2017 13:53:16 GMT

Thank you. This suggestion fixed my issue. Even though both files are in the same folder calling the inner file like " call inner.cmd" didn't work. Instead I needed to call it like so " call "C:\Users\user\Documents\inner.cmd" ".

Re: Issue running a .cmd file using %sysexec.

Kurt_Bremser — Fri, 20 Jan 2017 15:00:28 GMT

You probably used a fully qualified path name for outer.cmd. But that does not imply a change directory to its location. UNIX shell scripts do often extract the path from the called commandline and change to it for that reason.