The CICS Application Programming Reference
manual is quite clear about RESP2 11 on a RESP 22 for a READ:
11 The length of a record read with the INTO option specified exceeds the value specified in the LENGTH option; the record is truncated, and the data area supplied in the LENGTH option is set to the actual length of the record.
You attempted to read a record longer than the maximum value in the LENGTH option. There are many possible reasons for this, including (but by no means limited to):
1. Program compile failed
2. Program compile worked but load library is not in CICS region DFHRPL
3. Program compiled and went to a load library in the CICS region DFHRPL, but the NEWCOPY failed
4. Program memory was corrupted by a table overflow
5. VSAM data set has records longer than you allowed for
At this point, since the data and the program reside at your site, you need to do some debugging. First, assume the computer is not lying to you -- which means that WHATEVER you had in the LENGTH variable before the READ, it was not long enough. I would start debugging by confirming the program compiled with a zero return code, the correct load library was specified, and that the NEWCOPY worked -- unless you do these preliminary steps, you have no guarantee you are debugging the right code (and a surprisingly large number of issues are resolved by doing these steps and finding something went wrong). Once you've done that, use the debugging tools at your site (or CEDF if nothing else) to look at the READ command being executed and the parameter values as they exist when the READ statement is executed. If you still cannot find the issue, we'll need to see actual data such as CEDF screen shots to proceed.