The response back from customer support is that there is a hotfix/patch for a totally different problem that seems to also clear up some "call execute" issues as a side benefit.
I have put in a request with our people to obtain and apply the patch, but I'll have to way a number of days for the change management process to do its thing.
As a work around, per support's suggestion, I am going to us a temp file and %include to mimic the call execute affect. This is simple is all I have to do is
[pre]
* call execute(statement);
file tempfile;
put statement;
file log;
...
run;
quit;
%include tempfile;
[/pre]
For the four affected data steps.
Well, not quite that simple, I had to make some minor changes to the creation of statement as will, but nothing huge.
Thanks for the note Peter.C
The generated lline is < 255 characters, but, that doesn't mean that there isn't some sort of wrapping occurring.
The problem isn't showing up an every line, and some lines are longer than ones being corrupted.
I think it may have something to do with the total buffer space for something within SAS. My test run yesterday produced only one error, whereas last week, I was getting 3 of them.
Message was edited by: Chuck