This is a little weird situation that happens when we have a heavy activity (I mean lots of Stored Procedures running at the same time) on the system.
One of our Stored Procedures get a S0C4 when it moves a CLOB variable defined in linkage Section to a working storage variable.
Joined: 23 Nov 2006 Posts: 19270 Location: Inside the Matrix
Again we don't get this error always it just happens once in 100 runs
Which indicates that the code has a problem with some particular data content. . . Something is going "out of bounds" and you (your organization) are the only one with all of the tools/info needed to resolve. . .
How did you arrive at the size of group-10?
Have you queried the table to make sure that none of these clob columns are larger than expected?
As an experiment, add a new 01 that is inserted after the "group-record-area". I'd use 1 meg for the first test and adjust to see what is really needed. . .