|
View previous topic :: View next topic
|
| Author |
Message |
sabarikanth
New User
Joined: 07 Jun 2010
Posts: 59
Location: coimbatore
|
|
|
|
Hi team,
I have a program writen in Easytrieve. I have declared a Table of size 240000. Now i have to increase my table size to 500000. But if i change the value as 500000 then i'm receiving RC16.
| Code: |
FILE MASTER TABLE 240000
ARG 1 9 A
DESC 13 13 A
|
Error:
| Code: |
*******A003 INSUFFICIENT CORE STORAGE AVAILABLE - 00 00A7D8F0 D020 0538
MASTER 1 INPUT TABLE SAM FIX BLK 80 2
*******A014 PREMATURE TERMINATION DUE TO PREVIOUS ERROR(S) |
|
|
| Back to top |
|
 |
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix
|
|
|
|
And the question is?
Can't say I've ever tried a SAM file as a table. What it does, I have no idea.
One thing is you are using 22 bytes of data but have 80 bytes of record. That is not going to help.
Have you increased the region size already?
Have you considered reading the SAM and building a VIRTUAL table file, with just the data you need? I don't know if it would work for the size.
The sure-fire way to do it would be to replace the SAM with a VSAM KSDS with keyed reads.
I think you need to explain a little bit more about why you have such a big look-up table, and how you think it works as a SAM file. |
|
| Back to top |
|
|
sabarikanth
New User
Joined: 07 Jun 2010
Posts: 59
Location: coimbatore
|
|
|
|
HI Bill,
Yes i have increased the region size in EZTVFM. But still it is throwing the same error.
| Quote: |
| One thing is you are using 22 bytes of data but have 80 bytes of record. That is not going to help. |
How to acheive in changing 80 bytes from 22 bytes?
| Quote: |
| I think you need to explain a little bit more about why you have such a big look-up table, and how you think it works as a SAM file. |
We have a daily update in the Master file(specified earlier). So the table keeps on increasing in size.
Changing the file to a Key sequence Vsam would help in this.? |
|
| Back to top |
|
|
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix
|
|
|
|
For your table-lookup you have ARG (9 bytes) and DESC (13 bytes starting from position 13). I think you MASTER is 80 bytes long.
If you just extract the ARG and DESC data to a new file, then you will be only storing 22 bytes for each record, nearly a 75% saving which might allow for your doubling in number of entries in the table - it depends whether it is space or entries which is being exceeded (I don't know).
This "cut down" could be done externally to the program, or as an earliery JOB in the program. If you do it in the program, try making it a VIRTUAL file (I always used VIRTUAL for tables and only included the needed data, but never had any tables anywhere near this size).
You could make the "cut down" a VSAM KSDS and replace the table look-up, as I said before. If your MASTER is going to continue to grow, and if there is some immovable limit to do with tables, then at some point you are going to hit the limit, so now might be a good time to avoid that. With a KSDS you'd be able to handle orders of magnitude more than 500,000 if necessary.
Same 22 byte data, 9 byte key, read with the key, if found, use it, if not found, do whatever you are supposed to do.
I don't understand, if you have only 80 bytes, what is on the "MASTER" file. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
| Quote: |
| So the table keeps on increasing in size. |
If this is true, you need to stop using the "table". . .
One future day (like now) this will happen again and there will probably not be a way to save another 75%.
Why was this put into a table? How will the data be used? |
|
| Back to top |
|
|
|
|
