How to resolve the data overlapping due to occur clause

ranjithmainframe · New User Joined: 21 Jan 2008 Posts: 39 Location: chennai

an you please help on this...

I have three arrays declared in my cobol as follows

01 ARRAY-1.
02 WS-PRO-ARRAY OCCURS 3000 TIMES.
05 WS-PRO-ARR PIC X(351).

01 ARRAY-2.
02 WS-ADD-ARRAY OCCURS 3000 TIMES.
05 WS-ADD-ARR PIC X(194).

01 ARRAY-3.
02 WS-CON-ARRAY OCCURS 3000 TIMES.
05 WS-CON-ARR PIC X(206).

In the program,

Array-1 will be moved with 900 records from input file1
Array-2 will be moved with 800 records from input file2
Array-3 will be moved with 2100 (which is > 2000 declared limit in cobol) records from input file3

Finally when read the Array-2, it has the records overlapped

In thought of array-3 has caused the issue, I have increase the
limit from 2000 to 2200 and tried . But i got the same issue.

I tried increasing the limit of other array too. But the problem is not resolved
.Still the array-1 has the records got overlapped.

Please give an helping hand to resolve this issue.

Craq Giegerich · Posted: Wed Mar 12, 2008 7:26 pm

Check after you load each array to see when the error occurs.

Gnanas N · Posted: Wed Mar 12, 2008 7:26 pm

INITIALIZE those tables(arrays) to SPACES if you are using them for more than once before moving data to them.

dbzTHEdinosauer · Posted: Wed Mar 12, 2008 8:26 pm

Declare a counter for each of the internal COBOL Tables.

As you load each table, check the counter against the max number of occurances allowed for each table.

ranjithmainframe · New User Joined: 21 Jan 2008 Posts: 39 Location: chennai

Thank you..

I have just tried initializing the arrays which was not done before.
but still the array-2 has the same issue.

Further, the array overlapped happens only when the array-3 file get loaded with more than 2002 record exactly. say 2003 records.
And it is working fine when we give 2002 number of records as input to array-3.

Still i am working on it to resolve this....

Craq Giegerich · Posted: Wed Mar 12, 2008 10:09 pm

How is the subscript you are using defined?

ranjithmainframe · New User Joined: 21 Jan 2008 Posts: 39 Location: chennai

Hi Craq Giegerich,

My subscripts are defined as follows,

01 WS-PRO-CNT PIC 9(04) VALUE 0. for array-1
01 WS-ADD-CNT PIC 9(04) VALUE 0. for array-2
01 WS-CON-CNT PIC 9(04) VALUE 0. for array-3

Pcrummey · Posted: Thu Mar 13, 2008 12:36 am

Isn't there a max number of bytes for working storage?

Something like: Fixed length group items or tables are limited to 131,071 bytes.

There may not be any limitation any more(Never worked with working storage that big), I know there is for linkage to another program. But if there is a limit, your first Occurs would be over 1 million bytes. There is occurs depending that would make your table variable on the number of input records.

Anuj Dhawan · Posted: Thu Mar 13, 2008 12:54 am

Hi,

I might sound little dumb but didn't get when you say 'overlap'..what data do You expect in WS-PRO-ARRAY(1) & what do you get because of 'overlap'?

ranjithmainframe · New User Joined: 21 Jan 2008 Posts: 39 Location: chennai

Hi,

I meant data overlap because when read WS-PRO-ARRAY(i) and it has data that loaded from file-1 but it is not mapped at all with corresponding layout. All the records look like misplaced and get mixed with other records. I am not sure whether Array-3 is overlapped with Array-1. It looks like dump...

Thanks many...

Anuj Dhawan · Posted: Sun Mar 16, 2008 2:23 pm

Hi,

Show the data fromt input file & the data (perhaps DISPLAYs) using which you could say..

dbzTHEdinosauer · Posted: Mon Mar 17, 2008 12:39 pm

sounds as if you descision process (which array to populate) fails to properly identify which internal cobol table to fill, or one fo your routines to populate the internal cobol tables is populating the wrong table.

ranjithmainframe · New User Joined: 21 Jan 2008 Posts: 39 Location: chennai

Hi,

Thanks everyone for your time...

Due to time constraint, the same code has been replaced with SAS... But I suspect the problem was with array initialization... I will let everyone know if it the problem is identified in my testing...

thanks....