Avoid calling sh.exe

taylor.hermann · Post by **taylor.hermann** » Wed Oct 08, 2014 6:55 am

Hi,
This is somewhat of a jump off my old post, but a new topic in general.

viewtopic.php?t=153463

We've found out that "sh.exe" is causing issues and breaking jobs randomly. Is there a way to avoid calling it without switching to unix? Any ideas are appreciated.

Thanks,

ray.wurlod · Post by **ray.wurlod** » Wed Oct 08, 2014 3:13 pm

Depends. Why are you calling it?

taylor.hermann · Post by **taylor.hermann** » Thu Oct 09, 2014 6:36 am

Well..... That's what we are trying to figure out honestly. IBM told us setting "APT_PM_USE_STANDALONE_EXE = 1" would avoid calling it. But its still popping up in process explorer and is causing clients to crash and breaking jobs.

chulett · Post by **chulett** » Thu Oct 09, 2014 7:17 am

Then it seems you should continue to work with IBM, tell them they provided an incomplete (or incorrect) solution.

taylor.hermann · Post by **taylor.hermann** » Thu Oct 09, 2014 7:35 am

Yeah, we still are. They just have not been super helpful sadly. I figure I'd just try to exhaust as much resources as possible in the mean time.

chulett · Post by **chulett** » Thu Oct 09, 2014 9:10 am

I don't think the percentage of people running Windows servers is all that high out there so not sure how many people here could really help. Expecially with something odd like this.

ray.wurlod · Post by **ray.wurlod** » Thu Oct 09, 2014 3:41 pm

Track down whether it's you at fault. For example look for ExecSH as a before/after subroutine, look for DSExecute called with "SH" as the shell argument from your routines. If you eliminate these possibilities you have a stronger case to take back to IBM.

taylor.hermann · Post by **taylor.hermann** » Fri Oct 10, 2014 7:19 am

Neither one of these things are the case. This is the strangest error I've encountered :/