data overflow in working storage section

asmisurs · New User Joined: 24 Apr 2005 Posts: 2

Hi,

This is regarding overflow of data in working storage section. The program reads an input file which the data is keep on adding for every batch run. The input file is read into a table/array which is declared in working storage section. The overflow of data is causing other ws variables to be corrupted. For temporary solution we are using fillers after the table declaration for additional storage of data.

Could some one let me know is there any alternate way to handle the data in working storage section? What will be the maximum storage can working storage section can accomodate?
Your inputs and thouhts into this is really appreciable.

Thanks,
Sasi.
Bangalore

Gnanas N · Posted: Thu Apr 03, 2008 3:41 pm

dbzTHEdinosauer · Posted: Thu Apr 03, 2008 4:03 pm

normally, as an internal cobol table is loaded, one keeps track of the items added and compares against the max num items the table can contain. when this limit is reached, a useful message is displayed and the job is terminated.

data overflow is a very nice word to describe poor programming techniques

dick scherrer · Posted: Thu Apr 03, 2008 11:29 pm

Hello,

Why is an entire "large" file being read into working-storage? Sometimes an ok thing to do, but usually not.

Please do not say that it so that it can be compared against some other file. . . This is a terrible programming practice. . .

If you explain what the process does, we may be able to offer alternate suggestions.

Even if you fix the sloppy code that allows storage to be walked on, you will still have the issue of the size of the file growing.

Craq Giegerich · Posted: Thu Apr 03, 2008 11:37 pm

We have two programmers at the same time trying to overcome stupid designs.

Anuj Dhawan · Posted: Fri Apr 04, 2008 12:06 am