Skip to main content

ISAM Data Limitation

  • December 7, 2013
  • 5 replies
  • 0 views
D

Created an online solution for an appliance retail business using NetExpress v3.10. You can view this online solution in my personal website www.retailplus1.com

The question I would like to ask is the usual .DAT/.IDX data limitation since I tried encoding several records to check the limitation of an ISAM file. It seems to me that the limitation is1GB or about 1.3GB (indexed), it is getting a boundary violation error. Is this really the limit? Or is there any configuration that is needed to just even add a few Gigabyte to a file??

I only used $set indxformat"4" as my compiler directive.


#COBOLserver
#DataLimitation
#netexpress
#Windows

5 replies

Chris Glazier
Forum|alt.badge.img+3

Created an online solution for an appliance retail business using NetExpress v3.10. You can view this online solution in my personal website www.retailplus1.com

The question I would like to ask is the usual .DAT/.IDX data limitation since I tried encoding several records to check the limitation of an ISAM file. It seems to me that the limitation is1GB or about 1.3GB (indexed), it is getting a boundary violation error. Is this really the limit? Or is there any configuration that is needed to just even add a few Gigabyte to a file??

I only used $set indxformat"4" as my compiler directive.


#COBOLserver
#DataLimitation
#netexpress
#Windows

For an idxformat"4" file that is shared the limit is 1GB.

If the file is opened exclusively then the limit is 4GB.

I would recommend that you use idxformat"8" files with the filemaxsize option set to 8.

Then the files can be up to 128 tb in size if they are shared.

Thanks.

D

Created an online solution for an appliance retail business using NetExpress v3.10. You can view this online solution in my personal website www.retailplus1.com

The question I would like to ask is the usual .DAT/.IDX data limitation since I tried encoding several records to check the limitation of an ISAM file. It seems to me that the limitation is1GB or about 1.3GB (indexed), it is getting a boundary violation error. Is this really the limit? Or is there any configuration that is needed to just even add a few Gigabyte to a file??

I only used $set indxformat"4" as my compiler directive.


#COBOLserver
#DataLimitation
#netexpress
#Windows

Thanks Chris, you're a saver.

Anyhow from my code of idxformat"4".... that means I could just "edit" my Cobol codes to $set idxformat"8" and everything would be just fine?? Eventhough the file is already existing? I mean no need for me to Rebuild the indexes?

D

Created an online solution for an appliance retail business using NetExpress v3.10. You can view this online solution in my personal website www.retailplus1.com

The question I would like to ask is the usual .DAT/.IDX data limitation since I tried encoding several records to check the limitation of an ISAM file. It seems to me that the limitation is1GB or about 1.3GB (indexed), it is getting a boundary violation error. Is this really the limit? Or is there any configuration that is needed to just even add a few Gigabyte to a file??

I only used $set indxformat"4" as my compiler directive.


#COBOLserver
#DataLimitation
#netexpress
#Windows

Just read these statements from this forum;

Warning: do not set FILEMAXSIZE to 8 under any of the following circumstances:

-- You are sharing files with applications using earlier versions of the Micro Focus COBOL product that only supported 32-bit file access.

I am using NetExpress v3.10 (under Merant still). I do not know if my Cobol applications are affected by this scenario.

Chris Glazier
Forum|alt.badge.img+3

Created an online solution for an appliance retail business using NetExpress v3.10. You can view this online solution in my personal website www.retailplus1.com

The question I would like to ask is the usual .DAT/.IDX data limitation since I tried encoding several records to check the limitation of an ISAM file. It seems to me that the limitation is1GB or about 1.3GB (indexed), it is getting a boundary violation error. Is this really the limit? Or is there any configuration that is needed to just even add a few Gigabyte to a file??

I only used $set indxformat"4" as my compiler directive.


#COBOLserver
#DataLimitation
#netexpress
#Windows

Actually, what that statement means is that you cannot use filemaxsize"8" if you are sharing the same data files with applications that are not using filemaxsize"8".

So if you use filemaxsize"8" then ALL programs that use this same file must also use filemaxsize"8" or the file will become corrupt.

From your previous post, just changing the configuration option from idxformat"4" to idxformat"8" will only work for new files that are created by opening them output.

In order to take advantage of idxformat"8" larger files for existing files, you must convert the existing idxformat"4" files to idxformat"8" as the file formats are completely different.

I would recommend using the rebuild utility to convert the files.

D

Created an online solution for an appliance retail business using NetExpress v3.10. You can view this online solution in my personal website www.retailplus1.com

The question I would like to ask is the usual .DAT/.IDX data limitation since I tried encoding several records to check the limitation of an ISAM file. It seems to me that the limitation is1GB or about 1.3GB (indexed), it is getting a boundary violation error. Is this really the limit? Or is there any configuration that is needed to just even add a few Gigabyte to a file??

I only used $set indxformat"4" as my compiler directive.


#COBOLserver
#DataLimitation
#netexpress
#Windows

Got it.... Thanks again Chris.

Recent badge winners

Explore all badges
Terms & ConditionsAccessibility statement