MVSFORUMS.com

ed.sam13 · Beginner Joined: 09 Aug 2010 Posts: 31 Topics: 11

I am passing a CLOB from a Cobol program to a native Stored Procedure.

This is my SP input variable declarationion.

ed.sam13 · Beginner Joined: 09 Aug 2010 Posts: 31 Topics: 11

Actually it is good only until occurrence 348. When I populate 349th occurrence, the full CLOB is not getting to the SP. Its getting truncated.

William Collins · Supermod Joined: 03 Jun 2012 Posts: 437 Topics: 0

And the definition of WS-LIMIT is?

Interesting that it is in the LINKAGE SECTION, from the prefix, but that's not part of the problem.

ed.sam13 · Beginner Joined: 09 Aug 2010 Posts: 31 Topics: 11

The definition of WS-LIMIT is 9(04). I suspect that there is a 1MB limit set somewhere which is causing this issue. When it is 3000*349 it crosses the 1MB limit. I tried increasing the REGION parameter but of no help.

kolusu · Posted: Sun Oct 18, 2015 9:39 pm Post subject:

ed.sam13 · Beginner Joined: 09 Aug 2010 Posts: 31 Topics: 11

hi Kolusu, nope. WS-LIMIT just tells me how many occurrences of the array should be filled before calling the SP. The max value for WS-LIMIT could only be 500.

Ok so the logic in the program is as follows.
1) The size of each occurence of the array is 3000 bytes.
2) I get the value of WS-LIMIT from JCL and validate that the value is within 500. For example lets say I pass a value 400
3) So the program understands that 400 occurrences of the array should be passed to the SP.
4) So it populates 400 occurrences of WS-IN-BATCH in the code above.
5) Before calling the SP I move these 400 occurrences as a CLOB to the SP. To set the length of the CLOB I multiply 3000 * WS-LIMIT which in this case is 3000*400 = 1,200,0000 which is within the limits of a CLOB.

But the issue is when I pass WS-LIMIT as 400 I get SQLCODE -433. The call to the SP and the subsequent processing is good for WS-LIMIT until 348. For any value above 348 I am getting SQLCODE -433 while calling the SP.

I hope I explained it pretty well.

William Collins · Supermod Joined: 03 Jun 2012 Posts: 437 Topics: 0

It may be within the limits of a CLOB, but is it within the limit of your CLOB. The default size if not specified is one megabyte. Too much of a coincidence. You need to specify your maximum length on the definition. CLOB max is 2GB, so you should be OK.

ed.sam13 · Beginner Joined: 09 Aug 2010 Posts: 31 Topics: 11

Thanks. When I changed the definition of the field from CLOB to CLOB(3M) it worked