Just need to tell PowerCenter NOT to convert any '/' to '\' in the source and target type "command"on, set the following custom property at the Session(Config Object Tab) or Integration Service level:
solution is well documented here - Support
Besides the fact that this thread is 8 years old, there's a better solution:
Simply place the "/b" between "dir" and the files to search:
dir /b E:\Data\*.txt
This way the /b will not be "translated" into \b (which causes the error).
1 of 1 people found this helpful
It seems there are cases where placing /b between dir and the files to search does not work, like in this KB:
We should use the Custom Property SkipUnixToNTCmdPathConversion in these cases too.
thanks for that info, that was new to me.
Now one question about it: the KB article dates back to PowerCenter 8.6.x. Has there any more "recent" indication that this error occurs? I found this "dir /b" method to work since 9.1, so I would like to know whether writing a batch file is indeed the only method or whether the "dir /b" method is safe to use since (at least) 9.1.
Thanks a ton and kind regards,
I am also using the dir /b method and it works as expected
yes, we have a newer KB about it where points to the Custom Property as a solution:
But in this case we can't see the forward slash between dir and the list of files, so I don't know if that might be working in later versions.
In any case, the older KB should be archived as I don't think it is helpful at this point.
If this were my decision, I would leave the KB article where it is. It does note an issue which may arise for customers at any time, and the fact that it's old doesn't mean it's no longer useful.
My 2 cents.
Thanks a ton and regards,