4 replies to this topic

[Marco.Bega]

Hi,
I have a problem with a binary file.
I'm using a pro-iv vers 4.6 with unix aix.

I have a update that read and write many records.
When the file dimension is about 2 gb pro-iv return me an error "Error in writing file"
Where is the problem? Unix ? Pro-iv? Binary File?

Thanks in advance
Marco

[Rob Donovan]

Hi,

It could be your version of UNIX.

Some versions have a 2GB limit per file...

Rob D.

[Mike Wright]

Yep, it's almost certainly the 2Gb limit. We're in the process of porting from Unix to Linux, and I came across this problem recently. One tar file being created was going to be approx 3Gb, and failed when writing to Unix.

We had to unmount and re-mount the file system being used, and specified it as Large File Compatible. It worked fine then.

This was only a temporary transfer directory though. I'm not sure if Large File Compatible file systems have any implications for a live Pro-IV data directory.

HTH

Mike

[Marco.Bega]

I had tried to do a cut from one file 2gb dimension
with a second file 2gb, and unix had created a new file from 4gb.


The server is an AIX with o.s. lastets version, and it isn't unlimited files dimension.

thanks
marco

[DARREN]

I had tried to do a cut from one file 2gb dimension
with a second file 2gb, and unix had created a new file from 4gb.


The server is an AIX with o.s. lastets version, and it isn't unlimited files dimension.

thanks
marco

The limitation is within PROIV. It uses a 32 bit wordlength for addressing (on 32 bit kernels anyway). The solution is to create two seperate text files i.e. create a function with two cycles containing your driver file and text file and then use SEL-RANGE to select your record sets in these cycles e.g. first cycle selects records from A to M and the second selects N to Z

You can use the same file definition for both text files - just use the alias command to assign the logical to the desired physical.