Our application uses the pro-isam files. Under version 2 of Pro-IV,
we found the maximum file size we could obtain was 192meg. We
currently upgraded to version 4 of Pro-iv and have found that you
can use the new iscr to get a file up to 384meg. Pro-iv has told
us this is due to the increase (doubling) of the page size from
1500 to 3000. They also told us that they would not support this
maximum file size. We have customers that are fastly approaching
the 192meg limitation and we are contemplating breaking the file
into 2 separate files to eleviate the problem wich we are estimating
at being a pretty good size task. Has anyone else run into the
192meg file limitation and used the 'new' 384meg file size? If so,
have your file(s) exceeded the 192meg size without any ill effects?
I appreciate any comments that you may have on this. Thanks.
FYI - The file that we are having a problem with has 3 re-defines. Our
approach is to have 1 file with the larger of the 3 and the other file
to contain the remaining 2 redefines.
Click the link below to see the new game I'm developing!
Pro-ISAM maximum file size
Started by
Guest_Bill Herthum_*
, Aug 27 1999 12:32 PM
9 replies to this topic
#2
Rob Fantini
-
- Members
-
- 291 posts
ProIV Guru
- Gender:Male
- Location:Haverhill, United States
Posted 28 August 1999 - 11:52 PM
I use C-ISAM for large files.
C-ISAM supports very large files.
supports alternate indexes
But C-ISAM files are 2-3 times the size per record.
The latest proiv releases supposedly support varialble legnth c-isam files, but I have not been able to creat variable legnth c-isam files with alternate indexes.
The alternate indexes are a great feature...
C-ISAM supports very large files.
supports alternate indexes
But C-ISAM files are 2-3 times the size per record.
The latest proiv releases supposedly support varialble legnth c-isam files, but I have not been able to creat variable legnth c-isam files with alternate indexes.
The alternate indexes are a great feature...
#3
Rob Donovan
-
- Admin
-
- 1,652 posts
rob@proivrc.com
- Gender:Male
- Location:Spain
Posted 29 August 1999 - 06:37 PM
How do you specify that a CISAM file has Variable record lengths in PRO-IV.
I know how to do it in C++, PRO-IV ltd said that we would have to pay for a special licence for them to develop PRO-IV with variable record length CISAM files.
Rob
I know how to do it in C++, PRO-IV ltd said that we would have to pay for a special licence for them to develop PRO-IV with variable record length CISAM files.
Rob
#4
Rob Fantini
-
- Members
-
- 291 posts
ProIV Guru
- Gender:Male
- Location:Haverhill, United States
Posted 29 August 1999 - 07:03 PM
I've got 4.532 on Sco Unix.
iscr & isin almost support variable legnth C-ISAM.
I can create a variable legnth C-ISAM file. 'bcheck' indicates that the file is a variable record legnth file.
However all my c-iam files have alternate indexes, and I can't figure out how to great a c-isam file with alternate indexes from command line.
iscr & isin almost support variable legnth C-ISAM.
I can create a variable legnth C-ISAM file. 'bcheck' indicates that the file is a variable record legnth file.
However all my c-iam files have alternate indexes, and I can't figure out how to great a c-isam file with alternate indexes from command line.
#7
Richard Bassett
-
- Members
-
- 707 posts
ProIV Guru
- Gender:Not Telling
- Location:Rural France
Posted 19 December 1999 - 11:19 PM
I've seen the 'extended' C-ISAM used without a problem.
In that case the problem file was logic.pro (!) so C-ISAM wasn't a possible solution!
In that case the problem file was logic.pro (!) so C-ISAM wasn't a possible solution!
Nothing's as simple as you think
#8
Guest_Anil_*
Guest_Anil_*
-
- Guests
Posted 01 May 2000 - 09:05 PM
We are currently running PRO-IV version 4.0 Revision 5.0.3 on PROISAM database on HP UX 10.2
We were under the impression that files upto 192 MB would not create any problems but we are having problem with certain customized files which are still failing when they reach 64 MB size.
Is there any way with the new version to find out the page length and the maximum size that the file can go upto.
Any help in this matter will be appreciated.
Thanks in Advance.
We were under the impression that files upto 192 MB would not create any problems but we are having problem with certain customized files which are still failing when they reach 64 MB size.
Is there any way with the new version to find out the page length and the maximum size that the file can go upto.
Any help in this matter will be appreciated.
Thanks in Advance.
#9
Rob Donovan
-
- Admin
-
- 1,652 posts
rob@proivrc.com
- Gender:Male
- Location:Spain
Posted 02 May 2000 - 09:18 AM
Hi,
In unix run...
iscr -k -r1500
where should be replaced by the key length of the file.
**WARNING: THIS WILL REMOVE ALL DATA IN THE FILE!!!
You must copy the data, do the 'iscr' and then copy the data back in.
With version 4.6r200 and above you can also set the record size to 3000 (I think to give 384MB files) but I'm not sure if this is on all platforms.
Rob
In unix run...
iscr -k
where
**WARNING: THIS WILL REMOVE ALL DATA IN THE FILE!!!
You must copy the data, do the 'iscr' and then copy the data back in.
With version 4.6r200 and above you can also set the record size to 3000 (I think to give 384MB files) but I'm not sure if this is on all platforms.
Rob
#10
Don Mayer
-
- Members
-
- 24 posts
Member
- Gender:Male
- Location:Dewitt, United States
Posted 02 May 2000 - 12:32 PM
To view the paging size of a file do the following command:
ischk -v [file]
This will give you the follwing information:
dwm1.pro: 0 records
Page size 512 bytes
Level 0: 1 pages
Level 1: 1 pages
2 total pages, 0 free. 100%
Load factor 0%
The page size determines the maximum file size, for every 512 bytes of paging space you get 32mb added to your file size. In your case the page space for the 64mb file is probably 1024. You can use the isout utility to get all the data out of your file then use the iscr command to recreate at a larger size (iscr -k?? -r1530 [file] -- is max support under 4.0) and then use the isin to put the data back. We have had to do this numerous times, since ProIV only creates files at the least size for the record length.
512 --> 32mb iscr -k? -r250 (or less)
1024 --> 64mb iscr -k? -r500 (251 - 500)
.
.
3584 --> 192mb iscr -k? -r1500 (1280 - 1500)
.
.
6144 --> 384mb (under 4.6) iscr -k? -r3000
ischk -v [file]
This will give you the follwing information:
dwm1.pro: 0 records
Page size 512 bytes
Level 0: 1 pages
Level 1: 1 pages
2 total pages, 0 free. 100%
Load factor 0%
The page size determines the maximum file size, for every 512 bytes of paging space you get 32mb added to your file size. In your case the page space for the 64mb file is probably 1024. You can use the isout utility to get all the data out of your file then use the iscr command to recreate at a larger size (iscr -k?? -r1530 [file] -- is max support under 4.0) and then use the isin to put the data back. We have had to do this numerous times, since ProIV only creates files at the least size for the record length.
512 --> 32mb iscr -k? -r250 (or less)
1024 --> 64mb iscr -k? -r500 (251 - 500)
.
.
3584 --> 192mb iscr -k? -r1500 (1280 - 1500)
.
.
6144 --> 384mb (under 4.6) iscr -k? -r3000
Reply to this topic
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
Click the link below to see the new game I'm developing!
