Skip to main content

Been using IDX4 data configuration in some of my applications BUT apparently it won't go any big compared to IDX8. However I find that IDX8 is much more vulnerable to corruption (well, mostly on desktop/PC power failure interruptions). Is any of you experiencing the same?


#netexpress
#DataLimitation

Been using IDX4 data configuration in some of my applications BUT apparently it won't go any big compared to IDX8. However I find that IDX8 is much more vulnerable to corruption (well, mostly on desktop/PC power failure interruptions). Is any of you experiencing the same?


#netexpress
#DataLimitation
I don't believe that IDX8 is more vulnerable to corruption but the simple fact that the data and the indices all exist within the same file can make it more difficult to recover an IDX8 file once it is in a corrupted state. Whereas the index portion of an IDX4 file can be recreated as long as the .DAT portion is intact, this isn't always true for IDX8 files (depending on the type of corruption of course)

In Visual COBOL we have created a new filetype IDXFORMAT"12" which is the large indexed file format of IDX8 which uses a separate index file like IDX4.

This is not available in the NX/SX products however.

Been using IDX4 data configuration in some of my applications BUT apparently it won't go any big compared to IDX8. However I find that IDX8 is much more vulnerable to corruption (well, mostly on desktop/PC power failure interruptions). Is any of you experiencing the same?


#netexpress
#DataLimitation
Thanks Chris,

Been using IDX8 though and currently it is not easily being corrupted... I used the formatted IDX8 for all my componentized (COM ) Cobol application and it works perfectly online. It really does serve its purpose.

IDX8 has a megaterabyte data limitation as documented.... how about IDXFORMAT"12"?

Been using IDX4 data configuration in some of my applications BUT apparently it won't go any big compared to IDX8. However I find that IDX8 is much more vulnerable to corruption (well, mostly on desktop/PC power failure interruptions). Is any of you experiencing the same?


#netexpress
#DataLimitation

IDX12 has the same size limitations as IDX8. Please see the chart here:

To support the maximum size the file handler configuration option FILEPOINTERSIZE=8 must be set.

IDX12 is only supported in Visual COBOL.

Terms & ConditionsAccessibility statement