Originally posted by: SystemAdmin

Would anyone know why the v8.2.0.5 Batch Adapter running on XP wouldn't recognize the XCOPY within a batch file? It's like WTX just skips over the just that particular command. The batch file works perfectly from a command prompt. Also, I am able to echo the XCOPY command to see that it is getting to the point in my script. Just odd.

Thanks and frustrated!
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: GerryCullen

This is not a problem unique to WTX, but relates to a known problem with certain older DOS commands. Certain DOS commands (i.e., find, xcopy) will fail when run as a service (or with no stdin/stdout) due to requiring STDIN to be present, even though they require no input in the manner they're being used.

I'm fairly certain that you will be able to resolve this by providing a very basic level of stdin support to XCOPY by echoing a few bytes of data ("echo.") and piping to the command being executed. For example, in your batch file, instead of:

xcopy /c /d /e /k /r /v /y C:\tmp\dir1 C:\tmp\dir2\

try:

echo. | xcopy /c /d /e /k /r /v /y C:\tmp\dir1 C:\tmp\dir2\

For additional details:

• http://blogs.msdn.com/khen1234/archive/2005/04/25/411837.aspx

Ken Henderson's WebLog - Subtle bugs #2

• http://www.autoitscript.com/forum/index.php?showtopic=18285

AutoIt Forums > AutoIt v3 > General Help and Support > StdoutRead, Problem When Compiled
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

Adding the "echo. |" in front of my XCOPY worked like a charm! I should have asked yesterday as your reply would have saved me a ton of time. Thank you!
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange