Too many comments in QSQLSRC?

(yet another episode in "Novice [mis]adventures in SQL")
It seemed like such a good idea to have my Create View coded up in its own source member in QSQLSRC, so I could have that source member moved to our production repository of code, and SysAdmin could create production objects from that member with RUNSQLSTM.
And it also seemed reasonable that I could put a comment block at the top of the source member where the next poor schmuck could "check out" the source and get a sense of the method to my madness before laughing at my code.

So I have this source member with a somewhat complex Create View statement, running roughly 80 lines. My comment block was about 50 lines, including the updates history log structure, etc.

My RUNSQLSTM fails with a non-descript "Receiver value too small to hold result." (MCH1210).

I rip out all but 3 of my comment lines, and everybody's happy - no harm, no foul, no error. I thought about reinserting comments one by one to find the exact threshold of doom, but didn't.

Is this documented somewhere, that while one might expect the RUNSQLSTM to skip past any source line beginning with "--", that it might tire of skipping and trip? I did try to wrap the whole comment block thing in /* ... */, so it wouldn't have to deal with all the dashes, but that didn't work either.

So it all goes to production with three lines of comments, one of which being:
-- Add more comments at your peril!

Running OS 7.1 here.
One other item of note: The MCH1210 did not prevent creating the LF object, but experience from earlier this week tells me that when this happens when SysAdmin runs the RUNSQLSTM, the production object is flawed in some way, and fails to get created in a RSTLIB operation.

Michael Koester
Programmer/Analyst

DataEast