MVSFORUMS.com

suma · Beginner Joined: 23 Jan 2006 Posts: 65 Topics: 29

Hi all,

Does anyone know; what how these fillers are related to TABLE-RECORD table..please let me know.

CraigG · Posted: Wed Jan 16, 2008 9:23 am Post subject:

Looks like someone is trying to reserve extra space for the table-record table. It is not a save way to do it, if subscript range checking is in on then the extra occurances can't be accessed and if the compilier optimizer is used the space won't be there. Poor programming and poor documentation causes many problems.

suma · Beginner Joined: 23 Jan 2006 Posts: 65 Topics: 29

Thanks CraigG for your quick reply....

Is there any way I can change this type of coding..!
We are getting S0C4 abend due to this array from long back..and we are keep on adding more and more fillers to this array.

regards
Suma

jsharon1248 · Posted: Wed Jan 16, 2008 9:54 am Post subject:

Is this a really old program? Also, is the code referencing occurrences in the table higher than 728? I remember the old COBOL table size limits were much lower than they are now, although I can't find a manual old enough to say what the old limits were. The new table size limit is about 16MB, so if you have a chance to eliminate the intentional table overflow, I'd say, do it.

suma · Beginner Joined: 23 Jan 2006 Posts: 65 Topics: 29

yes..this is one of the old program in our shop. This program was created in 1994 and using old compiler. I cann't able to change the occurs clause. when I tried to change the occurs clause I got the error as shown...

"FIXED LENGTH GROUP ITEM IN WORKING-STORAGE OR LINKAGE SECTION IS GT 131,071 BYTES.
TRUNCATED TO 131,071. "

I think there is no way without adding the extra fillers...

Thanks
Suma

CraigG · Posted: Wed Jan 16, 2008 10:16 am Post subject:

jsharon1248 · Posted: Wed Jan 16, 2008 2:10 pm Post subject:

You could modify the process to utilize a VSAM file. If you have a unique key, you could use a KSDS file. If it's not unique, you could define an alternate index and utilize that. You could also try an RRDS file. Any of these options eliminates your worries about table overflow. I'd recommend creating the VSAM file in a separate step and reading it in the program that you posted. You could load and process in the same pgm, but it would probably be cleaner to separate the tasks.